atx/registry

mcp.eztexting.com/mcp/messaging

https://mcp.eztexting.com/mcp/messaging

79
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
mcp.tool_schema_changed-3

Findings (3)

mediumCapabilities are listable without authentication, including 6 whose names suggest state change (message_schedule_create_recurring, message_schedule_delete, message_schedule_update, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowInput schema changed without a name change: conversation_list
mcp.tool_schema_changed @ 1.0.0
infoCapability set changed: +3 / -0
mcp.capability_set_changed @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation1h ago0f4b590c89d74718…
http_response_observation1h ago91b964240590909d…
availability_observation1h ago48979fb234a4f6b2…
tls_certificate_observation1h ago9bb2df23e347f859…
oauth_metadata_observation1h agoe938372370977d1e…
mcp_protocol_observation1h ago7a86a44794993215…
mcp_capability_observation1h ago1ff9b9b0198c4cc9…
mcp_capability_drift1h ago718ad33a7789d81c…

Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.

Operate this service?

Prove control of mcp.eztexting.com/mcp/messaging to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →