Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/CNSLabs/agreements-api-sdkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/cnslabs/agreements-api-sdk/agreements-mcp-server-agreements)<a href="https://agentmods.dev/mcp/cnslabs/agreements-api-sdk/agreements-mcp-server-agreements"><img src="https://agentmods.dev/badge/mcp/cnslabs/agreements-api-sdk/agreements-mcp-server-agreements/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/cnslabs/agreements-api-sdk/agreements-mcp-server-agreements"><img src="https://agentmods.dev/badge/mcp/cnslabs/agreements-api-sdk/agreements-mcp-server-agreements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agreements scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"agreements": {
"url": "https://shodai.network/mcp",
"type": "streamable-http"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 6 lines scan A 66f5391180d4
agreements is an MCP server published in the GitHub repository CNSLabs/agreements-api-sdk (2 stars, last pushed 17d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
causallayer-mcp
Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split. Remote server at causallayer-mcp-demo.zykm9qkk7j.workers.dev.
causallayer
Deterministic AI liability attribution with Bitcoin-anchored proof certificates. Runs locally from the causallayer-mcp npm package.
copilot-mcp
Web3 founder diligence: code audit, jurisdiction, fund matching, portfolio, scoring. Runs locally from the @apexfdn/copilot-mcp npm package. Needs 2 environment variables to run.
mica-crypto-mcp
Markets in Crypto-Assets (MiCA) Regulation (EU) 2023/1114 compliance for EU crypto-asset issuers, exchanges, custodians, and CASPs. Runs locally from the mica-crypto-mcp Python package.
mcp-server
Blockchain-anchored e-signatures: send envelopes, manage templates, verify anchors on Solana. Runs locally from the @signatrust/mcp-server npm package. Needs 2 environment variables to run.
compliance
Pay-per-call compliance via x402: wallet sanctions, OFAC name, UK + US company verification. Remote server at mcp.onchaindiligence.com.