mcp.eztexting.com/mcp/contacts
https://mcp.eztexting.com/mcp/contacts
82
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1h 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 3 whose names suggest state change (contact_delete, contact_field_delete, contact_group_delete) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1h ago | 0f4b590c89d74718… |
| http_response_observation | 1h ago | 1a48d99d27f84a92… |
| availability_observation | 1h ago | e6ae7b8ccc1eabc1… |
| tls_certificate_observation | 1h ago | 9bb2df23e347f859… |
| oauth_metadata_observation | 1h ago | e938372370977d1e… |
| mcp_protocol_observation | 1h ago | 28b3eb2eeb9de184… |
| mcp_capability_observation | 1h ago | 680396757d736b5b… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.eztexting.com/mcp/contacts to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.