atx/registry

api.mcpanalytics.ai/mcp/api-key

https://api.mcpanalytics.ai/mcp/api-key

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 4 whose names suggest state change (create_analysis, datasets_upload, modify_analysis, …) — 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 ago5ddb093ab56e5a77…
http_response_observation2d ago74f9d91ab57c0757…
availability_observation2d ago62155631d86da10a…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago502c394e94983da8…
oauth_metadata_observation2d ago404c473b9fb07447…
mcp_protocol_observation2d agoba9d2d671a88e39a…
mcp_capability_observation2d ago27697890c06a8fc0…

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

Operate this service?

Prove control of api.mcpanalytics.ai/mcp/api-key to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →