Data Collection

dpf-it.com

An MCP server for managing workspaces, data parsing and mapping specs, and their processing jobs, including status checks and deletion.

1 endpoint18 known toolsFirst detected July 6, 2026Last detected October 10, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name: dpf-mcp-remote
Version: 1.0.0

Capabilities

tools.listChangedresources.listChanged

Known tools 18

list_my_workspaces

List every workspace the authenticated user has access to, including their permission on each.

Inferred read-only

create_workspace

Create a new workspace, owned by the authenticated user.

Potential side effects

list_data

List either the data specs (parsing + mapping rule sets, resource: "specs") or the data processing jobs (executions of a spec, resource: "jobs") defined in a workspace.

Inferred read-only

get_status

Poll the status of either a data spec's own process (schema inference + code generation, run by start-analysis — pass specId, reaches "ready" or "failed") or a data-load job (pass jobId, reaches "complete" or "failed").

Inferred read-only

delete_data_spec

Permanently delete a data spec and its associated configuration.

Potential side effects

submit_query

Run a SQL query against the Iceberg tables loaded into a workspace.

Inferred read-only

manage_connection

Create, list, test, or delete a workspace connection to an external data source.

Potential side effects

manage_trigger

Create, list, update, delete, or fire a workspace job trigger.

Potential side effects

onboard_data_source

First step of setting up a new data integration: creates a data spec.

Inferred read-only

finish_data_source_onboarding

Call after uploading the file(s) returned by onboard_data_source — kicks off AI analysis and waits until the spec reaches "ready" or "failed".

Inferred read-only

update_data_spec

Change an existing data spec's configuration.

Inferred read-only

finish_data_spec_update

Call after uploading the file(s) returned by update_data_spec — kicks off AI analysis and waits until the spec reaches "ready" or "failed".

Inferred read-only

run_data_job

First step of processing new data files through an already-configured data spec: creates a job and returns presigned upload URL(s) for each file.

Potential side effects

finish_data_job

Call after uploading the file(s) returned by run_data_job — starts processing and waits until the job completes or fails.

Inferred read-only

setup_scheduled_pull

End-to-end workflow for "pull files from this SFTP server / S3 bucket on a schedule" requests: reuses a matching connection if one already exists in the workspace (same hostname/username for sftp, same roleArn for aws_s3), otherwise creates one; tests it; then creates a trigger that feeds an already-analyzed data spec (see onboard_data_source) on the given frequency.

Inferred read-only

call_dpf_api

Escape hatch for DPF capabilities that don't have a dedicated tool yet.

Inferred read-only

manage_account

Returns instructions for creating a DPF account, verifying its email, resending the verification code, or resetting a forgotten password — it never performs these itself and never asks for a password.

Potential side effects

contact

Send a message to the DPF team — request a demo, ask about licensing, report an issue, or request a feature.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.dpf-mcp-remote]
url = "https://api.dpf-it.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "dpf-mcp-remote": {
      "type": "http",
      "url": "https://api.dpf-it.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dpf-mcp-remote
Remote MCP URL: https://api.dpf-it.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "dpf-mcp-remote": {
      "url": "https://api.dpf-it.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dpf-mcp-remote": {
      "type": "http",
      "url": "https://api.dpf-it.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dpf-mcp-remote",
  "transport": "streamable-http",
  "url": "https://api.dpf-it.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.