pody.io/api
https://pody.io/api/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 4f464bba8735a89e… |
| http_response_observation | 2d ago | 5348dfb2469c5e6b… |
| availability_observation | 2d ago | 86084c9d00f2ba95… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | e5664d8dc0e09cf0… |
| oauth_metadata_observation | 2d ago | 23f32ac87fd2fb80… |
| mcp_protocol_observation | 2d ago | fd8d42fc88bd7cf7… |
| mcp_capability_observation | 2d ago | c60358047d70ddc4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of pody.io/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.