WebIntel-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEMO_MODE | No | When true, the host of every request is rewritten to the in-network mock host mock-web for offline demos. | false |
| WEBINTEL_MAX_CHARS | No | Character budget for mcp_browser_navigate Markdown. Truncation retreats to a paragraph boundary and sets truncated. | 30000 |
| CRAWL_ALLOW_DOMAINS | No | Comma-separated allowlist, exact host match — *.github.com is not supported. Empty string disables the allowlist (local debugging only; the private-IP block still applies). | github.com,news.ycombinator.com,arxiv.org |
| WEBINTEL_RATE_PER_SEC | No | Per-host token-bucket refill rate (burst = capacity). Over-limit calls raise immediately; they do not queue. | 1 |
| WEBINTEL_ARTIFACTS_DIR | No | Directory for screenshots and raw HTML. | /artifacts |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_browser_navigateA | Navigate to a URL and return the purified page body as Markdown. Runs the full security pipeline first (scheme / DNS / private-IP block / domain allowlist / rate limit); navigation never starts on a refused URL. The final (post-redirect) URL is re-checked against the same verdicts. Use wait_until="domcontentloaded" when the page holds long-poll connections that prevent networkidle from ever firing. |
| mcp_extract_tableA | Extract all tables from a URL as structured JSON rows. Tables must go through this tool, not mcp_browser_navigate: Readability routinely drops or mangles interleaved / markup (GitHub Releases pages), so narrative text and tabular data are separated by design. |
| mcp_take_screenshotB | Screenshot a URL (optionally element-scoped or full-page) into the shared artifacts volume. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct output mode: purified Markdown body (navigate), structured JSON rows (extract_table), and a rendered image (screenshot). Descriptions explicitly delineate boundaries, e.g. telling the agent that tables must go through extract_table rather than navigate, removing any misselection risk.
All tools share the mcp_ prefix, but the verb patterns are slightly mixed: 'browser_navigate' (noun_verb) versus 'extract_table' and 'take_screenshot' (verb_noun). Still readable and predictable enough to infer purpose at a glance.
Three tools is lean but each earns its place by covering a distinct retrieval modality (text, tabular, visual). It is on the thin side for a server branded 'WebIntel', but not problematic.
Fetching, table extraction, and screenshots are covered, but the surface lacks discovery/search operations and link or metadata extraction that a web-intelligence server would typically expose. Agents can work around this by navigating to known URLs, but it is a notable gap.