mcp.bosonprotocol.io
https://mcp.bosonprotocol.io/mcp
53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d 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 20 whose names suggest state change (approve_exchange_token, cancel_voucher, create_buyer, …) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | c9030354c7ee6c0e… |
| http_response_observation | 1d ago | e96f40d797163c60… |
| availability_observation | 1d ago | 319acd905323d17b… |
| hosting_provider_observation | 1d ago | 958411567b2d9bdc… |
| tls_certificate_observation | 1d ago | b456449779547764… |
| oauth_metadata_observation | 1d ago | 66e53eaabf3f267a… |
| mcp_protocol_observation | 1d ago | 7ff176fa6a22db70… |
| mcp_capability_observation | 1d ago | 4b4a7f8997e49103… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.bosonprotocol.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.