Contorium MCP Server

@contorium/mcp npm v1.3.1

Published by @contorium — 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.

MCP bridge to Contorium Project Intelligence Layer — inspect, capture, and transfer project decisions, reasoning, and state for Claude Code, Cursor, Codex, and other MCP hosts.

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 3

high Shell/command execution in server code (bin/mcp-dashboard-bootstrap.cjs)MTC-SRC-002

In the server's implementation (`bin/mcp-dashboard-bootstrap.cjs:4`): 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 } = require('node:child_process'); const fs = require('node:fs'); const path = require('node:path'); const worksp

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 bin/mcp-dashboard-bootstrap.cjs

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

In the server's implementation (`dist/dashboardAttach.js:1`): 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 * as fs from 'node:fs'; import * as path from 'node:path'; import { bumpW

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/dashboardAttach.js

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

In the server's implementation (`dist/dashboardEnsure.js:1`): 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 * as fs from 'node:fs'; import * as path from 'node:path'; import { fileU

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/dashboardEnsure.js

Tools 102

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

  • analyze_projectreads sensitive data
  • get_project_evolution_timelinereads sensitive data
  • ask_projectno sensitive capability
  • capture_decisionno sensitive capability
  • capture_focusno sensitive capability
  • capture_noteno sensitive capability
  • commit_decisionno sensitive capability
  • confirm_handoff_injectionno sensitive capability
  • explain_contextno sensitive capability
  • get_active_intentsno sensitive capability
Show 92 more tools ↓
  • get_ai_statusno sensitive capability
  • get_blast_radiusno sensitive capability
  • get_change_logno sensitive capability
  • get_cognitive_healthno sensitive capability
  • get_cognitive_insightsno sensitive capability
  • get_cognitive_modeno sensitive capability
  • get_cognitive_snapshotno sensitive capability
  • get_cognitive_stateno sensitive capability
  • get_confidence_indexno sensitive capability
  • get_decision_evolutionno sensitive capability
  • get_decision_graphno sensitive capability
  • get_decision_logno sensitive capability
  • get_decisionsno sensitive capability
  • get_entity_knowledgeno sensitive capability
  • get_evolution_graphno sensitive capability
  • get_full_intelligenceno sensitive capability
  • get_handoff_injection_statusno sensitive capability
  • get_handoff_replayno sensitive capability
  • get_impact_graphno sensitive capability
  • get_intent_graphno sensitive capability
  • get_knowledge_healthno sensitive capability
  • get_memoryno sensitive capability
  • get_model_presetno sensitive capability
  • get_module_historyno sensitive capability
  • get_next_actionsno sensitive capability
  • get_project_changeno sensitive capability
  • get_project_contextno sensitive capability
  • get_project_decisionno sensitive capability
  • get_project_dnano sensitive capability
  • get_project_essenceno sensitive capability
  • get_project_graphno sensitive capability
  • get_project_graph_snapshotno sensitive capability
  • get_project_handoffno sensitive capability
  • get_project_historyno sensitive capability
  • get_project_identityno sensitive capability
  • get_project_impactno sensitive capability
  • get_project_intelligenceno sensitive capability
  • get_project_intelligence_healthno sensitive capability
  • get_project_intentno sensitive capability
  • get_project_intent_graphno sensitive capability
  • get_project_journeyno sensitive capability
  • get_project_knowledge_graphno sensitive capability
  • get_project_snapshotno sensitive capability
  • get_project_stateno sensitive capability
  • get_project_storyno sensitive capability
  • get_project_timelineno sensitive capability
  • get_project_whyno sensitive capability
  • get_provenance_chainno sensitive capability
  • get_recent_changesno sensitive capability
  • get_recent_eventsno sensitive capability
  • get_review_queueno sensitive capability
  • get_runtime_stateno sensitive capability
  • get_skill_suggestionsno sensitive capability
  • get_snapshotno sensitive capability
  • get_stability_indexno sensitive capability
  • get_state_conflictsno sensitive capability
  • get_suggested_questionsno sensitive capability
  • get_understanding_graphno sensitive capability
  • get_workspace_contextno sensitive capability
  • ignore_pending_decisionno sensitive capability
  • inspect_confidenceno sensitive capability
  • inspect_decisionno sensitive capability
  • inspect_evolutionno sensitive capability
  • inspect_graphno sensitive capability
  • inspect_healthno sensitive capability
  • inspect_impactno sensitive capability
  • inspect_intentno sensitive capability
  • inspect_pending_decisionsno sensitive capability
  • inspect_provenanceno sensitive capability
  • inspect_stateno sensitive capability
  • inspect_timelineno sensitive capability
  • inspect_whyno sensitive capability
  • note_change_eventno sensitive capability
  • prepare_execution_contextno sensitive capability
  • record_project_intentno sensitive capability
  • resolve_scope_contextno sensitive capability
  • review_decisionsno sensitive capability
  • review_pending_decisionsno sensitive capability
  • run_decision_evolutionno sensitive capability
  • search_memoryno sensitive capability
  • set_cognitive_modeno sensitive capability
  • set_decision_lifecycle_metano sensitive capability
  • skip_handoff_injectionno sensitive capability
  • store_memoryno sensitive capability
  • test_ai_connectionno sensitive capability
  • transfer_contextno sensitive capability
  • transfer_handoffno sensitive capability
  • transfer_intelligenceno sensitive capability
  • transfer_projectno sensitive capability
  • transfer_runtimeno sensitive capability
  • transfer_storyno sensitive capability
  • update_project_intentno sensitive capability

What this scan could not see

Versions 4

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 A 93/100 3 1.13.0 2026-09-07
v1.2.9 A 93/100 3 1.12.1 2026-07-27
v1.2.8 A 93/100 3 1.10.0 2026-07-25
v1.2.7 A 100/100 7 1.5.0 2026-07-22

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/contorium-mcp/badge.svg)](https://mcptrustchecker.com/registry/contorium-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/contorium-mcp"><img src="https://mcptrustchecker.com/registry/contorium-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/contorium-mcp/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 @contorium/mcp --online

Use the free API → How scoring works

More in Business & CRM