caper.network/api
https://caper.network/api/mcp
53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (2)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (submit_tx) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 8590e1543d0100f6… |
| http_response_observation | 2d ago | 705388122f3d0434… |
| availability_observation | 2d ago | ba145aac36cec799… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | 8eaf5327effa852a… |
| oauth_metadata_observation | 2d ago | 3a001be27026970a… |
| mcp_protocol_observation | 2d ago | 0e5c028a2d24f9dd… |
| mcp_capability_observation | 2d ago | 59fd6cb716e261bf… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of caper.network/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.