api.regfish.com
https://api.regfish.com/mcp
88
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| mcp_requires_authentication | +10 |
| tls.cert_expiring_soon | -8 |
| reachable | +6 |
| hsts_enabled | +4 |
Findings (2)
| medium | TLS certificate expires in 20 days tls.cert_expiring_soon @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 1f8c78af91a3eb2c… |
| http_response_observation | 2d ago | 1f1015af018d723b… |
| availability_observation | 2d ago | b39ca816d56ca30e… |
| tls_certificate_observation | 2d ago | 505f70a7ec42ec2a… |
| oauth_metadata_observation | 2d ago | 443dbf8e8ff8beaf… |
| 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 api.regfish.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.