wingmanprotocol.com
https://wingmanprotocol.com/mcp
82
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
Findings (1)
| medium | Capabilities are listable without authentication, including 8 whose names suggest state change (browse_close, cancel_watch, create_watch, …) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 707bdfc398bfcf31… |
| http_response_observation | 2d ago | c378a5e10e4205d6… |
| availability_observation | 2d ago | 33d2bc84afe5d2b8… |
| tls_certificate_observation | 2d ago | 28525e99a71853f5… |
| oauth_metadata_observation | 2d ago | db09179bac4ab921… |
| mcp_protocol_observation | 2d ago | 808a3cf18796a824… |
| mcp_capability_observation | 2d ago | 63f5af636d47cae8… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of wingmanprotocol.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.