atx/registry

gnosem.dev

https://gnosem.dev/mcp

67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 3h 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 (memory_write, memory_write_bulk) — 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_observation3h ago796f704341bf2b1b…
http_response_observation3h agoc6e0e133e1a2520f…
availability_observation3h agof9482c8cdfaded68…
hosting_provider_observation3h agoe7292135d1d3f6bd…
tls_certificate_observation3h agob34b5c36c4c406e7…
oauth_metadata_observation3h agoce8f1aa60b25d52d…
mcp_protocol_observation3h ago906efa8b568b92d1…
mcp_capability_observation3h agof4c229c190e59871…

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

Operate this service?

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

Claim this profile →