ContextFetch
Überblick
Beschreibung vom Entwickler (englisches Original)
Web search and any page as LLM-ready Markdown for AI agents. Free keyless tier, no signup.
Die drei Säulen von PopNx MCP
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
- Stimmen der NutzeriNoch keine BewertungenBewertungen starten in einem späteren Schritt zusammen mit Benutzerkonten
- Unsere Basischecksi3 von 3 bestandenAnhand öffentlicher Informationen geprüft; Code noch nicht gescannt
- NutzungiGanz neu↓ 152/Wo. · ★ –
Was du damit machen kannst
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
- Verbindung: Computer oder Cloud
- Transport: stdio, Streamable HTTP
- Kategorie: Suche & KI-Gedächtnis
- Das musst du eintragen: CONTEXTFETCH_API_KEY, x-api-key
Installation
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Bevor du installierst
- Basischecks: 3 von 3 bestanden
- Läuft auf dem Server des Entwicklers: Was du fragst, läuft über dessen Server.
- Kann 14 Dinge (Tools) contextfetch_search, contextfetch_extract_url, contextfetch_find_similar, contextfetch_research …
- Das trägst du selbst ein:
CONTEXTFETCH_API_KEY,CONTEXTFETCH_API_BASE,x-api-key
Als geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
- Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet
- npmNode.js installiert (für den Befehl npx)
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.
Oder führ ihn auf deinem Computer aus
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"contextfetch": {
"command": "npx",
"args": [
"-y",
"@contextfetch/mcp"
],
"env": {
"CONTEXTFETCH_API_KEY": "your-value",
"CONTEXTFETCH_API_BASE": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add --transport http contextfetch https://api.contextfetch.dev/mcp --header 'x-api-key: your-value'Oder führ ihn auf deinem Computer aus
claude mcp add contextfetch --env CONTEXTFETCH_API_KEY=your-value --env CONTEXTFETCH_API_BASE=your-value -- npx -y @contextfetch/mcpTrag die leeren Werte ein, bevor du ihn startest.
Oder kopier die Einstellungen selbst
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"contextfetch": {
"url": "https://api.contextfetch.dev/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}Oder führ ihn auf deinem Computer aus
Oder kopier die Einstellungen selbst
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"contextfetch": {
"command": "npx",
"args": [
"-y",
"@contextfetch/mcp"
],
"env": {
"CONTEXTFETCH_API_KEY": "your-value",
"CONTEXTFETCH_API_BASE": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Oder kopier die Einstellungen selbst
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"contextfetch": {
"type": "http",
"url": "https://api.contextfetch.dev/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}Oder führ ihn auf deinem Computer aus
Oder kopier die Einstellungen selbst
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"contextfetch": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@contextfetch/mcp"
],
"env": {
"CONTEXTFETCH_API_KEY": "your-value",
"CONTEXTFETCH_API_BASE": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Werte, die du selbst einträgst
- ContextFetch API key. Leave unset for the free keyless tier (25 requests per day per IP).
CONTEXTFETCH_API_BASEenvAPI base URL, only for a self-hosted engine.x-api-keygeheim HTTP headerContextFetch API key. Leave unset for the free keyless tier (25 requests per day per IP).
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Was er kann
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 7. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
contextfetch_searchSearch the web and get LLM-ready Markdown. Each result has its title, URL and only the passages relevant to the query (cross-encoder pruned context), so it costs far fewer tokens than raw pages. Use for current events, documentation, APIs, research and fact checking.
contextfetch_extract_urlFetch a public web page (docs, articles, GitHub files, arXiv papers) as clean Markdown with tables preserved. Pass `query` to get only the passages relevant to it instead of the whole page.
contextfetch_find_similarFind pages similar to a given URL (alternatives, related docs, competing libraries), excluding the source domain. Returns titles, URLs and the most relevant passages as Markdown.
contextfetch_researchResearch a question in one call, server-side: runs up to 5 web searches (sub-queries) concurrently, dedupes the pages by URL, ranks them all against the question with a cross-encoder and returns one Markdown evidence pack with numbered [n] sources and their query-pruned passages,
contextfetch_deep_researchDeep research in one call, no LLM: a deep search of the question, its sub-topics (or your sub_queries) as searches of their own, and the pages its list and index results link to, returned as one cited report: summary, key facts, a section per sub-topic and the sources, every pass
contextfetch_answerAnswer a question with passages quoted verbatim from the web, never generated: searches, scores every passage of the top pages with a cross-encoder and returns the best ones with [n] citations to their sources. Use it for quick factual lookups; the quotes may not fully answer an
contextfetch_agentA finished answer to a question, written with [n] citations to live web sources: one deep search reads the top pages and an LLM (gpt-oss-120b) writes the answer from them only, saying what is missing rather than guessing; when the pages lack the answer it searches again with new
contextfetch_crawlCrawl one website from a start URL and get its pages as Markdown: same-site links only, up to `max_depth` hops (<= 3) and `limit` pages (<= 50). Pass `query` to rank the pages by relevance and return only their relevant passages. Costs $0.001 per page returned ($1 per 1,000).
contextfetch_mapList a website's URLs without fetching its pages: its sitemaps (from robots.txt, else /sitemap.xml) plus the start page's links, same site only, up to `limit` (<= 5,000). Use it to find the right pages before contextfetch_extract_url or contextfetch_crawl. Costs $0.001 ($1 per 1,
contextfetch_balanceShow the API key's balance in dollars, daily burn rate (7-day average) and auto top-up settings, including the last auto-reload error if a payment failed. Needs an API key (Authorization: Bearer); free.
contextfetch_auto_reloadTurn auto top-up on or off, or change it: when the balance drops below `threshold_usd`, the saved card adds `amount_usd`, up to `monthly_max_usd` per month. Needs an API key and a card saved at checkout. The monthly cap cannot be raised above $500 here.
contextfetch_get_free_keyGet a free ContextFetch API key (no signup, no payment) with a $2.50 starter balance, for when the keyless daily limit runs out. One key per network, ever: keep the key it returns and use it as `Authorization: Bearer `.
searchSearch the web. Returns {results: [{id, title, url}]} as JSON; pass an id to `fetch` for the page text.
fetchFetch the full text of a search result by its id (a URL). Returns {id, title, text, url, metadata} as JSON.
Basischecksi
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026
- ✓ Bestanden
Entwickler passt zum Repo
Der Registry-Name wurde über die Domain contextfetch.dev bestätigt (die Registry prüft, wem die Domain gehört)
- … Noch nicht geprüft
Wird noch gepflegt
Dieses Repo haben wir noch nicht von GitHub gelesen
- … Noch nicht geprüft
Hat eine Lizenz
Dieses Repo haben wir noch nicht von GitHub gelesen
- ✓ Bestanden
Endpunkt antwortet
Antwort in 201 ms (HTTP 200)
- – Nicht zutreffend
Anmeldung mit OAuth
Keine Anmeldung nötig
- ✓ Bestanden
Keine versteckten Anweisungen in Tool-Beschreibungen
Wir haben 14 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Im Vergleich mit anderen in Suche & KI-Gedächtnisi
- Mehr Sterne als 0 % der anderen 5686 Server in dieser Kategorie
- Neuer in der Registry veröffentlicht als 71 % der anderen 5686 Server in dieser Kategorie
- Basischecks gleich gut wie oder besser als bei 100 % der anderen 5686 Server in dieser Kategorie
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Häufige Fragen
Ist ContextFetch sicher?
Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Welche Schlüssel oder Codes braucht er?
Das musst du eintragen: CONTEXTFETCH_API_KEY, x-api-key
Läuft er auf meinem Computer oder in der Cloud?
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Wird er noch gepflegt?
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.1.0) kam vor 16 Tagen in die Registry.
Welche Apps können ihn nutzen?
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
Was kann ich stattdessen nutzen?
In derselben Kategorie: Context7, Codebase Memory, Exa
Alternativen
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
README vom Entwickler
README öffnen
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
ContextFetch MCP server
Web search and clean, LLM-ready Markdown for AI agents: $1 per 1,000 searches, and 25 a day free with no key and no signup.
claude mcp add contextfetch -- npx -y @contextfetch/mcp
That is the whole setup for Claude Code. Then ask your agent something that needs the web:
Search for how Postgres SKIP LOCKED works for job queues
contextfetch_search returns each page as Markdown, cut down to the passages that answer the query:
## 1. PostgreSQL Job Queues with SKIP LOCKED | CodeNotes
https://codenotes.tech/blog/postgresql-job-queues-with-skip-locked · score 1.000
FOR UPDATE SKIP LOCKED is useful because it lets many workers claim different rows without blocking on rows another worker has already locked. But it is only the claiming primitive. A production queue also needs the right schema, indexes, retry policy, stuck-job recovery, cleanup, monitoring, and replay-safe handlers. ...
11 tools: search, page to Markdown, find similar, research, answer, crawl, site map, balance, free key and auto top-up. Exa- and Tavily-compatible API underneath, at contextfetch.dev.
Install
Claude Code (one line, keyless):
claude mcp add contextfetch -- npx -y @contextfetch/mcp
With a paid key:
claude mcp add contextfetch -e CONTEXTFETCH_API_KEY=your_key -- npx -y @contextfetch/mcp
Cursor: add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
{
"mcpServers": { "contextfetch": { "command": "npx", "args": ["-y", "@contextfetch/mcp"], "env": { "CONTEXTFETCH_API_KEY": "your_key" } } } }
Windsurf: add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": { "contextfetch": { "command": "npx", "args": ["-y", "@contextfetch/mcp"], "env": { "CONTEXTFETCH_API_KEY": "your_key" } } } }
To use the free tier, drop the env block (or leave CONTEXTFETCH_API_KEY empty). The same JSON works in Claude Desktop's claude_desktop_config.json and in any other MCP client that launches stdio servers.
Requires Node.js 18 or newer.
Tools
| Tool | Arguments | What it does | Cost |
|---|---|---|---|
contextfetch_search | query, num_results (1-25, default 5), include_domains?, exclude_domains? | Web search. Each result comes back as title, URL and only the passages relevant to your query (cross-encoder pruned Markdown). | $1 per 1,000 |
contextfetch_extract_url | url, query? | Any public page (docs, articles, GitHub files, arXiv) as clean Markdown with tables kept. With query, returns only the relevant passages. | $1 per 1,000 |
contextfetch_find_similar | url, num_results (1-25, default 5) | Pages similar to a URL, excluding its own domain. | $1 per 1,000 |
contextfetch_research | query, sub_queries? (up to 5), num_results_per_query (1-10, default 5) | Server-side research: runs the sub-queries concurrently, dedupes pages by URL, ranks them all against query with the cross-encoder and returns one Markdown evidence pack (numbered [n] sources with their query-pruned passages, quoted verbatim; nothing generated), headed by the sub-queries, source count, tokens and credits used. | $1 per 1,000 sub-queries (max 5) |
contextfetch_deep_research | query, sub_queries? (up to 3), num_results_per_query (1-25, default 5; at most 10 used) | The earlier name of contextfetch_research, kept for existing setups: same server-side evidence pack, up to 3 sub-queries. | $1 per 1,000 sub-queries (max 3) |
contextfetch_answer | query, num_results (1-10, default 5) | Extractive answer: the best-scoring passages of the top pages, quoted verbatim with [n] markers and a numbered source list. No text is generated, so it suits factual lookups more than open-ended questions. | $1 per 1,000 |
contextfetch_crawl | url, max_depth (0-3, default 1), limit (1-50, default 10), query?, include_paths?, exclude_paths? (regexes on the URL path) | Crawls one site from url (same-site links, robots.txt obeyed) and returns each page as Markdown with its depth. With query, pages are ranked by relevance and pruned to the relevant passages. | $1 per 1,000 pages |
contextfetch_map | url, limit (1-5,000, default 100), include_paths?, exclude_paths? | Lists a site's URLs from its sitemaps and the start page's links without fetching the pages. | $1 per 1,000 |
contextfetch_balance | none | Remaining credits, burn rate (credits/day over the last 7 days) and auto-reload settings, including the last auto-reload error if a payment failed. Needs CONTEXTFETCH_API_KEY. | free |
contextfetch_get_free_key | none | Claims the network's free API key (2,500 searches, one per network) and uses it for the rest of the session. Give it to your user to keep in CONTEXTFETCH_API_KEY. | free |
contextfetch_auto_reload | enabled, threshold? (100-100,000), pack? (instant, builder, scale), monthly_max_usd? (max 500) | Turns auto-reload on or off or changes it: when credits drop below threshold, the card saved at checkout buys pack again, up to the monthly cap. Needs CONTEXTFETCH_API_KEY and a saved card. The cap cannot go above $500 here. | free |
All tools return Markdown text. Without a key, contextfetch_balance and contextfetch_auto_reload return a short message saying they need one, with the buy link. On the free tier, results start with a one-line notice showing how many free searches are left today. When the API reports them, a closing line shows latency (total and per stage: recall, fetch, rerank), whether the answer came from cache, and token savings (pruned tokens vs raw page tokens).
contextfetch_research sub-queries
Pass your own sub_queries (different angles on the question); the tool description tells the calling model to do so. If you omit them, the API derives them from query with fixed rules:
- the query itself;
- the query +
documentation; - the query +
benchmarkwhen it mentions speed, performance, latency, memory or a comparison (vs,compare), otherwise the query +example.
A suffix the query already contains is skipped (so react useActionState example runs 2 searches, not 3). The whole research runs server-side in one /v1/research call that costs $1 per 1,000 sub-queries; a sub-query that fails is refunded and named in the header. If all fail, the tool returns the error.
Environment variables
| Variable | Default | Meaning |
|---|---|---|
CONTEXTFETCH_API_KEY | unset | Your API key. Unset or empty uses the free keyless tier. |
CONTEXTFETCH_API_BASE | https://api.contextfetch.dev | API base URL. Point it at your own engine if you self-host. |
Free tier and pricing
| Price | |
|---|---|
| No key | 25 searches a day per network, no signup |
Free key (contextfetch_get_free_key) | 2,500 searches, one per network, no card |
| Search, page to Markdown, answer, find similar, map | $1 per 1,000 |
| Crawl | $1 per 1,000 pages returned |
| Research | $1 per 1,000 sub-queries |
Pay as you go: top up from $10 (+10% from $100, +20% from $500). The balance never expires and one balance covers all your keys. Monthly plans and per-key limits are in the dashboard at contextfetch.dev/account.
When the balance or the free tier runs out (HTTP 402), the tool returns a one-click top-up link (Stripe: card, Apple Pay, Google Pay) and a line to pass on to your user. Then set CONTEXTFETCH_API_KEY as shown above.
Retries and connections
Connection failures before the request is sent (refused, DNS, connect timeout), HTTP 429 and HTTP 5xx are retried with exponential backoff and jitter (about 0.25-0.5 s, then 0.5-1 s), at most 3 attempts per API call and 30 seconds in total, retries included. A 429 or 5xx with a Retry-After header waits exactly that long, unless that would pass the 30 second budget. 400, 401, 402, 422 and other 4xx responses are never retried. A connection that drops after the request was sent is not retried either, since the search may already have been billed. Connections are pooled and kept alive by Node's built-in fetch (undici), so there is no extra HTTP dependency.
Errors
Errors never crash the server; they come back as tool results with isError: true and a plain explanation: invalid key (401), out of credits or free limit reached (402, lists the packs with their buy links), no saved card for auto-reload (409, with the buy link), URL not allowed (400, only public http(s) URLs), a page contextfetch_extract_url could not fetch (with the reason, such as HTTP 404), rate limited (429), server errors (5xx), network failures, and a 30 second limit per call (retries included).
Develop
npm install
npm run build # compiles src/ to dist/ and marks dist/index.js executable npm test # builds, then drives dist/index.js over stdio against a local mock API (no network) CONTEXTFETCH_API_BASE=http://localhost:8000 node dist/index.js
Publish
Publishing @contextfetch/mcp needs the npm organization contextfetch (create it at npmjs.com and add the publishing account as a member). Then npm publish from this folder; publishConfig.access is already public and prepublishOnly builds first.
License
MIT