atx/registry

api.dpf-it.com

https://api.dpf-it.com/mcp

79
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2h 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
mcp.tool_schema_changed-3

Findings (3)

mediumCapabilities are listable without authentication, including 6 whose names suggest state change (create_workspace, delete_data_spec, finish_data_spec_update, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowInput schema changed without a name change: manage_account, manage_trigger
mcp.tool_schema_changed @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation2h ago9f90c3d3784f0fc3…
http_response_observation2h agoc636beddb8fc6d06…
availability_observation2h ago4c38739c21339335…
tls_certificate_observation2h ago210c722d7bd8faf5…
oauth_metadata_observation2h ago62f4fb53b58b7b46…
mcp_protocol_observation2h agoe8cc4d7f806bd88d…
mcp_capability_observation2h agoccffeb0302966655…
mcp_capability_drift2h ago42d31ca4ed52a2d2…

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

Operate this service?

Prove control of api.dpf-it.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →