Ccs runs on your own machine — the client starts it, so there is no endpoint to ping.
Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.
The linked repository no longer exists on GitHub — it was deleted or made private.
What the code does
We have not read this server's code yet
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет ccs-mcp-server ссылается на dshcorrectover/ccs-mcp-server
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Ccs
same job, measured the same wayRuntime verification for agent tool calls: Ed25519 signed receipts, fail-closed RCE/SSRF checks.
Counter-signed evidence records for agent commerce: receipts, verification, dispute envelopes.
Fail-closed Cedar policy gate + Ed25519 signed receipts for agent tool calls. Denies on any error.
Fail-closed action authorization, MCP risk scanning, x402 checks, and signed receipts.
Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.
Independent effect verification and signed receipts for consequential AI agent actions.
Trust checks for MCP servers: trust scores, tool-drift detection, signed diligence receipts. Free.
Governance layer for agentic AI — signed, verifiable receipts for every agent action.
Ccs — questions
Answers built from our own checks of this server.