ENDPOINT 1
https://scraper.geonode.io/mcp
MCP server metadata
- Name
- Scraper API
- Version
- 0.1.0
Without an API key only the `extract` tool is listed. Without an API key, extraction is synchronous only, without JavaScript rendering or request headers other than Accept-Language, and limited to a small per-client rate and daily volume. An API key, sent as the X-Api-Key header, lifts these restrictions; the plan's own limits apply instead. With a key, all tools are listed.
Known tools 1
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.scraper-api]
url = "https://scraper.geonode.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"scraper-api": {
"type": "http",
"url": "https://scraper.geonode.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: scraper-api
Remote MCP URL: https://scraper.geonode.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"scraper-api": {
"url": "https://scraper.geonode.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"scraper-api": {
"type": "http",
"url": "https://scraper.geonode.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "scraper-api",
"transport": "streamable-http",
"url": "https://scraper.geonode.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.