Agentreader MCP vs Fetcher
A side-by-side look at the Agentreader MCP and Fetcher MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agentreader MCP for finance & fintech work as a local process; choose Fetcher for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agentreader MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
AGENTREADER_PRIVATE_KEY. - You want tools like
read_page, page_metadata, clean_html.
Choose Fetcher when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 52/100 · Good | 54/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | AGENTREADER_PRIVATE_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 13 | Not listed |
| Full listing | View Agentreader MCP | View Fetcher |
Tools & capabilities
Agentreader MCP tools 13
read_pageWeb page → clean LLM-ready markdown articlepage_metadataTitle, OpenGraph, Twitter cards, JSON-LD, headingsclean_htmlRaw HTML → markdownpdf_textPDF URL → full text (up to 25 MB)parse_feedRSS/Atom/RDF feed → normalized JSON itemsparse_sitemapXML sitemap → URL listextract_linksPage link graph with anchor textdns_lookupDNS records with TTLsscreenshotReal-browser PNG screenshotsummarizeAI summary of URL or text (dense, factual)extract_structuredPage/text → JSON matching **your** JSON Schemasanctions_screenOFAC SDN + Consolidated screening: fuzzy transliteration-aware name match or crypto-address lookup, with verdict + list provenance- +1 more on the listing page
Fetcher tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Agentreader MCP
{
"mcpServers": {
"agentreader-mcp": {
"command": "npx",
"args": [
"-y",
"agentreader-mcp"
],
"env": {
"AGENTREADER_PRIVATE_KEY": "YOUR_AGENTREADER_PRIVATE_KEY_HERE"
}
}
}
}
Fetcher
{
"mcpServers": {
"fetcher-2": {
"url": "https://api.fetcher.cloud/capabilities"
}
}
}
Frequently asked questions
Agentreader MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Fetcher belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Agentreader MCP for finance & fintech work and Fetcher for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Agentreader MCP has no declared pricing — check the project's own site. Fetcher has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agentreader-mcp and fetcher-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agentreader MCP has a quality signal of 52/100 (Good) with 3 views, 0 installs and 0 GitHub stars. Fetcher has 54/100 (Good) with 1 views, 0 installs and 0 GitHub stars.