ContextFetch
REMOTE · API.CONTEXTFETCH.DEV · 2 COMPONENTS
Web search and any page as LLM-ready Markdown for AI agents. Free keyless tier, no signup.
Available components
Last scanned (11 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1747 tokens (~134/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
- Tool “contextfetch_research” rewrote its description, which is the text the model reads security
- Tool “contextfetch_deep_research” rewrote its description, which is the text the model reads security
- 22 Oct 26 0
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool “contextfetch_deep_research” rewrote its description, which is the text the model reads security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.10 ▲ functional
- “contextfetch_search” added an optional parameter “start_published_date” cosmetic
- “contextfetch_search” added an optional parameter “time_range” cosmetic
- “contextfetch_search” added an optional parameter “topic” cosmetic
- “contextfetch_search” added an optional parameter “category” cosmetic
- “contextfetch_search” added an optional parameter “country” cosmetic
- “contextfetch_search” added an optional parameter “end_published_date” cosmetic
- “contextfetch_search” added an optional parameter “language” cosmetic
- 21 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- 20 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 19 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://api.contextfetch.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.contextfetch.dev | CN=YE1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 559decf5c366eaf2781e9b85bde96e05e3a |
| SANs: api.contextfetch.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.contextfetch.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| contextfetch.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.contextfetch.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.contextfetch.dev/mcp | HTTPS enforced | 308 | https://api.contextfetch.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
contextfetch_answer ContextFetch extractive answer ~105
Answer 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 open-ended question. Costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| num_results | integer | – | Pages searched for passages (1-10, default 5). |
| query | string | yes | The question. |
No output schema declared.
No examples provided.
contextfetch_auto_reload ContextFetch auto-reload ~170
Turn auto-reload on or off, or change it: when credits drop below `threshold`, the saved card buys `pack` again, 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.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | true to turn auto-reload on, false to turn it off. |
| monthly_max_usd | number | – | Monthly spending cap in USD (at most 500). |
| pack | string | – | Pack to buy: instant $15/15,000, builder $50/60,000, scale $150/200,000. |
| threshold | integer | – | Reload when credits drop below this (100-100,000, default 1,000). |
No output schema declared.
No examples provided.
contextfetch_balance ContextFetch balance ~55
Show the API key's remaining credits, daily burn rate (7-day average) and auto-reload settings, including the last auto-reload error if a payment failed. Needs an API key (Authorization: Bearer); free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
contextfetch_crawl ContextFetch site crawl ~196
Crawl 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 1 credit per page returned.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_paths | array | – | Regexes; never follow links whose path matches one. |
| include_paths | array | – | Regexes; only follow links whose path matches one, e.g. ["^/docs/"]. |
| limit | integer | – | Maximum pages to return (1-50, default 10). |
| max_depth | integer | – | Link hops from the start page (0-3, default 1). |
| query | string | – | Optional topic: ranks pages and prunes each to the relevant passages. |
| url | string | yes | Public http(s) start URL. |
No output schema declared.
No examples provided.
contextfetch_deep_research ContextFetch deep research ~164
Deep 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 passage quoted verbatim with [n]. Costs 1 credit. For a quick evidence pack use contextfetch_research.
| Name | Type | Req | Description |
|---|---|---|---|
| num_results_per_query | integer | – | Results per sub-query (1-25, default 5; at most 10 are used). |
| query | string | yes | The research question. |
| sub_queries | array | – | Up to 3 search queries covering different angles of the question. Strongly recommended. |
No output schema declared.
No examples provided.
contextfetch_extract_url ContextFetch URL to Markdown ~85
Fetch 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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional question or topic; returns only the relevant passages. |
| url | string | yes | Public http(s) URL to read. |
No output schema declared.
No examples provided.
contextfetch_find_similar ContextFetch find similar pages ~83
Find 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.
| Name | Type | Req | Description |
|---|---|---|---|
| num_results | integer | – | Number of results to return (1-25, default 5). |
| url | string | yes | Public http(s) URL to find similar pages for. |
No output schema declared.
No examples provided.
contextfetch_get_free_key ContextFetch free starter key ~64
Get a free ContextFetch API key (no signup, no payment) with starter credits, for when the keyless daily limit runs out. One key per network, ever: keep the key it returns and use it as `Authorization: Bearer <key>`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
contextfetch_map ContextFetch site map ~165
List 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 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_paths | array | – | Regexes; never list URLs whose path matches one. |
| include_paths | array | – | Regexes; only list URLs whose path matches one, e.g. ["^/blog/"]. |
| limit | integer | – | Maximum URLs (1-5,000, default 100). |
| url | string | yes | Public http(s) URL of the site (any page on it). |
No output schema declared.
No examples provided.
contextfetch_research ContextFetch research (evidence pack) ~191
Research 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, quoted verbatim (no generated text). Costs 1 credit. Pass your own `sub_queries` (distinct angles on the question) for better coverage; if omitted they are derived from `query`: the query, query + "documentation", and query + "benchmark" (speed or comparison questions) or + "example".
| Name | Type | Req | Description |
|---|---|---|---|
| num_results_per_query | integer | – | Results per sub-query (1-10, default 5). |
| query | string | yes | The research question. |
| sub_queries | array | – | Up to 5 search queries covering different angles of the question. Recommended. |
No output schema declared.
No examples provided.
contextfetch_search ContextFetch web search ~310
Search 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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Focus on one kind of page: company, research paper, news, pdf, github, personal site, linkedin profile, financial report, people. |
| country | string | – | Two-letter country code (US, DE): that country's results rank higher. |
| end_published_date | string | – | Only pages published on or before this date (YYYY-MM-DD). |
| exclude_domains | array | – | Never return results from these domains. |
| include_domains | array | – | Only return results from these domains, e.g. ["docs.python.org"]. |
| language | string | – | Two-letter language code (en, de): results in that language rank higher. |
| num_results | integer | – | Number of results to return (1-25, default 5). |
| query | string | yes | Natural-language search query. |
| start_published_date | string | – | Only pages published on or after this date (YYYY-MM-DD). Undated pages are dropped. |
| time_range | string | – | Only pages published in the last day, week, month or year. |
| topic | string | – | news: news sources, recent pages first. finance: SEC filings and finance sites. Default general. |
No output schema declared.
No examples provided.
fetch Fetch ~54
Fetch the full text of a search result by its id (a URL). Returns {id, title, text, url, metadata} as JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | An id from `search` (the page URL). |
No output schema declared.
No examples provided.
search Search ~47
Search the web. Returns {results: [{id, title, url}]} as JSON; pass an id to `fetch` for the page text.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query. |
No output schema declared.
No examples provided.
How do I install the ContextFetch MCP server?
ContextFetch is a hosted endpoint at https://api.contextfetch.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.contextfetch.dev
claude mcp add --transport http dev-contextfetch-mcp 'https://api.contextfetch.dev/mcp'
What is the ContextFetch MCP server?
ContextFetch is an MCP server listed in the public MCP registry as dev.contextfetch/mcp. Web search and any page as LLM-ready Markdown for AI agents. Free keyless tier, no signup. This page covers its hosted endpoint (https://api.contextfetch.dev/mcp).
Is the ContextFetch MCP server safe to use?
ContextFetch scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ContextFetch MCP server expose?
ContextFetch exposes 13 tools: contextfetch_search, contextfetch_extract_url, contextfetch_find_similar, contextfetch_research, contextfetch_deep_research, and 8 more. Their descriptions and schemas cost roughly 1,689 tokens of context every time the server is loaded.
Does the ContextFetch MCP server require authentication?
No. We connected to ContextFetch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ContextFetch MCP server still maintained?
ContextFetch is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.