mcp.immostage.ai/api
https://mcp.immostage.ai/api/mcp
81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1d 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 | 1d ago | 9dd21780b1d92bb4… |
| http_response_observation | 1d ago | 022f6324f9b12abc… |
| availability_observation | 1d ago | 4cc2f2d82bcb1189… |
| hosting_provider_observation | 1d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 1d ago | 02f340fdb41faceb… |
| oauth_metadata_observation | 1d ago | 3282826827707a29… |
| mcp_protocol_observation | 1d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.immostage.ai/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.