whycantwehaveanagentforthis.com/api
https://whycantwehaveanagentforthis.com/api/mcp
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 6d ago
Why this score
| oauth_metadata_present | +14 |
| 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 | 6d ago | 106f3232c8807719… |
| http_response_observation | 6d ago | 9f283b9c954dc29f… |
| availability_observation | 6d ago | ba145aac36cec799… |
| hosting_provider_observation | 6d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 6d ago | 6bdd259097cafdb7… |
| oauth_metadata_observation | 6d ago | e96d7acf7156a7a8… |
| mcp_protocol_observation | 6d ago | 66ae84325176ae7e… |
| mcp_capability_observation | 6d ago | 38766854a3905dc0… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of whycantwehaveanagentforthis.com/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.