atx/registry

emc2ai.io/api

https://emc2ai.io/api/mcp

67
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
reachable+2
hsts_enabled+1

Findings (2)

mediumCapabilities are listable without authentication, including 2 whose names suggest state change (get_trade_signals, run_backtest) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation2d ago03a0efad2c33aa36…
http_response_observation2d ago71c3d63272282445…
availability_observation2d agof36c9fb6ff1637f4…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago854af79558e3965d…
oauth_metadata_observation2d agoe2f0dc736e40584d…
mcp_protocol_observation2d ago40e09b69d60ea4e3…
mcp_capability_observation2d ago8e85ca9b0648c815…

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

Operate this service?

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

Claim this profile →