erikbethke.com/api
https://erikbethke.com/api/mcp
68
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| 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 2 whose names suggest state change (get_blog_post, sign_guestbook) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | f744e13cf8b0e36a… |
| http_response_observation | 2d ago | 4d314324373a8b48… |
| availability_observation | 2d ago | 4e25c5f5159b79e7… |
| tls_certificate_observation | 2d ago | 327e8b910d2b095e… |
| oauth_metadata_observation | 2d ago | 18dd328b380c7002… |
| mcp_protocol_observation | 2d ago | 3f01c8df8230ddcf… |
| mcp_capability_observation | 2d ago | bb5bfc7a694fe057… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of erikbethke.com/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.