Coherence MCP Server
coherence-mcp-server
npm
v0.5.5
Published by seeker71 — 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.
Unified MCP server for Coherence Network — invite anyone or anything to ask what is alive, browse ideas and field stories, and contribute with attribution.
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 − 11 = 89. 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 |
|---|---|
| −10 | capability blast radius (critical) — 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 3
critical Completed toxic-flow trifecta across toolsMTC-FLOW-002
This server (without client built-ins) exposes a complete data-exfiltration chain: coherence_get_news_feed → coherence_read_file ⇒ coherence_send_message. Untrusted input is ingested, private data is read, and it can be sent to an external sink — and at least one leg is a direct schema wire (⇒), where a producer's output drops straight into a free-text parameter of the next tool, so the chain needs little agent cooperation. Static analysis proves the primitive exists, not that a specific run will occur.
Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.
Location: flow coherence_get_news_feed → coherence_read_file → coherence_send_message
high Shell/command execution in server code (index.mjs)MTC-SRC-002
In the server's implementation (`index.mjs:11`): 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: rt { spawn } from "node:child_process"; import { fileURLToPath } from "node:url"; import { dirname, join } from "node: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 index.mjs
low Unconstrained path parameter "path" on "coherence_read_file"MTC-CAP-008
Tool "coherence_read_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool coherence_read_file · inputSchema.properties.path
Tools 92
Each tool and what it can reach — statically extracted from the published source.
coherence_get_news_feedingests untrusted inputcoherence_list_conceptsingests untrusted inputcoherence_list_ideasingests untrusted inputcoherence_news_feedingests untrusted inputcoherence_read_filereads sensitive datacoherence_send_messagenetwork egresscoherence_add_news_sourceno sensitive capabilitycoherence_advance_ideano sensitive capabilitycoherence_agent_invitationno sensitive capabilitycoherence_apply_blueprintno sensitive capability
Show 82 more tools ↓
coherence_awareness_publishno sensitive capabilitycoherence_awareness_streamno sensitive capabilitycoherence_belief_profileno sensitive capabilitycoherence_cc_supplyno sensitive capabilitycoherence_constellationno sensitive capabilitycoherence_contribute_field_storyno sensitive capabilitycoherence_contributor_ledgerno sensitive capabilitycoherence_create_assetno sensitive capabilitycoherence_create_edgeno sensitive capabilitycoherence_create_ideano sensitive capabilitycoherence_create_specno sensitive capabilitycoherence_create_workspaceno sensitive capabilitycoherence_create_workspace_projectno sensitive capabilitycoherence_discoverno sensitive capabilitycoherence_federation_nodesno sensitive capabilitycoherence_friction_reportno sensitive capabilitycoherence_get_assetno sensitive capabilitycoherence_get_change_requestno sensitive capabilitycoherence_get_conceptno sensitive capabilitycoherence_get_deposit_historyno sensitive capabilitycoherence_get_dif_statsno sensitive capabilitycoherence_get_entity_edgesno sensitive capabilitycoherence_get_field_storyno sensitive capabilitycoherence_get_field_story_artifactno sensitive capabilitycoherence_get_ideano sensitive capabilitycoherence_get_identitiesno sensitive capabilitycoherence_get_inboxno sensitive capabilitycoherence_get_nearby_peersno sensitive capabilitycoherence_get_news_resonanceno sensitive capabilitycoherence_get_recent_difno sensitive capabilitycoherence_get_resonant_peersno sensitive capabilitycoherence_get_specno sensitive capabilitycoherence_get_taskno sensitive capabilitycoherence_get_treasury_infono sensitive capabilitycoherence_get_trending_newsno sensitive capabilitycoherence_get_workspaceno sensitive capabilitycoherence_get_workspace_activityno sensitive capabilitycoherence_get_workspace_pillarsno sensitive capabilitycoherence_governance_requestsno sensitive capabilitycoherence_idea_progressno sensitive capabilitycoherence_invite_memberno sensitive capabilitycoherence_lineage_valuationno sensitive capabilitycoherence_link_conceptsno sensitive capabilitycoherence_link_identityno sensitive capabilitycoherence_list_assetsno sensitive capabilitycoherence_list_blueprintsno sensitive capabilitycoherence_list_change_requestsno sensitive capabilitycoherence_list_edgesno sensitive capabilitycoherence_list_federation_nodesno sensitive capabilitycoherence_list_lineageno sensitive capabilitycoherence_list_my_workspacesno sensitive capabilitycoherence_list_news_sourcesno sensitive capabilitycoherence_list_providersno sensitive capabilitycoherence_list_specsno sensitive capabilitycoherence_list_tasksno sensitive capabilitycoherence_list_workspace_membersno sensitive capabilitycoherence_list_workspace_projectsno sensitive capabilitycoherence_list_workspacesno sensitive capabilitycoherence_lookup_identityno sensitive capabilitycoherence_news_resonanceno sensitive capabilitycoherence_node_message_sendno sensitive capabilitycoherence_node_messagesno sensitive capabilitycoherence_pipeline_policiesno sensitive capabilitycoherence_propose_governanceno sensitive capabilitycoherence_record_contributionno sensitive capabilitycoherence_record_depositno sensitive capabilitycoherence_resonanceno sensitive capabilitycoherence_resonateno sensitive capabilitycoherence_select_ideano sensitive capabilitycoherence_showcaseno sensitive capabilitycoherence_statusno sensitive capabilitycoherence_task_claimno sensitive capabilitycoherence_task_eventsno sensitive capabilitycoherence_task_nextno sensitive capabilitycoherence_task_reportno sensitive capabilitycoherence_task_seedno sensitive capabilitycoherence_traceno sensitive capabilitycoherence_update_ideano sensitive capabilitycoherence_update_specno sensitive capabilitycoherence_vitalityno sensitive capabilitycoherence_vote_governanceno sensitive capabilitycoherence_workspace_tasksno 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
- Tools were statically extracted from the published source (92 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.5.5 latest |
B 89/100 | 3 | 1.13.0 | 2026-09-07 |
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.
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 coherence-mcp-server --onlineMore in AI, Memory & Reasoning
FDA device & vehicle recall risk for AI agents: recall history, MAUDE trend, risk score.
Open-source MCP server exposing Agent402.Tools' catalog — 500+ strong: 400+ self-hostable tools + 100 multi-tool skill packs (security-audit, trend-analysis, structured-scrape, decode-blob, forecasting-bake-off) for AI agents — browser, web search & answe
Zero-dependency MCP server that gives AI agents a self-updating project memory in AGENTS.md. Returns merge instructions instead of mutating state, so every change is a reviewable diff.
MCP Apps UI resources and server helpers for n8n
MCP server providing comprehensive access to BookStack knowledge management system
MCP server for tracking achievements with STAR methodology