
ThinkNEO Control Plane
ai.thinkneoPublished by thinkneo.aiOfficial publisherv1.29.0Updated Oct 24, 2026
Enterprise AI Control Plane: governance, guardrails, spend tracking, compliance & smart routing.
Overview
A remote MCP server for enterprise AI governance, offering 72 tools for guardrails, spend tracking, routing, observability, compliance and security.
- What you can do
- Apply governance and guardrail checks, policy engine rules and trust scoring to AI usage and agent activity, with prompts for governance audits and policy preflight checks. Track spend and cost (FinOps), route requests to providers and models, and manage a provider/model registry. Monitor usage and observability, validate outcomes, benchmark agents, and export audit records. Run security detection through ThinkShield rule packs covering injection, auth abuse, recon and header anomalies. Bridge MCP to Google's A2A protocol with agent control skills, plus caching, memory, scheduling and alerts tools.
- When to use it
- Useful when an organization wants an assistant to apply policy, guardrail and spend controls around AI and agent activity, or to inspect governance, compliance and security signals from one endpoint. Less relevant for individual users who only need general-purpose tools.
- Requirements
- Remote streamable HTTP endpoint at mcp.thinkneo.ai; no authentication, environment variables or headers are declared in the manifest. The README mentions a free tier of 500 calls per month with an auto-provisioned API key, and a self-hosted option via git clone, pip install and uvicorn or Docker.
Installation
In SourceWeft
- Open ThinkNEO Control Plane in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.thinkneo%2Fcontrol-plane/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"thinkneo-control-plane": {
"type": "http",
"url": "https://mcp.thinkneo.ai/mcp"
}
}
}README
ThinkNEO MCP Server
Open MCP server with built-in defense layer (ThinkShield). Part of the ThinkNEO Platform — enterprise AI governance.
[License: Apache-2.0] [MCP Protocol] [A2A Protocol] [Tools] [A2A Skills] [Glama AAA] [Tests]
What This Is
An open-source MCP server providing 72 tools for AI governance, observability, and security:
- ThinkShield — Production defense layer: detection engine, 5 rule packs, runtime middleware. 145 tests, p99 < 1ms.
- 72 MCP Tools — Governance, guardrails, FinOps, smart routing, observability, compliance, outcome validation, and more.
- 24 A2A Skills — Bidirectional MCP-A2A bridge for Google's Agent-to-Agent Protocol (v0.3.0, Linux Foundation).
- Apache-2.0 — Use it, fork it, contribute.
What This Is Not
- Not the full ThinkNEO Platform. Governance orchestration, cryptographic audit chain, tenant management, and enterprise integrations are proprietary and run at thinkneo.ai.
- Not a standalone security product. ThinkShield is the defense component of a larger governed platform.
Why Open
We open-source our defense layer because real security doesn't depend on hidden rules — it depends on tested, audited, continuously improved detection plus a strong governance moat around it.
Snort. Suricata. Falco. OWASP CRS. The security industry runs on open detection. We follow that tradition.
The detection is open. The governance is proprietary. That's where the moat is.
Architecture
Quickstart
Or with Docker:
Connect from Claude Desktop, Cursor, or any MCP client:
Free tier: 500 calls/month, auto-provisioned API key. All 72 tools available.
Components
ThinkShield Rule Packs
MCP Tools (72)
Governance (6) | Guardrails (3) | FinOps (4) | Smart Router (4) | Trust Score (2) | Registry (5) | Bridge (4) | Observability (5) | Business Value (6) | A2A Control (4) | Optimization (1) | Outcome Validation (4) | Policy Engine (4) | Benchmarking (3) | Compliance (2) | Agent SLA (4) | Audit Export (3) | Cache (3) | Security (5) | Tokens (1) | Memory (2) | Scheduling (1) | Alerts (1)
Full tool reference: docs/quickstart.md
MCP Spec Compliance
Complete Model Context Protocol 2024-11-05 implementation. Forward-compatible with MCP 2025-03-26.
Ecosystem
This repo is part of the ThinkNEO ecosystem:
Security
See SECURITY.md for vulnerability reporting.
Contributing
See CONTRIBUTING.md.
Related
License
Apache-2.0 — see LICENSE.
About
ThinkNEO AI Technology Co., Ltd. — Hong Kong CR No. 2296774.
Built by the team behind the ThinkNEO Enterprise AI Control Plane, AIRGP protocol, and A2ASTC conformance suite.
Source: README.md at commit 0f014e1
Tools
0Version history
1- v1.29.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts