@domscout/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOMSCOUT_API_KEY | Yes | Your API key for domscout. | |
| DOMSCOUT_BASE_URL | No | Overrides the current production gateway for an intentionally separate deployment. Defaults to https://api.domscout.io. | https://api.domscout.io |
| DOMSCOUT_DOCS_BASE_URL | No | Where the contract resources are fetched from. Defaults to https://www.domscout.io. | https://www.domscout.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| domscout_check_creditsA | Free — this call never consumes credits or quota. Returns the credit balance, this month's quota usage, the per-second rate limit, and the full price list for every capture option. Call this before a large run to budget it, and after a 429 to find out whether you were rate limited (retry in a second) or are out of credits (do not retry). |
| domscout_extract_markdownA | Costs 1 credit. Loads a page and returns its main content as clean Markdown, with the title, description, Open Graph fields, word count, an estimated token count, and a content-quality flag. This is the right tool for reading a page — it is the cheapest option and returns text rather than an image. Use domscout_capture_screenshot only when you actually need to SEE the page. Set fast:true for static pages (documentation, blogs, news, changelogs): same price, same result shape, roughly an order of magnitude faster, but it does not run JavaScript. Check meta.renderJs and meta.contentQuality in the result and retry without fast:true if the page came back thin. |
| domscout_capture_screenshotA | Costs 1 credit for a viewport PNG/JPEG/WebP; +1 for fullPage, +1 for PDF. Returns the image itself. Use this when you need to see layout, styling, or a visual state — for reading text, domscout_extract_markdown is cheaper and more useful. |
| domscout_extract_dataA | Costs 2 credits. Pulls named fields off a page using CSS selectors and returns typed JSON. Each field reports found/missing/invalid_selector separately, so a partial result tells you which selector was wrong rather than failing the whole call. Requires Pro or above. |
| domscout_inspect_pageA | Costs 2 credits. Returns a semantic snapshot: the accessibility tree, the interactive elements, and a selector for each. Use this before domscout_automate_page to find out what is on the page and what to target. Requires Pro or above. |
| domscout_automate_pageA | Costs 1 credit, +1 if more than 10 steps. Runs a sequence of actions — click, type, select, scroll, wait, navigate, pressKey, assert — and returns the final page plus a per-step pass/fail report. Call domscout_inspect_page first to find selectors. Requires Pro or above. The whole sequence shares a 24-second budget. |
| domscout_crawl_siteA | Costs 1 credit per page crawled — submitting the crawl itself is free. Returns a job ID immediately — poll it with domscout_get_job. Always respects robots.txt (this cannot be disabled), caps at 500 pages and depth 5, and requires an explicit HTTPS allowedOrigins list. Requires a Business plan or above. |
| domscout_get_jobA | Free — this call never consumes credits or quota. Poll a job ID returned by a crawl, a batch, or an auto-promoted capture. Status is one of pending, processing, retrying, done, error, cancel_requested, cancelled. Polling is free, so poll as often as you like — but the per-second rate limit still applies. |
| domscout_cancel_jobB | Free — this call never consumes credits or quota. Cooperatively cancels a durable job, batch, or crawl. Work already in flight may still complete. |
| domscout_send_feedbackA | Free — this call never consumes credits or quota. — and it will never be charged, by design. Use this whenever something about this API got in your way: an error you could not act on, a parameter that did not behave as documented, a capability you needed and could not find, or a result that was wrong. Include the requestId from a failed call and the team sees exactly what happened on their side. A human reads these. Do not include API keys or other secrets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| domscout API reference | Every endpoint and parameter in one file, including the credit price list and the stable error codes. Read this when a tool is not enough and you need the raw HTTP contract. |
| domscout OpenAPI 3.1 specification | The canonical machine-readable wire contract. |
TDQS
Scored across 10 tools
Each tool targets a distinct purpose: billing, reading, visual capture, structured extraction, page inspection, automation, crawling, job management, and feedback. Even similarly named extraction tools (extract_markdown, extract_data, capture_screenshot) are clearly separated by their descriptions, eliminating ambiguity.
All tool names follow the same pattern: a common 'domscout_' prefix followed by a snake_case verb_noun structure. Verbs are distinct and descriptive (check, automate, extract, capture, inspect, crawl, get, cancel, send), making the set feel uniform and predictable.
Ten tools is a well-scoped set for a webpage capture and automation service. Each tool covers a distinct capability area without redundancy, and there are enough tools to handle both simple and complex workflows without overwhelming an agent.
The tool surface covers the full lifecycle of working with web pages: inspection, reading, structured extraction, visual capture, automation, site-wide crawling, job status polling, cancellation, and billing oversight. No obvious dead ends exist—even job management and feedback channels are included.