mcp.windowsforum.com
https://mcp.windowsforum.com/
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (get_post) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 6e9d67fec40d3cdf… |
| http_response_observation | 2d ago | 76425a55bd17d65c… |
| availability_observation | 2d ago | b1267f81d4fd8dd6… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 4691775983f4fac9… |
| oauth_metadata_observation | 2d ago | 2fd070b9c38d47b9… |
| mcp_protocol_observation | 2d ago | e85ed3b571c01b46… |
| mcp_capability_observation | 2d ago | 5eeda86316549351… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.windowsforum.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.