mcp.capmus.com
https://mcp.capmus.com/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 2 whose names suggest state change (create_post, send_message) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 07c7c87ad1f4d33e… |
| http_response_observation | 1d ago | 5bb56b6a13db19df… |
| availability_observation | 1d ago | fb7e7d4268a8210e… |
| hosting_provider_observation | 1d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 1d ago | b22d01b6abd08c93… |
| oauth_metadata_observation | 1d ago | 66db05d013d5c12f… |
| mcp_protocol_observation | 1d ago | 1a1e66f11961feb6… |
| mcp_capability_observation | 1d ago | 828c64bddd3d037f… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.capmus.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.