Model Context Protocol
Use domscout as agent tools
The @domscout/mcp package exposes this API as MCP tools, so an agent platform can read pages, capture images, extract structured data, and run bounded crawls without you writing an HTTP client. Every tool is the same route documented in the API guide, with the same plan gates, the same credit weights, and the same safety controls.
01 · Connect
Point a client at the server
Create a key in the dashboard, then add the server to your MCP client configuration. The package is run with npx, so there is nothing to install.
The default target is https://api.domscout.io.
02 · Tools
What the agent can call
Costs come back with the result
No request exceeds 10 credits, and every tool result carries what it cost and what remains, so an agent can budget without a second call.
Plan gates still apply
A tool is usable when its plan and the deployment state allow the underlying route. Trusted browser-side JavaScript has a separate account entitlement. domscout_check_credits reports which capabilities this key can actually use.
Web search is not among them. POST /search is withheld while no provider is configured, so no MCP tool wraps it.
03 · Resources
Documentation the agent can read directly
04 · Keys
Where the key lives
The server sends an x-api-key to the API host and reads the response. It holds no browser, database, or billing credential. Keep the key in your MCP client's environment block — never commit it, and never paste it into a prompt, because prompt text is frequently logged by the platform running the agent.