atx/registry

gateway.pipeworx.io/tle

https://gateway.pipeworx.io/tle/mcp

63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d 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 (3)

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

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation2d agod4cb78f27868af7b…
http_response_observation2d ago8d71a36ac8bb2dad…
availability_observation2d agoae6a4c2cec91e031…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d agoce1eb48bbb441381…
oauth_metadata_observation2d agoda0dc9ab20d4ccf1…
mcp_protocol_observation2d ago7ac6df0b135b22cf…
mcp_capability_observation2d ago0f8ce519ac424221…

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

Operate this service?

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

Claim this profile →