ThinkNEO Control Plane
REMOTE · MCP.THINKNEO.AI
Enterprise AI Control Plane: governance, guardrails, spend tracking, compliance & smart routing.
Available components
Last scanned (13 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 16 Oct 2026.
Category Security
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://mcp.thinkneo.ai/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of mcp.thinkneo.ai. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| mcp.thinkneo.ai. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.thinkneo.ai/mcp | Unreachable | ||
| http (plaintext) | http://mcp.thinkneo.ai/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
thinkneo_registry_publish ~288
Publish an MCP server to the ThinkNEO Marketplace. Validates the endpoint by calling initialize and tools/list, runs automated security scan for secrets and injection patterns, computes a security score (0-100), and stores the entry with version history. Validates the endpoint (calls initialize + tools/list), runs security scan (secrets detection, injection patterns), and stores the entry. Authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | – | – | Categories: governance, security, data, development, productivity, communication, analytics, devops, finance, marketing, other |
| description | string | yes | Short description of what this MCP server does (max 500 chars) |
| display_name | string | yes | Human-readable display name |
| endpoint_url | string | yes | MCP server endpoint URL (e.g. https://my-server.com/mcp) |
| license | string | – | License (e.g. MIT, Apache-2.0) |
| name | string | yes | Package name (lowercase, hyphens allowed, e.g. 'my-mcp-server') |
| readme | string | – | Full readme/documentation in markdown |
| repo_url | string | – | Source code repository URL |
| tags | – | – | Tags for discoverability (e.g. ['ai', 'governance', 'security']) |
| transport | string | – | Transport type: streamable-http, sse, or stdio |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_registry_review ~121
Rate and review an MCP server in the ThinkNEO Marketplace. One review per user per package (updates on repeat). Rating from 1 (poor) to 5 (excellent) with optional comment. Reviews affect the package average rating shown in search results. One review per user per package (updates on repeat). Authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Review comment (max 2000 chars) |
| name | string | yes | Package name to review |
| rating | integer | yes | Rating from 1 (poor) to 5 (excellent) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_registry_search ~162
Search the ThinkNEO MCP Marketplace — the npm for MCP tools. Discover MCP servers and tools by keyword, category, rating, or verified status. Returns name, description, tools count, rating, downloads, and verified badge. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | Filter by category: governance, security, data, development, productivity, communication, analytics, devops, finance, marketing, other |
| limit | integer | – | Max results to return (1-100, default 20) |
| min_rating | – | – | Minimum average rating (1.0-5.0) |
| query | string | – | Search query — matches name, description, tags, and tool names |
| verified_only | boolean | – | If true, return only verified packages |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_rotate_key ~37
Instruct the gateway to rotate an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| key_prefix | string | yes | First 8 chars of the key to rotate |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_route_model ~255
AI Smart Router — find the cheapest model that meets your quality threshold. Specify your task type and quality requirements, and ThinkNEO will recommend the optimal model with estimated cost and savings vs premium models. Supports 17+ models across Anthropic, OpenAI, Google, Meta, Mistral, DeepSeek, Alibaba, Cohere, and xAI. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_per_request | – | – | Maximum budget per request in USD. Omit for no limit. |
| estimated_tokens | integer | – | Estimated total tokens for the request (input + output). Default 1000. |
| max_latency_ms | – | – | Maximum acceptable latency in milliseconds. Omit for no limit. |
| preferred_providers | – | – | Comma-separated list of preferred providers (e.g., 'openai,anthropic'). These will be prioritized at similar cost. |
| quality_threshold | integer | – | Minimum quality score required (0-100). Default 85 = enterprise-grade. |
| task_type | string | yes | The type of AI task: summarization, classification, code_generation, chat, analysis, translation, or embedding |
| text_sample | – | – | Optional sample text for better routing. Helps estimate token count and task complexity. Max 500 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_router_explain ~101
Explain why the Smart Router would choose a specific model for a task type. Shows both benchmark-based (real outcomes) and static quality estimates, and explains the reasoning behind the recommendation. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| quality_threshold | integer | – | Minimum quality score required (0-100, default 85) |
| task_type | string | yes | Task type: 'summarization', 'code_generation', 'classification', 'translation', 'analysis', 'chat' |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_schedule_demo ~178
Schedule a demo or discovery call with the ThinkNEO team. Collects contact information and preferences. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company or organization name |
| contact_name | string | yes | Full name of the person requesting the demo |
| context | – | – | Additional context such as current AI providers used, request volume, or specific use case |
| string | yes | Business email address to receive follow-up from the ThinkNEO team | |
| interest | – | – | Primary area of interest: guardrails, finops, observability, governance, or full platform |
| preferred_dates | – | – | Preferred meeting dates, times, and timezone (e.g., 'Tuesdays or Thursdays, 9-11am EST') |
| role | – | – | Contact's role: cto, cfo, security, engineering, or other |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_set_baseline ~199
Define the pre-AI cost baseline for a business process. Example: 'customer_support_ticket costs $12 per ticket and takes 15 minutes without AI'. This baseline is used to calculate ROI when agents handle the same process. Call this once per process to establish the comparison point.
| Name | Type | Req | Description |
|---|---|---|---|
| avg_duration_minutes | – | – | Average time in minutes for one unit without AI, e.g. 15 |
| cost_per_unit_usd | number | yes | Pre-AI cost per unit in USD, e.g. 12.00 for a $12 support ticket |
| notes | – | – | Additional context about this baseline |
| process_name | string | yes | Name of the business process, e.g. 'customer_support_ticket', 'loan_review', 'content_moderation' |
| unit_label | string | – | What one unit represents, e.g. 'ticket', 'review', 'decision', 'document' |
| workspace | string | – | Workspace identifier |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_simulate_savings ~221
Simulate how much your organization would save on AI costs using ThinkNEO Smart Router. Enter your current monthly AI spend and primary model, and see estimated monthly and annual savings with a recommended model mix. No authentication required — try it now!
| Name | Type | Req | Description |
|---|---|---|---|
| monthly_ai_spend | number | yes | Your current monthly AI API spend in USD (e.g., 5000.00) |
| primary_model | string | – | Your primary model: 'gpt-4o', 'claude-opus-4', 'claude-sonnet-4', 'gpt-4.1', or 'gemini-2.5-pro' |
| task_distribution | – | – | JSON string of task distribution, e.g., '{"chat": 0.3, "summarization": 0.2, "code_generation": 0.2, "classification": 0.15, "analysis": 0.1, "translation": 0.05}'. Values should sum to ~1.0. Omit fo… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_sla_breaches ~65
View SLA breach history — which SLAs were breached, by which agents, actual vs threshold values, and resolution status. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | – | – | Filter by agent name |
| days | integer | – | Days to look back (default 30) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_sla_dashboard ~42
SLA overview dashboard — all agents, current status, error budgets, and recent breaches (7d). The SRE dashboard for AI agents. Requires authentication.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_sla_define ~284
Define or update an SLA (Service Level Agreement) for an AI agent. Set accuracy, quality, cost, safety, or latency thresholds with automatic breach detection and configurable actions (alert, escalate, disable, switch_model). Like SRE SLOs but for AI agent outcomes. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | Agent name to set SLA for (e.g., 'support-bot', 'finance-agent') |
| breach_action | string | – | Action on breach: 'alert' (notify), 'escalate' (notify + flag), 'disable' (stop agent), 'switch_model' (fallback model) |
| metric | string | yes | Metric to monitor: 'accuracy' (outcome verification rate %), 'response_quality' (avg quality score), 'cost_efficiency' (cost per verified outcome), 'safety' (guardrail pass rate %), 'latency' (avg re… |
| threshold | number | yes | Target threshold value (e.g., 95.0 for 95% accuracy) |
| threshold_direction | string | – | 'min' = actual must be >= threshold (for accuracy, quality). 'max' = actual must be <= threshold (for cost, latency). |
| window | string | – | Rolling window: '1h', '24h', '7d', or '30d' |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_sla_status ~65
Check current SLA status for all agents or a specific agent. Shows actual metric values vs thresholds, healthy/breached status, and error budget remaining. Automatically records breaches. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | – | – | Optional: specific agent name. Leave empty for all agents. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_start_trace ~143
Start a new agent observability trace. Creates a session that tracks all tool calls, model calls, decisions, and errors for an AI agent run. Returns a session_id to use with thinkneo_log_event and thinkneo_end_trace. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | Name of the agent being traced (e.g., 'marketing-agent', 'support-bot') |
| agent_type | string | – | Type of agent: 'assistant', 'autonomous', 'workflow', 'pipeline', or 'generic' |
| metadata | – | – | Optional dict with additional context (e.g., {"task": "email-draft", "user_id": "u123"}) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_usage ~55
Returns usage statistics for your ThinkNEO API key. Shows calls today, this week, this month, monthly limit, remaining calls, top tools used, estimated cost, and current tier. Works without authentication (returns general info).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_verification_dashboard ~75
Aggregated outcome verification metrics — verification rates, failure patterns, agent reliability rankings, and daily trends. Shows how reliably your AI agents are delivering verified outcomes. 'Datadog for AI outcomes'. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Time period: '24h', '7d', or '30d' |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_verify_claim ~111
Trigger verification of a registered action claim. Runs the appropriate verification adapter (HTTP check, file check, database check, etc.) and returns the result with evidence. If already verified, returns cached result (use force=true to re-verify). Part of the Outcome Validation Loop — 'From Prompt to Proof'. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_id | string | yes | UUID of the claim to verify (from thinkneo_register_claim) |
| force | boolean | – | Force re-verification even if already verified/failed |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
thinkneo_write_memory ~178
Write or update a Claude Code project memory file (.md). Persists project context, user preferences, feedback, and reference notes across Claude Code sessions. Filename must end in .md with lowercase alphanumeric characters. Path traversal is blocked. Requires authentication.Use this to persist project context, user preferences, feedback, and reference notes across Claude Code sessions. The filename must end in .md and contain only lowercase letters, digits, underscores, and hyphens (e.g. 'user_fabio.md', 'project_new_feature.md'). Path traversal is blocked.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Full markdown content to write to the file. |
| filename | string | yes | Name of the memory file to write (e.g. 'user_fabio.md', 'project_thinkneodo_droplet.md'). Must end in .md. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the ThinkNEO Control Plane MCP server?
ThinkNEO Control Plane is a hosted endpoint at https://mcp.thinkneo.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.thinkneo.ai
claude mcp add --transport http ai-thinkneo-control-plane 'https://mcp.thinkneo.ai/mcp'
What is the ThinkNEO Control Plane MCP server?
ThinkNEO Control Plane is an MCP server listed in the public MCP registry as ai.thinkneo/control-plane. Enterprise AI Control Plane: governance, guardrails, spend tracking, compliance & smart routing. This page covers its hosted endpoint (https://mcp.thinkneo.ai/mcp).
Is the ThinkNEO Control Plane MCP server safe to use?
ThinkNEO Control Plane scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ThinkNEO Control Plane MCP server expose?
ThinkNEO Control Plane exposes 68 tools: thinkneo_check_spend, thinkneo_complete, thinkneo_read_memory, thinkneo_write_memory, thinkneo_evaluate_guardrail, and 63 more. Their descriptions and schemas cost roughly 7,409 tokens of context every time the server is loaded.
Does the ThinkNEO Control Plane MCP server require authentication?
Its publisher declares no required credentials for ThinkNEO Control Plane. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the ThinkNEO Control Plane MCP server still maintained?
ThinkNEO Control Plane has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.