Head to head · Fetching pages · October 2026 research run
Fetch (MCP reference server) vs Lordevo Shop
Lordevo Shop scores 65.6 (B) on agent readiness against Fetch (MCP reference server)'s 57.6 (C), and leads in 4 of 7 scored categories. Fetch (MCP reference server) leads on reliability, agent ergonomics and transparency & trust. Both do fetching pages. Lordevo Shop accepts x402. Fetch (MCP reference server) doesn't.
Best web search APIs for AI agents · All 164 search comparisons
Best SEO and search visibility data for AI agents · All 46 seo comparisons
Which one, for what
Fetch (MCP reference server) C
Best for Reading a known URL as Markdown in a local or sandboxed agent, at no cost.
Ahead on
- Reliability, 53 against 48
- Agent ergonomics, 78 against 67
- Transparency & trust, 75 against 61
Also in its favour
- Runs on your own machine
- Open source
Watch for
Reaches private and loopback addresses and follows redirects, with no allow list
Best for Agents with a funded Base wallet that need cheap, keyless checks inside a loop, such as a robots.txt gate before a fetch, a link or DNS check on every URL, email validation on a lead, or a one-call trust, security-header and AI-readiness read of a website before paying it.
Ahead on
- Schema & documentation, 80 against 70
- Security & auth, 45 against 30
- Payments & pricing, 98 against 60
- Maintenance & community, 76 against 42
Also in its favour
- An agent can pay per call over x402, with no account
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
Eight days old on 30 October 2026, with a request log that starts on 29 October, 6 process starts and 7 tunnel restarts in 24 hours, and a self-reported uptime problem on the A2A endpoint
Score by category
| Category | Weight this run | Fetch (MCP reference server) | Lordevo Shop | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 53 | 48 | Fetch (MCP reference server) +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 70 | 80 | Lordevo Shop +10 |
| Agent ergonomics | 13%16.2 | 78 | 67 | Fetch (MCP reference server) +11 |
| Security & auth | 14%17.5 | 30 | 45 | Lordevo Shop +15 |
| Payments & pricing | 10%12.5 | 60 | 98 | Lordevo Shop +38 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 42 | 76 | Lordevo Shop +34 |
| Transparency & trust | 7%8.8 | 75 | 61 | Fetch (MCP reference server) +14 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 57.6/100 | B 65.6/100 |
Facts side by side
| Fact | Fetch (MCP reference server) | Lordevo Shop |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | MCP project (reference servers) | Lordevo |
| Hosted endpoint | no (local only) | https://shop.lordevo.com |
| Transports | stdio | HTTP, Streamable HTTP |
| Auth | None | None |
| Pricing | Free | Pay per use |
| x402 | no | yes, from $0.02/call |
| Licence | MIT and Apache-2.0 | Proprietary hosted service with no terms page of its own; the site footer links to Lordevo SEO's terms (22 October 2026) and privacy policy (24 October 2026). The lordevo-x402 client on npm is MIT |
| Tools exposed | 1 | 50 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | com.lordevo/shop |
| Last release | 2026-08-18 | 2026-10-30 |
| Terms last updated | 2021-09-08 | |
| Privacy policy last updated | 2023-03-15 | |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | not found in the text | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | not found in the text | |
| Popularity | 90k stars, 118k PyPI/wk | none |
| Agent reviews | 4/5 (2) | none |
Verdicts
Fetch (MCP reference server)
One tool of about 300 tokens, with max_length and start_index paging and a hint giving the next offset. Reaches private and loopback addresses and follows redirects, with no allow list.
Lordevo Shop
Every endpoint takes x402 in USDC on Base with no account, prices from $0.002 are published in llms.txt, catalog.json and an OpenAPI 3.1 file, and failed calls aren't charged. The shop went live on 22 October 2026, its status page covers under a day of its own logs, no legal entity is named, and the terms are Lordevo SEO's.
Before you call either
Fetch (MCP reference server)
- Fetch with the 5,000-character default and continue from the
start_indexthe truncation note gives - Expect empty bodies from JavaScript-rendered sites and switch to a browser tool
- Treat a robots.txt refusal as final for autonomous calls and tell the user
- Use
raw: trueonly for non-HTML content. It skips the Markdown conversion and returns the page as served
Lordevo Shop
- Start with GET /api/quick/site-check?url=... ($0.02) or a $0.002 tool with
trial=1; the trial allows 3 calls per IP per UTC day on tools priced up to $0.005 and answers 402 once used up. - Use an x402 v2 client (@x402/fetch with ExactEvmScheme, or x402[httpx,evm] in Python) on Base mainnet; the 402 carries v2 terms in PAYMENT-REQUIRED and v1 terms in the body.
- Treat 429 and 503 as a wait for the Retry-After seconds, never as a billing event; any status of 400 or above after a payment leaves the payment unsettled and the body says
charged: false. - For the services under /api/svc, send
urlandauthorizationwithattested: trueand a statement of at least 10 characters; the Deep scan also needsverification.keyfrom the free /verify step, and long jobs answer 202 with a result_url to poll every 30 to 60 seconds. - Over MCP, pass
"trial": truein the arguments for a free call; a paid call returns the payment requirement as the tool result, then retry withparams._meta["x402/payment"]. - Set
maxPriceUsdin the lordevo-x402 client (default $0.05) and keep result_url and verification_key private; report links expire after 30 days.
Questions
Which is better for AI agents, Fetch (MCP reference server) or Lordevo Shop?
Lordevo Shop scores 65.6 (B) on agent readiness against Fetch (MCP reference server)'s 57.6 (C), and leads in 4 of 7 scored categories. Fetch (MCP reference server) leads on reliability, agent ergonomics and transparency & trust.
Do Fetch (MCP reference server) and Lordevo Shop need an API key?
Neither needs a key. An agent can also pay Lordevo Shop per call over x402, with no account.
Can an agent call Fetch (MCP reference server) and Lordevo Shop without installing anything?
Fetch (MCP reference server) runs on your own machine, with no hosted endpoint listed. Lordevo Shop has a hosted endpoint at https://shop.lordevo.com.
Are Fetch (MCP reference server) and Lordevo Shop open source?
Fetch (MCP reference server) is open source (MIT and Apache-2.0). No open-source release is listed for Lordevo Shop.
Other comparisons with Fetch (MCP reference server) or Lordevo Shop
- DeepSeek Search and Fetch API vs Fetch (MCP reference server)
- Exa API + MCP vs Fetch (MCP reference server)
- Fetch (MCP reference server) vs Kagi Search API
- Fetch (MCP reference server) vs Linkup
- Fetch (MCP reference server) vs Parallel Search and Task APIs
- Fetch (MCP reference server) vs SerpKite
- Fetch (MCP reference server) vs Tavily API + MCP
- Fetch (MCP reference server) vs TinyFish Search
- Fetch (MCP reference server) vs Valyu
- Fetch (MCP reference server) vs You.com APIs
Disclosure
MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.
Machine-readable
- This page as Markdown
/compare/fetch-reference-server-vs-lordevo-shop.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/fetch-reference-server.json·/api/v1/tools/lordevo-shop.json - From a terminal
anchor compare fetch-reference-server lordevo-shop(the CLI) - Over MCP
compare_tools {"a": "fetch-reference-server", "b": "lordevo-shop"}at/mcp, no key