Compare · Web Search
Fetch vs Jina MCP Local MCP Server
Fetch exposes 1 tools and adds about 235 tokens to every model turn. Jina MCP Local exposes 17 tools and adds about 3,529. Jina MCP Local costs 15.0× as much context. Measured by connecting to each server and counting its tool list, not from the README.
| Context tax | ~235 tok/turn(leaner) | ~3,529 tok/turn |
|---|---|---|
| Tools | 1 | 17 |
| Cost per 1,000 turns (Claude Sonnet 5.5, uncached) | $0.47 | $7.06 |
| Security score | 95/100 | 97/100 |
| Cold start | 3,873 ms | 799 ms |
| Runs | Local (stdio) | Local (stdio) |
| Needs keys | None declared | None declared |
| Freshness | Active | Active |
| GitHub stars | 91k | 884 |
| License | — | Apache-2.0 |
| Official MCP registry | No | No |
Install in Claude Code
Jina MCP Local
claude mcp add jina-mcp-local -- npx -y jina-mcp-local
Tools
By name, from each server's live tool list. The same name can still behave differently.
Only in Fetch · 1
- fetch
In both · 0
- none
Only in Jina MCP Local · 17
- show_api_key
- primer
- guess_datetime_url
- capture_screenshot_url
- read_url
- search_web
- search_arxiv
- search_ssrn
- search_images
- parallel_search_web
- parallel_search_arxiv
- parallel_search_ssrn
- parallel_read_url
- sort_by_relevance
- deduplicate_strings
- deduplicate_images
- search_bibtex
Questions
- Which uses fewer tokens, Fetch or Jina MCP Local?
- Fetch: its tool definitions take about 235 tokens per turn against 3,529 for Jina MCP Local (15.0× more). Tool definitions are resent on every model turn.
- Do Fetch and Jina MCP Local have the same tools?
- No tool names overlap: Fetch has 1 tools and Jina MCP Local has 17.
- Are Fetch and Jina MCP Local hosted or local?
- Fetch: local (stdio). Jina MCP Local: local (stdio).
Token counts use the o200k tokenizer on each server's tool definitions as an agent receives them; clients that load tools lazily pay less. Prices are Claude Sonnet 5.5 input at $2/MTok. Want to check one yourself? Run npx mcpskillhub test <package> — how it works.