Working with it

MCP server

Point an agent at it with a URL and a key.

Every tool is also an MCP server. Any client that speaks the Model Context Protocol — Claude Code, Cursor, VS Code, Windsurf and the rest — can call them directly, with no glue code and no SDK.

Connecting

One URL and your key. Most clients take this as JSON:

{  "mcpServers": {    "snoopscan": {      "url": "https://api.snoopscan.com/mcp",      "headers": { "Authorization": "Bearer sk_YOUR_KEY" }    }  }}

Integrations has the exact steps for each client, including the ones that want a command rather than a URL.

Available tools

The same tools as the API, named the same way, with the same arguments. An agent that can call scrape can also crawl, map, search and extract — so "read this documentation site and answer from it" is one instruction rather than a script.

Billing

Calls made through MCP are ordinary API calls: same rate card, same activity log, same key. An agent left running is spending real credits, so give it its own key and you can watch what it costs and revoke it on its own.

Give an agent its own key. Not because it will misbehave, but because when you want to see what it spent — or stop it — you want one line in the log and one key to revoke.

Credits