atx/registry

api.delx.ai/v1/mcp/protocol

https://api.delx.ai/v1/mcp/protocol?src=registry

82
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 51m ago

Why this score

oauth_metadata_present+14
tls_present_and_valid+12
mcp.unauthenticated_consequential_tools-8
reachable+6
hsts_enabled+4
mcp_capabilities_discoverable+4

Findings (2)

mediumCapabilities are listable without authentication, including 2 whose names suggest state change (add_context_memory, close_session) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation51m ago84cc83b1fd42ded7…
http_response_observation51m agod08f95aa9a2e81df…
availability_observation51m ago2562de1ef129bcde…
tls_certificate_observation51m agoefdb5a8cd0d61606…
oauth_metadata_observation51m agodb6ffa9d664c2d66…
mcp_protocol_observation51m agofbbf0e506d9746cc…
mcp_capability_observation51m agodb6d93137d9eb926…

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

Operate this service?

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

Claim this profile →