@unblockingapi/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNBLOCKINGAPI_KEY | Yes | Your API key. | |
| UNBLOCKINGAPI_BASE_URL | No | Override the API base URL. | https://api.unblockingapi.com |
| UNBLOCKINGAPI_TIMEOUT_MS | No | Per-request timeout. Rendered fetches can take ~35s. | 45000 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| unblock_fetchA | Fetch a URL through UnblockingAPI, bypassing bot detection, CAPTCHAs, and geo-blocks with rotating residential proxies. Returns the page HTML. Set render=true for JavaScript-heavy sites (SPAs, dynamic content) to get the fully rendered DOM. |
| google_searchA | Run a Google search through UnblockingAPI and get structured organic results as JSON. Useful for SERP data, research, and competitive analysis without getting blocked. |
| idealista_propertyA | Extract structured data from an idealista.com property listing (Spain's largest real-estate portal) — price, size, rooms, bathrooms, floor, energy rating, features, photos, advertiser, and more, as JSON. Pass the full listing URL. |
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 purpose: unblock_fetch fetches raw HTML, google_search returns structured search results, and idealista_property extracts specific real-estate listing data. There is no overlap or ambiguity between them.
All tool names follow a consistent snake_case pattern and are descriptive, but the pattern isn't strictly verb_noun: unblock_fetch is verb_verb, google_search is noun_verb, and idealista_property is noun_noun. Minor deviation from a uniform convention.
With 3 tools, the set is small but well-scoped for the server's purpose of unblocking web data access. Each tool earns its place, though the count feels slightly thin for broader scraping scenarios.
Generic fetch covers arbitrary URLs, structured search covers SERP data, and a specialized extractor covers a major site. Missing features like custom structured extraction from other sites are workarounds via unblock_fetch, so the surface is reasonably complete for its niche.