mcp.certman.app
https://mcp.certman.app/
81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | c3afb4c78dfb090d… |
| http_response_observation | 2d ago | b099c0ce6a2dcc84… |
| availability_observation | 2d ago | c2a6efdb14613b1e… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | b2dfee5685e92f37… |
| oauth_metadata_observation | 2d ago | 35af43f88c898e7d… |
| mcp_protocol_observation | 2d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.certman.app to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.