api.healthparse.io
https://api.healthparse.io/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 |
|---|---|---|
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| dns_resolution_observation | 2d ago | 3730b487e32f6901… |
| http_response_observation | 2d ago | 681178c55ceaea6b… |
| availability_observation | 2d ago | 3d8e818e7a872d3f… |
| tls_certificate_observation | 2d ago | 2c9c46b0001bef90… |
| oauth_metadata_observation | 2d ago | e133e06d39178049… |
| mcp_protocol_observation | 2d ago | 1825536902b84d3e… |
| mcp_capability_observation | 2d ago | 7052c66adb3287e7… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.healthparse.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.