Octopoda MCP Server

octopoda PyPI v3.3.4

Published by ryjoxtechnologies — 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
A
93/100
Last scanned get badge →
Trust
A · 93/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
A Why this grade threat 100 − adoption risk = 93/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 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. 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 (synrix_runtime/dashboard/static/assets/NeuralGraph-JivWmplo.js)MTC-SRC-010

In the server's implementation (`synrix_runtime/dashboard/static/assets/NeuralGraph-JivWmplo.js:4060`): 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: {let t=ov(s,e),{Body:n}=new Function(t)();return n}function ov(s,e){return` ${lv(s,e)} ${av(s)} return {Body: Body, V

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 synrix_runtime/dashboard/static/assets/NeuralGraph-JivWmplo.js

high Dynamic code execution in server code (synrix_runtime/dashboard/static/assets/NeuralGraph-JivWmplo.js)MTC-SRC-001

In the server's implementation (`synrix_runtime/dashboard/static/assets/NeuralGraph-JivWmplo.js:4060`): 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: {let t=ov(s,e),{Body:n}=new Function(t)();return n}function ov(s,e){return` ${lv(s,e)} ${av(s)} return {Body: Body, V

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 synrix_runtime/dashboard/static/assets/NeuralGraph-JivWmplo.js

high Dynamic code execution in server code (synrix_runtime/dashboard/static/assets/index-DTLPD_iM.js)MTC-SRC-001

In the server's implementation (`synrix_runtime/dashboard/static/assets/index-DTLPD_iM.js:6193`): 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: }\r result = eval(expression, {"__builtins__": {}}, allowed_names)\r return str(result)\r excep

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 synrix_runtime/dashboard/static/assets/index-DTLPD_iM.js

high Shell/command execution in server code (octopoda_zf/active/sandbox.py)MTC-SRC-002

In the server's implementation (`octopoda_zf/active/sandbox.py:80`): 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: ct = {} exec(code, self._safe_globals(), ns) # noqa: S102 - sandboxed; see docstring bo

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 octopoda_zf/active/sandbox.py

high Shell/command execution in server code (synrix/engine.py)MTC-SRC-002

In the server's implementation (`synrix/engine.py:183`): 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: try: result = subprocess.run( [str(engine_path), "--version"], capture_output=True,

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 synrix/engine.py

high Shell/command execution in server code (synrix_runtime/dashboard/static/assets/index-DTLPD_iM.js)MTC-SRC-002

In the server's implementation (`synrix_runtime/dashboard/static/assets/index-DTLPD_iM.js:10404`): 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: s\r store_result = subprocess.run(\r [sys.executable, "-c", """\r from octopoda import AgentRuntime\r ag

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 synrix_runtime/dashboard/static/assets/index-DTLPD_iM.js

high Shell/command execution in server code (synrix_runtime/loop_intel_v2/circuit_breaker.py)MTC-SRC-002

In the server's implementation (`synrix_runtime/loop_intel_v2/circuit_breaker.py:73`): 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: } try: subprocess.run( ["curl", "-s", "-X", "POST", "https://api.resend.com/emails",

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 synrix_runtime/loop_intel_v2/circuit_breaker.py

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([octopoda_read_messages]) co-exist with external-action tools ([octopoda_send_message]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [octopoda_read_messages] → sinks [octopoda_send_message]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow octopoda_read_messages → octopoda_send_message

medium Hardcoded egress to an external endpoint (synrix/fact_extractor.py)MTC-SRC-003

In the server's implementation (`synrix/fact_extractor.py:409`): 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: ry: resp = requests.post( "https://api.anthropic.com/v1/messages", header

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 synrix/fact_extractor.py

medium Hardcoded egress to an external endpoint (synrix_runtime/api/cloud_server.py)MTC-SRC-003

In the server's implementation (`synrix_runtime/api/cloud_server.py:3486`): 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: ode.js): await fetch("https://api.octopoda.dev/v1/ingest", { 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 synrix_runtime/api/cloud_server.py

medium Hardcoded egress to an external endpoint (synrix_runtime/dashboard/static/assets/index-DTLPD_iM.js)MTC-SRC-003

In the server's implementation (`synrix_runtime/dashboard/static/assets/index-DTLPD_iM.js:24982`): 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.octopodas.com/v1/agents/my_agent/remember", { 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 synrix_runtime/dashboard/static/assets/index-DTLPD_iM.js

medium Dynamic module load from a non-literal (octopoda_zf/active/sandbox.py)MTC-SRC-005

In the server's implementation (`octopoda_zf/active/sandbox.py:60`): 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: he sandbox") return __import__(name, *args, **kwargs) class RestrictedSandbox: """Dev/benchmark sandbox. See m

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 octopoda_zf/active/sandbox.py

medium Dynamic module load from a non-literal (octopoda_zf/instrument/autogen_hook.py)MTC-SRC-005

In the server's implementation (`octopoda_zf/instrument/autogen_hook.py:88`): 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: try: mod = __import__(path, fromlist=["BaseGroupChat"]) base_group_chat = getattr(mod, "BaseGro

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 octopoda_zf/instrument/autogen_hook.py

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_full_system.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_full_system.py:350`): 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: ps_redirect(): r = requests.get("http://octopodas.com", timeout=10, allow_redirects=False) return r.status_cod

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 tests/test_full_system.py

low Shell/command execution in packaging/dev tooling (tests/test_full_system.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_full_system.py:230`): 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(): result = subprocess.run( [sys.executable, "-c", "from octopoda import AgentRuntime; print('OK')"

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 tests/test_full_system.py

Tools 29

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

  • octopoda_read_messagesingests untrusted input
  • octopoda_send_messagenetwork egress
  • octopoda_agent_statsno sensitive capability
  • octopoda_broadcastno sensitive capability
  • octopoda_consolidateno sensitive capability
  • octopoda_forgetno sensitive capability
  • octopoda_forget_staleno sensitive capability
  • octopoda_get_contextno sensitive capability
  • octopoda_get_goalno sensitive capability
  • octopoda_list_agentsno sensitive capability
Show 19 more tools ↓
  • octopoda_log_decisionno sensitive capability
  • octopoda_loop_historyno sensitive capability
  • octopoda_loop_statusno sensitive capability
  • octopoda_memory_healthno sensitive capability
  • octopoda_process_conversationno sensitive capability
  • octopoda_read_sharedno sensitive capability
  • octopoda_recallno sensitive capability
  • octopoda_recall_historyno sensitive capability
  • octopoda_recall_similarno sensitive capability
  • octopoda_relatedno sensitive capability
  • octopoda_rememberno sensitive capability
  • octopoda_restoreno sensitive capability
  • octopoda_searchno sensitive capability
  • octopoda_search_filteredno sensitive capability
  • octopoda_set_goalno sensitive capability
  • octopoda_shareno sensitive capability
  • octopoda_snapshotno sensitive capability
  • octopoda_statusno sensitive capability
  • octopoda_update_progressno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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
v3.3.4 latest A 93/100 15 1.9.0 2026-07-23

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: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/octopoda/badge.svg)](https://mcptrustchecker.com/registry/octopoda)
HTML
<a href="https://mcptrustchecker.com/registry/octopoda"><img src="https://mcptrustchecker.com/registry/octopoda/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/octopoda/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 octopoda --online --registry pypi

Use the free API → How scoring works

More in Developer Tools