taskman.london
https://taskman.london/mcp
53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1h ago
Why this score
| 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 3 whose names suggest state change (create_booking_request, create_customer_booking, update_contact_note) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1h ago | 80fa678851537370… |
| http_response_observation | 1h ago | 09cd9f711705718e… |
| availability_observation | 1h ago | 58bfd1738b388b66… |
| hosting_provider_observation | 1h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1h ago | 8851d4884d00942a… |
| oauth_metadata_observation | 1h ago | 237f8d6d66e1b907… |
| mcp_protocol_observation | 1h ago | 55b821c519836e52… |
| mcp_capability_observation | 1h ago | 665489f3ebde50f9… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of taskman.london to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.