web-data-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token for authentication | |
| WEB_DATA_MCP_HTTP_TOKEN | No | Optional token for HTTP transport authentication |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_urlA | Scrape a public web page into clean markdown in one call: runs a crawler, waits, scores the result (completeness, bot-wall detection), and automatically retries with stronger settings when quality is low. Costs Apify credits per run. For arbitrary actors or fire-and-forget runs use run_actor instead. |
| run_actorA | Start an allowlisted Apify actor with an explicit input object. Returns run_id and dataset_id handles for get_run_status / fetch_dataset_items / validate_dataset. Costs Apify credits. Prefer scrape_url for simple page scrapes. |
| get_run_statusA | Check whether an actor run has finished and where its dataset is. Free and safe to poll. |
| fetch_dataset_itemsA | Read items from an actor run dataset with pagination, field projection, and a hard token budget. Start with response_format "summary" to see the shape cheaply, then fetch "items" with a fields projection. Items arrive as JSON in the text content; structured content carries pagination metadata (total, next_offset, truncated). |
| validate_datasetA | Score a dataset before trusting it: schema pass rate (if a JSON Schema is given), field completeness, duplicate rate, and bot-wall detection. Use the score to decide between consuming the data and retry_low_quality_run. |
| retry_low_quality_runA | Re-run an actor with progressively stronger anti-blocking settings (residential proxies, then a browser crawler) until the dataset quality score reaches the threshold or attempts are exhausted. Each attempt costs Apify credits. |
| dataset_to_rag_documentsA | Turn scraped items into embedding-ready documents: token-bounded chunks with overlap, source attribution, stable content-hash ids for idempotent vector upserts, and selected metadata. Paginate with offset/limit for large datasets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/fctpe/web-data-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server