atx/registry

api.temp.md

https://api.temp.md/mcp

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

Why this score

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

Findings (3)

mediumCapabilities are listable without authentication, including 4 whose names suggest state change (publish_temp, recover_update_token, set_comments, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation2d ago253c8aa8c0fd2fac…
http_response_observation2d ago31e4ad875f924866…
availability_observation2d ago6524f6f363076bf2…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d agoa0a47301ce7c4e46…
oauth_metadata_observation2d agodbe00529045d7478…
mcp_protocol_observation2d agodc8018adfb72ba7c…
mcp_capability_observation2d ago972286fb4bf8c290…

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

Operate this service?

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

Claim this profile →