flingflyers.com
https://flingflyers.com/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (2)
| medium | Capabilities are listable without authentication, including 3 whose names suggest state change (publish_flyer, revoke_flyer, update_flyer) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 1b291bbf7bbfb951… |
| http_response_observation | 2d ago | a42fb32b695a10c8… |
| availability_observation | 2d ago | 726fded1b8004e25… |
| tls_certificate_observation | 2d ago | 7419c2c2a4757803… |
| oauth_metadata_observation | 2d ago | e596962b63a3f663… |
| mcp_protocol_observation | 2d ago | 06407e0188ae56b8… |
| mcp_capability_observation | 2d ago | e24a3fa034044d62… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of flingflyers.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.