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/thinkneo-ai/mcp-serverWrote 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/thinkneo-ai/mcp-server/control-plane)<a href="https://agentmods.dev/mcp/thinkneo-ai/mcp-server/control-plane"><img src="https://agentmods.dev/badge/mcp/thinkneo-ai/mcp-server/control-plane/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/thinkneo-ai/mcp-server/control-plane"><img src="https://agentmods.dev/badge/mcp/thinkneo-ai/mcp-server/control-plane.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
control-plane 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 1mo 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
{
"control-plane": {
"url": "https://mcp.thinkneo.ai/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.
- 1mo ago First seen · 6 lines scan A d569643d1b85
control-plane is an MCP server published in the GitHub repository thinkneo-ai/mcp-server (3 stars, last pushed 3mo 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
mcp-smb-products
MCP server "mcp-smb-products", hosted remotely at mcp.thinkneo.app, as configured in thinkneo-ai/mcp-smb-products.
dingdawg-legal-agent
AI contract review, clause drafting, compliance checklists & legal research. Runs locally from the dingdawg-legal-agent npm package. Needs 1 environment variable to run.
peac
PEAC record operations as MCP tools (verify, inspect, decode, issue, bundle). Runs locally from the @peac/mcp-server npm package.
model-ledger
Developer-first model inventory and governance framework for SR 11-7, EU AI Act, and NIST AI RMF compliance. Runs locally from the model-ledger Python package.
mcp-eu-ai-act
EU AI Act + GDPR compliance scanner. One call, no arguments, 10 seconds. 22 AI frameworks detected. Remote server at mcp.arkforge.tech.
complyedge
Runtime EU AI Act deny for agent I/O (Article 5, Article 50) — ComplyEdge Python SDK. Runs locally from the complyedge Python package.