api.m2mcent.com/bid-clarification-q-and-a-mcp
https://api.m2mcent.com/bid-clarification-q-and-a-mcp/sse
75
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 | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | a3b9f45f1a3e894d… |
| http_response_observation | 2d ago | eabc974d4ea74840… |
| availability_observation | 2d ago | 2f7b9552528fd31a… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | e02ed8490b87e88c… |
| oauth_metadata_observation | 2d ago | e7a89ca65ae221fa… |
| mcp_protocol_observation | 2d ago | 928a15841195af03… |
| mcp_capability_observation | 2d ago | 7ceb56d48b6bd14e… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.m2mcent.com/bid-clarification-q-and-a-mcp to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.