atx/registry

markmesh.com/api/v1

https://markmesh.com/api/v1/mcp

67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago

Why this score

mcp_requires_authentication+10
tls_present_and_valid+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation1d agob84aa836eef9e7ea…
http_response_observation1d agob28bac15fc1c4b8c…
availability_observation1d agoc5181e1a277fce76…
hosting_provider_observation1d agoe7292135d1d3f6bd…
tls_certificate_observation1d agoa22bc61eccc77b31…
oauth_metadata_observation1d agob02b52f75b066bab…
mcp_protocol_observation1d ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →