mcp.sentinelsignal.io
https://mcp.sentinelsignal.io/mcp
82
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
Findings (1)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (submit_feedback) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 7b13b21d0fdcd22b… |
| http_response_observation | 2d ago | e5dcea320e703634… |
| availability_observation | 2d ago | 53ffe8d28ffaf8f6… |
| tls_certificate_observation | 2d ago | 6bc4a2e8a6757117… |
| oauth_metadata_observation | 2d ago | f6a420cb24c33d5e… |
| mcp_protocol_observation | 2d ago | 098dfd7c9c278d6c… |
| mcp_capability_observation | 2d ago | 4e1426482d98c14d… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.sentinelsignal.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.