mcpcheckup.xyz/api
https://mcpcheckup.xyz/api/mcp
53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (create_scorecard) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 5a9d4080dc7498a3… |
| http_response_observation | 1d ago | ab60eab41a232344… |
| availability_observation | 1d ago | 563af179f95b8d3d… |
| hosting_provider_observation | 1d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 1d ago | 302273dd7c84c4d2… |
| oauth_metadata_observation | 1d ago | 41f5ef84f457ea97… |
| mcp_protocol_observation | 1d ago | 944a6da926fd65be… |
| mcp_capability_observation | 1d ago | 9fcba00f9bfe0e8a… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcpcheckup.xyz/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.