mcp.beycome.com
https://mcp.beycome.com/mcp
49
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 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (2)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (beycome_submit_property_link) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 837d2ab73536914d… |
| http_response_observation | 1d ago | 20da8cd8d0bcd28a… |
| availability_observation | 1d ago | 0494b8fcae9bb04f… |
| hosting_provider_observation | 1d ago | 958411567b2d9bdc… |
| tls_certificate_observation | 1d ago | c91d7842674bf636… |
| oauth_metadata_observation | 1d ago | e7e8d8ba0f3b56e0… |
| mcp_protocol_observation | 1d ago | 255c703dd3ed2f3b… |
| mcp_capability_observation | 1d ago | b627190d89d27976… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.beycome.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.