huggingbay.xyz/api
https://huggingbay.xyz/api/mcp
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1d 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 | 1d ago | d536201033fdafe8… |
| http_response_observation | 1d ago | f1a14313a5296c6a… |
| availability_observation | 1d ago | 00799b9fdbbd24af… |
| hosting_provider_observation | 1d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1d ago | 0dbc2a9cfd03ae59… |
| oauth_metadata_observation | 1d ago | 4a86f9bb99f8acda… |
| mcp_protocol_observation | 1d ago | 2beeed3853921f23… |
| mcp_capability_observation | 1d ago | b52834444d9e6f19… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of huggingbay.xyz/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.