Society Protocol (societycomputer) MCP Server

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.

Trust grade
D
68/100
Last scanned get badge →
Trust
D · 68/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
D Why this grade threat 75 − adoption risk = 68/100

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:

PointsWhat was foundCategory
−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:

PointsAdoption-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.

Findings 15

high Dynamic evaluation of a non-literal value (dist/skills/engine.js)MTC-SRC-010

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

high Assembled command execution and dynamic evaluation in the same serverMTC-SRC-011

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

high Dynamic code execution in server code (dist/skills/engine.js)MTC-SRC-001

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

high Shell/command execution in server code (dist/autoconfig.js)MTC-SRC-002

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

high Shell/command execution in server code (dist/bootstrap.js)MTC-SRC-002

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

high Shell/command execution in server code (dist/cli/commands.js)MTC-SRC-002

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

high Shell/command execution in server code (dist/index.js)MTC-SRC-002

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

high Shell/command execution in server code (dist/persona/zkp/engine.js)MTC-SRC-002

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

high Shell/command execution in server code (dist/skills/engine.js)MTC-SRC-002

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

medium Hardcoded egress to an external endpoint (dist/planner.js)MTC-SRC-003

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

medium Hardcoded egress to an external endpoint (dist/skills/engine.js)MTC-SRC-003

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

medium Untrusted input concatenated into a command sink (dist/autoconfig.js)MTC-SRC-009

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

medium Untrusted input concatenated into a command sink (dist/index.js)MTC-SRC-009

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

medium Dynamic module load from a non-literal (dist/compression.js)MTC-SRC-005

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

medium Dynamic module load from a non-literal (dist/persona/embeddings.js)MTC-SRC-005

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

Tools 57

Each tool and what it can reach — statically extracted from the published source.

  • society_send_messagenetwork egress
  • circuit_idno sensitive capability
  • Persona Active Capabilitiesno sensitive capability
  • Persona Capability by Tokenno sensitive capability
  • Persona Claim by IDno sensitive capability
  • Persona Graph by Domainno sensitive capability
  • Persona Memory by IDno sensitive capability
  • Persona Preferences by Categoryno sensitive capability
  • Persona Profileno sensitive capability
  • Persona ZKP Circuitsno sensitive capability
Show 47 more tools ↓
  • Persona ZKP Proof by IDno sensitive capability
  • persona_add_memoryno sensitive capability
  • persona_attenuate_capabilityno sensitive capability
  • persona_contextno sensitive capability
  • persona_generate_zk_proofno sensitive capability
  • persona_get_profileno sensitive capability
  • persona_issue_capabilityno sensitive capability
  • persona_issue_claimno sensitive capability
  • persona_memory_digestno sensitive capability
  • persona_preferences_snapshotno sensitive capability
  • persona_query_graphno sensitive capability
  • persona_revoke_capabilityno sensitive capability
  • persona_run_retention_sweepno sensitive capability
  • persona_search_memoriesno sensitive capability
  • persona_share_subgraphno sensitive capability
  • persona_update_preferenceno sensitive capability
  • persona_verify_access_logno sensitive capability
  • persona_verify_zk_proofno sensitive capability
  • persona_zkp_challengeno sensitive capability
  • queryno sensitive capability
  • society_cancel_chainno sensitive capability
  • society_export_capsuleno sensitive capability
  • society_get_chainno sensitive capability
  • society_get_peersno sensitive capability
  • society_get_pending_stepsno sensitive capability
  • society_get_reputationno sensitive capability
  • society_get_statusno sensitive capability
  • society_get_swarm_statusno sensitive capability
  • society_join_roomno sensitive capability
  • society_leave_roomno sensitive capability
  • society_list_bridgesno sensitive capability
  • society_list_chainsno sensitive capability
  • society_list_missionsno sensitive capability
  • society_list_peeringsno sensitive capability
  • society_list_roomsno sensitive capability
  • society_list_templatesno sensitive capability
  • society_open_bridgeno sensitive capability
  • society_pause_missionno sensitive capability
  • society_request_peeringno sensitive capability
  • society_resume_missionno sensitive capability
  • society_review_stepno sensitive capability
  • society_start_missionno sensitive capability
  • society_start_research_swarmno sensitive capability
  • society_stop_missionno sensitive capability
  • society_submit_stepno sensitive capability
  • society_summonno sensitive capability
  • vault_idno sensitive capability

What this scan could not see

Versions 1

Scan 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.

VersionScoreFindingsEngineScanned
v1.3.1 latest D 68/100 15 1.9.0 2026-07-24

Embed this score

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.

MCP Trust Score: D · 68/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/society-protocol-2/badge.svg)](https://mcptrustchecker.com/registry/society-protocol-2)
HTML
<a href="https://mcptrustchecker.com/registry/society-protocol-2"><img src="https://mcptrustchecker.com/registry/society-protocol-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/society-protocol-2/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

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

Use the free API → How scoring works

Other implementations of Society Protocol 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Developer Tools