atx/registry

mcp.usemycontext.ai

https://mcp.usemycontext.ai/mcp

63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d 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
reachable+2

Findings (2)

mediumCapabilities are listable without authentication, including 1 whose name suggests state change (suggest_update) — 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 ago71957f5c6fbbcc0d…
http_response_observation1d ago40faa5e2cb888fe0…
availability_observation1d ago919a4384d30a098b…
hosting_provider_observation1d agoe7292135d1d3f6bd…
tls_certificate_observation1d agofa1be6877a8880a8…
oauth_metadata_observation1d ago0c078d66131a3714…
mcp_protocol_observation1d ago0fd4952be977530c…
mcp_capability_observation1d ago5e5cb06928123615…

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

Operate this service?

Prove control of mcp.usemycontext.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →