atx/registry

api.mcpanalytics.ai/mcp/api-key

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

60
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 51m 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
mcp.tool_schema_changed-3
reachable+2

Findings (3)

mediumCapabilities are listable without authentication, including 5 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
lowInput schema changed without a name change: build_status, report_cards, reports_view
mcp.tool_schema_changed @ 1.0.0

Evidence (9)

TypeObservedSHA-256
dns_resolution_observation50m ago5ddb093ab56e5a77…
http_response_observation50m ago74f9d91ab57c0757…
availability_observation50m agoddcb016076c2eeb0…
hosting_provider_observation50m agoe7292135d1d3f6bd…
tls_certificate_observation50m ago11c37473896f765b…
oauth_metadata_observation50m ago404c473b9fb07447…
mcp_protocol_observation50m ago6414047cf6693487…
mcp_capability_observation50m agoff61cd22c76777dc…
mcp_capability_drift50m ago65c7ff3660fb848f…

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 →