Datpaq APIs, ready for your agent.
A hosted Model Context Protocol server that puts the full Datpaq API surface inside Codex, Claude Desktop, Cursor, Cline, and any other MCP-aware agent. Paste one URL and your Datpaq API key, ship.
Your Datpaq API key on every request, streamable HTTP, every active Datpaq endpoint included.
URL: https://mcp.datpaq.com/
Transport: streamable HTTP
Auth: Authorization: Bearer YOUR_DATPAQ_API_KEY
Tools: 34 hosted tools across 13 active APIsThe agent loop
Connect. Authenticate. Call.
Three steps from a fresh agent install to calling Datpaq endpoints. No SDK, no glue code, no wrapper service to maintain.
Connect
Paste the Datpaq MCP block into your agent's config. Streamable HTTP, no binary to install, works behind corporate proxies.
Authenticate
Drop your own Datpaq API key into the Authorization header. Calls bill against your plan; no shared quota or anonymous tier.
Call
Your agent discovers 34 tools across 13 active interfaces and calls them directly. No client code, no boilerplate, no wrappers.
How agents reach datpaq
Cited and called
Answer engines reach Datpaq two ways at once: they cite the content they crawl, and they invoke the API directly — over the MCP server you just connected. The same answer can do both.
What you get
Designed for agents, audited for safety
The hosted surface is curated: only API call tools, no local-state passthroughs, no shell-out, no inactive interfaces. The 34 tools you see are the 34 tools agents can call.
Hosted, not installed
Paste a URL into your agent's config and you're connected. No npm package, no Docker image, no version-pinning to track.
Your API key, every call
Your Datpaq key authenticates every call. Bills against your existing plan with the same rate limits and audit trail as the API.
Same API surface
Every active Datpaq interface — whois, IP intelligence, EV charger, image processing, currency, more — is exposed as MCP tools.
Streamable HTTP
Modern MCP transport with session resumption, no SSE quirks, and clean failure modes when the network blips.
Works everywhere
Compatible with Codex, Claude Desktop, Cursor, Cline, Continue, and any other MCP client supporting remote streamable HTTP.
Curated for safety
Local-state and shell-out tools from the CLI are stripped from the hosted surface. Agents see only the API call tools.
Fresh every call
Per-request client construction, response cache disabled. DELETE-then-GET sequences never return stale snapshots.
Open source
Generated from the same OpenAPI spec as the CLI and dashboard. Audit the tool definitions, run your own copy, fork freely.
What an agent does with it
Talk to the API in plain English
Once the server is connected, your agent picks the right tool and parameters automatically. These are prompts a teammate could type today.
Connect from any MCP client
Add the hosted Datpaq MCP endpoint to your client's config. Some tools use JSON, Codex uses TOML, and UI-based clients ask for the same URL plus Authorization header.
Your key, your bill
Every call travels with your Datpaq API key in the Authorization header. The hosted server never stores it; the same key works in the CLI, dashboard, and direct API.
Want it local instead?
The Datpaq CLI ships a stdio MCP server that runs on your machine and reads from your local config. Useful for offline development, private data, or when you'd rather not depend on a hosted endpoint.
Connect Datpaq to your agent
One URL, one API key, every active Datpaq endpoint — inside Codex, Claude Desktop, Cursor, Cline, or whatever MCP-aware tool you ship in.