One hosted endpoint for every AI app that speaks MCP. Sign in with your account or send your key; your AI gets tools for reading the live web and for building apps on it. Prefer to run it yourself? It's open source.
Server URL
https://mcp.unblockingapi.com/mcpThe app never sees your API key. Disconnect it any time under Connected apps.
https://mcp.unblockingapi.com/mcp/.well-known/oauth-protected-resource and register themselves; the authorization server is app.unblockingapi.com and the scope is mcp.Authorization: Bearer <key> or X-Api-Key: <key>.unblock_fetch and find_templates for reading pages, get_build_guide for building apps on the API. All read-only.io.github.unblockingapi/mcp), npm, GitHub (MIT).Your AI picks them by itself. Leave render unset: the API fetches plainly first and uses a real browser when a site needs one.
unblock_fetchFetch a URL through UnblockingAPI
Reads any page through rotating residential proxies and a real browser. Picks a plain fetch or a browser per site by itself. Returns the page as Markdown, or HTML on request; pass a template to get JSON instead.
1 credit per successful fetch; failures are free
find_templatesFind a structured-data template
Checks whether a published template parses a site into JSON — by the URL you're about to fetch, a keyword or a category.
Free
get_build_guideHow to build an app on UnblockingAPI
For writing code on the API: the REST reference, keeping the key server-side, templates, and complete recipes (rank tracker, listings aggregator, price monitor).
Free
For an app without a guide here: most take a URL and headers in this shape (some call the URL key serverUrl or httpUrl). Leave the headers out if the app supports MCP sign-in.
{
"mcpServers": {
"unblockingapi": {
"url": "https://mcp.unblockingapi.com/mcp",
"headers": { "Authorization": "Bearer your_api_key_here" }
}
}
}The same server over stdio, for apps that launch local MCP servers. Needs Node.js 18+.
{
"mcpServers": {
"unblockingapi": {
"command": "npx",
"args": ["-y", "@unblockingapi/mcp"],
"env": { "UNBLOCKINGAPI_KEY": "your_api_key_here" }
}
}
}The app's name as it registered itself, the UnblockingAPI account you're signed in as, and the address you'll be sent back to. The app can fetch pages and look up templates on your account - nothing else: no key, password or billing access.
Under Settings → Connected apps on app.unblockingapi.com. It is signed out at once.
That is the server's answer to a request without credentials: a 401 pointing at its sign-in metadata. Apps that support MCP sign-in follow it automatically; for others, add the key header.
Same tools and costs. Hosted needs nothing installed and most apps sign in without a key. Local runs npx -y @unblockingapi/mcp on your machine with UNBLOCKINGAPI_KEY set, which some people prefer for control or offline config management.