atx/registry

in-context.me

https://in-context.me/mcp

49
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d 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 (2)

mediumCapabilities are listable without authentication, including 1 whose name suggests state change (booking_create) — 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_observation1d ago2c18d943d5bd98e4…
http_response_observation1d ago955e2eca48429ce9…
availability_observation1d ago6702b3aed76dfb59…
hosting_provider_observation1d agoe7292135d1d3f6bd…
tls_certificate_observation1d ago2cbb03760941587b…
oauth_metadata_observation1d ago8116a9782e7358cd…
mcp_protocol_observation1d agoa97fb045d8a68a42…
mcp_capability_observation1d agobd1993adc3e74f96…

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

Operate this service?

Prove control of in-context.me to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →