atx/registry

gateway.pipeworx.io/data-edmonton

https://gateway.pipeworx.io/data-edmonton/mcp

63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 6h 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 (4)

mediumCapabilities are listable without authentication, including 1 whose name suggests state change (subscribe) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0
infoCapability set changed: +2 / -0
mcp.capability_set_changed @ 1.0.0

Evidence (9)

TypeObservedSHA-256
dns_resolution_observation6h ago51db5f25b7f57f91…
http_response_observation6h agode96907d16c3a6ac…
availability_observation6h agod618d12f5fe0ddba…
hosting_provider_observation6h agoe7292135d1d3f6bd…
tls_certificate_observation6h ago46d35f1181aa7f8e…
oauth_metadata_observation6h agoda0dc9ab20d4ccf1…
mcp_protocol_observation6h agof9794d4e58633dfa…
mcp_capability_observation6h agoefcca97a830293e3…
mcp_capability_drift6h agoc721211cd0d7074b…

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

Operate this service?

Prove control of gateway.pipeworx.io/data-edmonton to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →