Should my agent depend on the MCP server ai.thinkneo/control-plane?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

ThinkNEO Control Plane

ai.thinkneo/control-plane

Enterprise AI Control Plane: governance, guardrails, spend tracking, compliance & smart routing.

— the operator's own registry description reported

Publisher ai.thinkneo · first seen 2026-08-12 · endpoint https://mcp.thinkneo.ai/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.775 (unusual). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency91 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools68

vs populationhigh

capabilities6

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_6f9d5cb7e6607e987e6615da · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

thinkneo_a2a_audit thinkneo_a2a_flow thinkneo_a2a_log thinkneo_a2a_policy thinkneo_agent_roi thinkneo_alert_rule_create thinkneo_alert_rule_delete thinkneo_alert_rule_list thinkneo_alert_rule_test thinkneo_audit_export thinkneo_benchmark_compare thinkneo_benchmark_report thinkneo_bridge_a2a_to_mcp thinkneo_bridge_generate_agent_card thinkneo_bridge_list_mappings thinkneo_bridge_mcp_to_a2a thinkneo_business_impact thinkneo_cache_status thinkneo_check thinkneo_check_pii_international thinkneo_check_policy thinkneo_check_spend thinkneo_compare_models thinkneo_complete thinkneo_compliance_generate thinkneo_count_tokens thinkneo_decision_cost thinkneo_detect_injection thinkneo_detect_waste thinkneo_end_trace thinkneo_evaluate_guardrail thinkneo_evaluate_trust_score thinkneo_get_budget_status thinkneo_get_compliance_status thinkneo_get_observability_dashboard thinkneo_get_proof thinkneo_get_savings_report thinkneo_get_trace thinkneo_get_trust_badge thinkneo_list_alerts thinkneo_log_decision thinkneo_log_event thinkneo_log_risk_avoidance thinkneo_manage_secrets thinkneo_optimize_prompt thinkneo_provider_status thinkneo_read_memory thinkneo_register_claim thinkneo_registry_get thinkneo_registry_install thinkneo_registry_publish thinkneo_registry_review thinkneo_registry_search thinkneo_rotate_key thinkneo_route_model thinkneo_router_explain thinkneo_schedule_demo thinkneo_set_baseline thinkneo_simulate_savings thinkneo_sla_breaches thinkneo_sla_dashboard thinkneo_sla_define thinkneo_sla_status thinkneo_start_trace thinkneo_usage thinkneo_verification_dashboard thinkneo_verify_claim thinkneo_write_memory

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	68/68	✓
has a description	68/68	✓
description is substantive	67/68	67/68
parameters are typed	68/68	✓
parameters are described	68/68	✓

68 of 68 tools graded · 68 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.28.0

server version ThinkNEO Control Plane

Capabilities: completions experimental logging prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:57:41Z	ok_tools	200	91	2025-06-18
2026-08-12T05:32:59Z	ok_tools	200	127	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/ai.thinkneo/control-plane.svg)](https://robinsaige.com/s/ai.thinkneo/control-plane)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview