greatquestion.co/api/mcp/v1
https://greatquestion.co/api/mcp/v1
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 3h ago
Why this score
| 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 | 3h ago | 4e17db0bbc1eb872… |
| http_response_observation | 3h ago | d08decb9844543f6… |
| availability_observation | 3h ago | b7a867d08c4835e7… |
| hosting_provider_observation | 3h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 3h ago | 4533b2db93af27ab… |
| oauth_metadata_observation | 3h ago | 8a2fdc197e99efa1… |
| mcp_protocol_observation | 3h ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of greatquestion.co/api/mcp/v1 to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.