FATSEARCH MCP server
io.github.fatsearch/fats·v0.2.4·49 starsWeb pages, PDFs and documents as small, clean, cached Markdown for AI agents
49 stars
Reviews
Write oneNobody has reviewed FATSEARCH yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
FATSEARCH tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How FATSEARCH compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,255 servers
- GitHub stars
- 49
- more than 94% of 28,688 servers
Install FATSEARCH in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the FATSEARCH repository's README, as published. We do not edit it. Read it on GitHub
Reads the pages your agent's built-in fetch can't (JS pages, PDFs) through your own provider key, kept on disk as clean Markdown, navigated by outline and ids.
same question · same answer · 81× less context That's the point.
Every page your agent reads costs you this
Your agent gets a short outline. It reads one section when it needs depth, not the whole page. Menus, cookie banners, navigation, footer links, tracking scripts: gone. Prices, dates, numbers: kept (loss guard counts every one).
[!TIP]
The "free" fetch costs ~100× more at the model. And it stays in context, every turn after.
Your key never touches the chat
fats setup opens a one-time key form on 127.0.0.1, behind a random token, for 30 minutes. You paste the key there in your browser, so it stays out of the chat, the model's context and the agent's logs. The form refuses a POST from another origin; the key is checked live, saved with mode 0600, sent only to its provider.
$ fats setup decodo
= setup decodo · waiting for the key at http://127.0.0.1:59802/k/e0c8baba7a5b058947f4fdab97dabb05/decodo · 30 min · $0
tell the user (never ask for the key in chat):
1. open https://dashboard.decodo.com/web-data/playground (no account yet: https://dashboard.decodo.com/register)
2. Copy the API key shown on the Web Data playground. Do NOT paste it in this chat.
3. open http://127.0.0.1:59802/k/e0c8baba7a5b058947f4fdab97dabb05/decodo , paste the key, press Save
then: fats setup (when the user says done; end your turn, do not poll · checks it, $0)
link dead (30 min passed)? run fats setup decodo again and give the user the new line 3fats setup shows a form still waiting (! formwaiting decodo · 23 min left · ) or one whose time ran out (! formexpired decodo · the link the user got is dead → fats setup decodo · new link, same 3 steps). Over SSH (SSHCONNECTION or SSHTTY set) one more line says how to paste the key in a terminal there.
On hard pages
fats tries plain HTTP first (free). If the page is a JS shell, a captcha, or a wall, it climbs to your providers: cheapest first, hedged, with cost tracking on every call.
$ fats https://www.nytimes.com/ dry:true
nytimes.com/ fetch plain → oxy (after a captcha) → bd ∥ oxyjs after 5s → new u1 · up to $0.0040Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
FATSEARCH: common questions
- Is FATSEARCH MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the FATSEARCH safety report
- Does FATSEARCH need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is FATSEARCH maintained?
- The last commit was 13 days ago (2026-10-22). The latest release is v0.2.4.
- What can I use instead of FATSEARCH?
- Servers from other publishers that do the same job: kordoc MCP server, Front-End Checklist MCP server and Docling MCP server. Compare all FATSEARCH alternatives.
- How does FATSEARCH compare with other MCP servers?
- safety score 85/100 (higher than 70% of 48,255 servers); github stars 49 (more than 94% of 28,688 servers). Full comparison.
Alternatives to FATSEARCH
Same job from other publishers: the closest match first, then the best rated.
- kordocParse Korean documents (HWP, HWPX, PDF, XLSX, DOCX, PPTX) to Markdown; fill forms, diff, render.not reviewedWidely usedA
Front-End ChecklistReview frontend code and live pages against 386 quality-gated web development rules.not reviewedWidely usedA- Docling MCPConvert PDFs and other documents to structured formats via Docling, for AI applications.not reviewedEstablishedA
