git.top/mcp/core
https://git.top/mcp/core
58
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 3h ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| mcp.tool_schema_changed | -3 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (2)
| low | Input schema changed without a name change: get_project mcp.tool_schema_changed @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (9)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 3h ago | 1810efbc8d95807d… |
| http_response_observation | 3h ago | 3ce22270bc926746… |
| availability_observation | 3h ago | e2127360b09b1ea5… |
| hosting_provider_observation | 3h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 3h ago | bb91ab106e418167… |
| oauth_metadata_observation | 3h ago | 19c3b463c01a93b1… |
| mcp_protocol_observation | 3h ago | 39ce0946dc8e8107… |
| mcp_capability_observation | 3h ago | 906a02163bbb2862… |
| mcp_capability_drift | 3h ago | e61a7593d2f6da1c… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of git.top/mcp/core to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.