mcp.boundr.dev
https://mcp.boundr.dev/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 | 88678e4d99ffeeb2… |
| http_response_observation | 2d ago | 545738b8a68131a5… |
| availability_observation | 2d ago | 81a3453364c222c7… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 3275ec6a5bdfe7ae… |
| oauth_metadata_observation | 2d ago | 724fe2d812e8bb53… |
| mcp_protocol_observation | 2d ago | 16d183ce547bd217… |
| mcp_capability_observation | 2d ago | 84ba43e87bddc36c… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.boundr.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.