receipts-mcp.vercel.app/api
https://receipts-mcp.vercel.app/api/mcp
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1d 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 | 1d ago | b03fef51ee1729bb… |
| http_response_observation | 1d ago | e9552f7658278a74… |
| availability_observation | 1d ago | 5d56f42212e1554e… |
| hosting_provider_observation | 1d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 1d ago | c56037c91c742c74… |
| oauth_metadata_observation | 1d ago | 221f16ec6432e86d… |
| mcp_protocol_observation | 1d ago | 66ae84325176ae7e… |
| mcp_capability_observation | 1d ago | f42501dcc6847323… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of receipts-mcp.vercel.app/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.