atx/registry

emailoctopus.usefulapi.io

https://emailoctopus.usefulapi.io/mcp

63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago

Why this score

oauth_metadata_present+14
mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
headers.missing_hsts-3
reachable+2

Findings (2)

mediumCapabilities are listable without authentication, including 5 whose names suggest state change (emailoctopus_create_contact, emailoctopus_create_list, emailoctopus_delete_contact, …) — 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 (8)

TypeObservedSHA-256
dns_resolution_observation2d ago29913366e4be4c7d…
http_response_observation2d agoa2c42f2732507cd0…
availability_observation2d agoa7affa86039dcbce…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago241c00c57b74836a…
oauth_metadata_observation2d ago0e21533531dab7cd…
mcp_protocol_observation2d ago2fa554a8b7557712…
mcp_capability_observation2d agoee9f01cab99bbed7…

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

Operate this service?

Prove control of emailoctopus.usefulapi.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →