The MCP server lets you connect an AI agent to the Portal API without writing an HTTP client. The endpoint is https://api.portal.deepsee.io/mcp, and it authenticates with the same API key used for all other API requests. Every read endpoint in the API is exposed to the agent as a tool.

You can find your active API key, along with copy-ready configuration snippets, in the Portal API Settings section. The snippets display your key masked, but the copy buttons copy the full key.

Connecting a Client

Claude Code

claude mcp add --transport http deepsee https://api.portal.deepsee.io/mcp \
  --header "x-api-key: YOUR_API_KEY"

Cursor, Claude Desktop, VS Code, and Other Standard Clients

Clients that use the standard MCP configuration file take the following block:

{
  "mcpServers": {
    "deepsee": {
      "url": "https://api.portal.deepsee.io/mcp",
      "headers": { "x-api-key": "YOUR_API_KEY" }
    }
  }
}

Client Requirements

The server authenticates on a custom x-api-key request header, so your client must support custom headers.

ChatGPT connectors currently support OAuth or no-auth rather than static headers, and are therefore not compatible with the server at this time. OAuth support is on our roadmap.

Common Use Cases

Once connected, an agent can query the same fraud, brand safety, ad experience, content authenticity, and supply chain signals available through the portal and the API. Two patterns are typical:

• Analyst workflows. Checking a domain or a list of domains against DeepSee.io signals from within an existing AI tool, without building an integration first.
• Agentic buying and curation systems. Supplying observed inventory signals to automated systems that would otherwise operate on declared data such as ads.txt entries, sellers.json claims, and declared categories.

Note that the agent determines which tools to call and how to interpret the results. The underlying data is identical to what the API returns; the quality of the output depends on how the request is framed.

Credits and Billing

Tool calls are billed identically to standard API requests. An MCP tool call and a direct API call are the same request, so both consume credits at the same rate against your existing monthly allocation. No separate plan or add-on is required.

For details on credit allocations and Flexible Credit Usage, see API Access.

Further Documentation

The full list of available tools, along with endpoint reference material is on the API reference page.