statement-normalizer.mcpize.run
https://statement-normalizer.mcpize.run/
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 | f948d9ed8ef9a475… |
| http_response_observation | 1d ago | ca776145697a57c6… |
| availability_observation | 1d ago | 166b6f3d60fdf665… |
| hosting_provider_observation | 1d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1d ago | cc68fcbf74ac25ed… |
| oauth_metadata_observation | 1d ago | 39401e2b923fd677… |
| 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 statement-normalizer.mcpize.run to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.