mcp.thinkneo.ai
https://mcp.thinkneo.ai/mcp
82
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 4d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
Findings (1)
| medium | Capabilities are listable without authentication, including 5 whose names suggest state change (thinkneo_alert_rule_create, thinkneo_alert_rule_delete, thinkneo_registry_publish, …) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 4d ago | 0eef10818e44611e… |
| http_response_observation | 4d ago | 0ace2f8794388b1b… |
| availability_observation | 4d ago | 0c9cbe6d45e11c7b… |
| tls_certificate_observation | 4d ago | 2b48502aa3966021… |
| oauth_metadata_observation | 4d ago | dc93cb274c79ce50… |
| mcp_protocol_observation | 4d ago | c19077b3d23c4d5d… |
| mcp_capability_observation | 4d ago | 3862ecf99ba7f589… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.thinkneo.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.