Contract Ops MCP Server
contract-ops-mcp
npm
v0.3.0
Source verified
Published by drbaher — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
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 − 6 = 94. 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 |
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 1
high Shell/command execution in server code (contract-ops-mcp.mjs)MTC-SRC-002
In the server's implementation (`contract-ops-mcp.mjs:20`): 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: { execFile } from "node:child_process"; import { resolve, sep, join } from "node:path"; import { realpathSync, mkdtempSy
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 contract-ops-mcp.mjs
Tools 50
Each tool and what it can reach — statically extracted from the published source.
audit_showno sensitive capabilitycatalogno sensitive capabilitycompare_versionsno sensitive capabilitycontract_vault_acceptno sensitive capabilitycontract_vault_at_riskno sensitive capabilitycontract_vault_dueno sensitive capabilitycontract_vault_exportno sensitive capabilitycontract_vault_ingestno sensitive capabilitycontract_vault_obligationno sensitive capabilitycontract_vault_obligationsno sensitive capability
Show 40 more tools ↓
contract_vault_queryno sensitive capabilitycontract_vault_remindno sensitive capabilitycontract_vault_reviewno sensitive capabilitycontract_vault_riskno sensitive capabilitycontract_vault_verifyno sensitive capabilityconvert_to_pdfno sensitive capabilitydraft_ndano sensitive capabilityextract_contractno sensitive capabilityfill_templateno sensitive capabilitygenerate_redlinesno sensitive capabilitylint_contractno sensitive capabilitynda_setupno sensitive capabilitynegotiate_acceptno sensitive capabilitynegotiate_analyzeno sensitive capabilitynegotiate_counterno sensitive capabilitynegotiate_diffno sensitive capabilitynegotiate_finalizeno sensitive capabilitynegotiate_initno sensitive capabilitynegotiate_reviewno sensitive capabilitynegotiate_statusno sensitive capabilitynegotiate_validateno sensitive capabilityreview_ndano sensitive capabilityrunno sensitive capabilitysuite_statusno sensitive capabilitytemplate_vault_clause_libraryno sensitive capabilitytemplate_vault_clausesno sensitive capabilitytemplate_vault_compare_clausesno sensitive capabilitytemplate_vault_composeno sensitive capabilitytemplate_vault_diffno sensitive capabilitytemplate_vault_exportno sensitive capabilitytemplate_vault_findno sensitive capabilitytemplate_vault_getno sensitive capabilitytemplate_vault_historyno sensitive capabilitytemplate_vault_infono sensitive capabilitytemplate_vault_listno sensitive capabilitytemplate_vault_statsno sensitive capabilitytemplate_vault_swapno sensitive capabilitytemplate_vault_verifyno sensitive capabilityverify_receiptno sensitive capabilityverify_signatureno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (50 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.3.0 latest |
A 94/100 | 1 | 1.8.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.
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 contract-ops-mcp --onlineMore in Developer Tools
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.