atx/registry

mcp.eztexting.com/mcp/contacts

https://mcp.eztexting.com/mcp/contacts

75
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
mcp_capabilities_discoverable+4
headers.missing_hsts-3

Findings (2)

mediumCapabilities 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
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation2d ago0f4b590c89d74718…
http_response_observation2d agob62e6568906e868d…
availability_observation2d agofcb22196188dd3bd…
tls_certificate_observation2d agofb96695f7e7dabb0…
oauth_metadata_observation2d agoe938372370977d1e…
mcp_protocol_observation2d agof55776ae2cae491f…
mcp_capability_observation2d agof25a1add7f8943a3…

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.

Claim this profile →