society-protocol
npm
v1.3.1
Published by societycomputer — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 24.9 = 75. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −15.4 | Assembled command execution and dynamic evaluation in the same server MTC-SRC-011 | injection |
| −9.5 | Untrusted input concatenated into a command sink ×2 MTC-SRC-009 | injection |
2. Client adoption risk — 75 − 7 = 68. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`dist/skills/engine.js:639`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ão!) return eval(expr); } catch { return false; } } buildOpenCla
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/skills/engine.js
The implementation both builds shell commands out of runtime values (`dist/autoconfig.js`) and evaluates runtime values as code (`dist/skills/engine.js`). Each is a separate arbitrary-execution primitive; a server exposing both gives anything that reaches either one a direct path to running attacker-chosen code. These two sinks are in different files — confirm whether they are actually connected, or are unrelated code paths (e.g. a vendored bundle plus a CLI wrapper).
Fix: Remove the dynamic eval, and pass command arguments as an argv array instead of building a shell string. If both are genuinely required, constrain and validate every value that can reach them.
Location: server implementation
In the server's implementation (`dist/skills/engine.js:639`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ão!) return eval(expr); } catch { return false; } } buildOpenCla
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/skills/engine.js
In the server's implementation (`dist/autoconfig.js:14`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ; import { exec } from 'child_process'; import { detectCloudEnvironment } from './bootstrap.js'; const execAsync = promi
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/autoconfig.js
In the server's implementation (`dist/bootstrap.js:15`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ; import { exec } from 'child_process'; const execAsync = promisify(exec); const REGISTRY_URL = process.env.SOCIETY_REGI
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/bootstrap.js
In the server's implementation (`dist/cli/commands.js:32`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: cSync } = await import('child_process'); let cmd = 'npx vitest run'; if (options.unit) cmd += ' test/uni
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/cli/commands.js
In the server's implementation (`dist/index.js:56`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: spawn, execSync } from 'child_process'; import { fileURLToPath } from 'url'; import { resolve } from 'path'; import { re
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/index.js
In the server's implementation (`dist/persona/zkp/engine.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execFileSync } from 'child_process'; import { existsSync, readFileSync } from 'fs'; import { dirname, join } from 'pa
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/persona/zkp/engine.js
In the server's implementation (`dist/skills/engine.js:16`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { SkillParser } from './parser.js'; export class SkillExecutionError exte
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/skills/engine.js
In the server's implementation (`dist/planner.js:243`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const response = await fetch('https://api.anthropic.com/v1/messages', { method: 'POST', headers
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/planner.js
In the server's implementation (`dist/skills/engine.js:317`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const response = await fetch('https://api.anthropic.com/v1/messages', { method: 'POST', headers
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/skills/engine.js
In the server's implementation (`dist/autoconfig.js:119`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const { stdout } = exec('df -T ' + path); // Parse output to get filesystem type re
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/autoconfig.js
In the server's implementation (`dist/index.js:1653`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: md) { try { execSync(`command -v ${cmd}`, { stdio: 'ignore' }); return true; } catch {
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/index.js
In the server's implementation (`dist/compression.js:142`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eName) { return import(moduleName); } getCompressionStats(original, compressed) { const savings
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/compression.js
In the server's implementation (`dist/persona/embeddings.js:76`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: w Function('m', 'return import(m)'); const ort = await dynamicImport('onnxruntime-node'); if (!t
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/persona/embeddings.js
Each tool and what it can reach — statically extracted from the published source.
society_send_messagenetwork egresscircuit_idno sensitive capabilityPersona Active Capabilitiesno sensitive capabilityPersona Capability by Tokenno sensitive capabilityPersona Claim by IDno sensitive capabilityPersona Graph by Domainno sensitive capabilityPersona Memory by IDno sensitive capabilityPersona Preferences by Categoryno sensitive capabilityPersona Profileno sensitive capabilityPersona ZKP Circuitsno sensitive capabilityPersona ZKP Proof by IDno sensitive capabilitypersona_add_memoryno sensitive capabilitypersona_attenuate_capabilityno sensitive capabilitypersona_contextno sensitive capabilitypersona_generate_zk_proofno sensitive capabilitypersona_get_profileno sensitive capabilitypersona_issue_capabilityno sensitive capabilitypersona_issue_claimno sensitive capabilitypersona_memory_digestno sensitive capabilitypersona_preferences_snapshotno sensitive capabilitypersona_query_graphno sensitive capabilitypersona_revoke_capabilityno sensitive capabilitypersona_run_retention_sweepno sensitive capabilitypersona_search_memoriesno sensitive capabilitypersona_share_subgraphno sensitive capabilitypersona_update_preferenceno sensitive capabilitypersona_verify_access_logno sensitive capabilitypersona_verify_zk_proofno sensitive capabilitypersona_zkp_challengeno sensitive capabilityqueryno sensitive capabilitysociety_cancel_chainno sensitive capabilitysociety_export_capsuleno sensitive capabilitysociety_get_chainno sensitive capabilitysociety_get_peersno sensitive capabilitysociety_get_pending_stepsno sensitive capabilitysociety_get_reputationno sensitive capabilitysociety_get_statusno sensitive capabilitysociety_get_swarm_statusno sensitive capabilitysociety_join_roomno sensitive capabilitysociety_leave_roomno sensitive capabilitysociety_list_bridgesno sensitive capabilitysociety_list_chainsno sensitive capabilitysociety_list_missionsno sensitive capabilitysociety_list_peeringsno sensitive capabilitysociety_list_roomsno sensitive capabilitysociety_list_templatesno sensitive capabilitysociety_open_bridgeno sensitive capabilitysociety_pause_missionno sensitive capabilitysociety_request_peeringno sensitive capabilitysociety_resume_missionno sensitive capabilitysociety_review_stepno sensitive capabilitysociety_start_missionno sensitive capabilitysociety_start_research_swarmno sensitive capabilitysociety_stop_missionno sensitive capabilitysociety_submit_stepno sensitive capabilitysociety_summonno sensitive capabilityvault_idno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.3.1 latest |
D 68/100 | 15 | 1.9.0 | 2026-07-24 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan society-protocol --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.