atx/registry

api.bowmark.ai/mcp/registry

https://api.bowmark.ai/mcp/registry

38
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 3h ago

Why this score

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

Findings (4)

mediumCapabilities are listable without authentication, including 3 whose names suggest state change (delete_connection, run, run_view) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
mediumNew state-changing capability exposed: run_view
mcp.consequential_capability_added @ 1.0.0
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
lowInput schema changed without a name change: get_library, run
mcp.tool_schema_changed @ 1.0.0

Evidence (9)

TypeObservedSHA-256
dns_resolution_observation3h ago31e591c47109a385…
http_response_observation3h ago8645dd820db42784…
availability_observation3h ago66e61d91da19ed53…
hosting_provider_observation3h agoe7292135d1d3f6bd…
tls_certificate_observation3h ago8bbd06bdf4d4dc38…
oauth_metadata_observation3h agoecb6ae73b757d6a6…
mcp_protocol_observation3h agoe41f9c4cb9bcdb21…
mcp_capability_observation3h agoa477b2a840c583a3…
mcp_capability_drift3h agocb4daf6cd472dfcf…

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

Operate this service?

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

Claim this profile →