Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 0
- 4 3
- 3 5
- 2 6
- 1 2
Trust in production
- Trust it - 0%
- With caveats - 44%
- Wouldn't - 56%
25% would recommend this server
How reviewers scored it
- Setup & docs 2.8
- Auth experience 2.6
- Reliability 2.4
- Maintainer responsiveness 3.5
Why it got a D
A reference server, meant as a teaching example rather than for production. It fetches any URL the model asks for, and page text can carry prompt injection. October's SSRF flaw (CVE-2026-104120) was fixed in 2026.10.10 and two bypasses in 2026.10.24, so use 2026.10.24 or later and never add --allow-private-ips. Biggest deduction: the SSRF was public for about five weeks before the fix, and the guard still doesn't stop DNS rebinding.
How to connect
// .vscode/mcp.json (README uvx config)
{ "mcp": { "servers": { "fetch": { "command": "uvx", "args": ["mcp-server-fetch"] } } } }// claude_desktop_config.json (README uvx config)
{ "mcpServers": { "fetch": { "command": "uvx", "args": ["mcp-server-fetch"] } } }Is Fetch MCP Server safe?
Is Fetch MCP Server safe to use?
Fetch MCP Server grades D (notable weaknesses - review closely). There is no login: anything that can start or reach it gets its full access. Past advisories were fixed slowly, so stay on the latest release. It shells out to helper programs or serves HTTP without enforced TLS, so keep it local and isolated.
Does Fetch MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Fetch MCP Server support authentication?
No. It has no login of its own, so limit who and what can start it.
Alternatives in Docs & Knowledge
- A Context7 MCPPulls version-accurate library documentation into the model context.
- B Stack Overflow MCP ServerOfficial hosted Stack Overflow server (beta) to search questions and answers.
- B Zotero MCP (zotero-mcp-server)A community MCP server for your Zotero library, run locally from PyPI, to search, read and annotate papers, add items by DOI or BibTeX, and manage collections and tags.
- C AIOS Public Discovery MCP ServerHosted server that checks the status, recent changes and source evidence of five monitored GOV.UK employment guidance topics, including minimum wage and statutory sick pay.
- C AWS Knowledge MCP ServerAWS's hosted read-only server for AWS docs, API references, regional availability and agent skills.
Embed this badge
[](https://trustedmcp.io/servers/fetch-mcp-server)<a href="https://trustedmcp.io/servers/fetch-mcp-server"><img src="https://trustedmcp.io/badge/fetch-mcp-server.svg" alt="TrustedMCP grade D" height="80"></a>Community reviews
Not ready for anything that matters
Ran into problems pretty quickly. Watch out for instructions hidden in the data it reads. I review actions before approving them. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out. Releases come often and the changelog is clear.
Used for Answering questions from our internal wiki
- Setup & docs 2/5
- Auth experience 2/5
- Reliability 1/5
- Maintainer responsiveness 2/5
Went back to calling the API directly
Setup was rough and the result was flaky. Filed an issue and got a reply within two days. Anything it pulls in I treat as untrusted, prompt injection through content is a real risk here. There is no auth layer, so whatever can reach it can use it. I keep it local only. For anything real I would look elsewhere.
Used for Onboarding Q&A for new hires
- Setup & docs 1/5
- Auth experience 2/5
- Reliability 1/5
- Maintainer responsiveness 2/5
Handy for dev, careful in prod
Useful tool, though I would not hand it to a junior unsupervised. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. Anything it pulls in I treat as untrusted, prompt injection through content is a real risk here. You can tell it is actively maintained, the rough edges keep getting fixed.
Used for Summarising meeting notes
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 5/5
The Fetch integration I wanted
Our agents call this dozens of times a day. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. Worth it, just do not skip the hardening steps.
Used for Answering questions from our internal wiki
- Setup & docs 4/5
- Auth experience 2/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Fine once configured properly
Some tools are great, a couple feel half finished. You can tell it is actively maintained, the rough edges keep getting fixed.
Used for Summarising meeting notes
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Clean integration, sensible permissions
Set this up for our team after comparing a few options. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. Anything it pulls in I treat as untrusted, prompt injection through content is a real risk here. I would use it in prod, but only with a human approving writes.
Used for Drafting docs from existing pages
- Setup & docs 4/5
- Auth experience 2/5
- Reliability 4/5
- Maintainer responsiveness 4/5
OK for read-only work
It does the job, but it took some tweaking. There is no auth layer, so whatever can reach it can use it. I keep it local only. Watch out for instructions hidden in the data it reads. I review actions before approving them. Releases come often and the changelog is clear.
Used for Drafting docs from existing pages
- Setup & docs 4/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Works, just lock it down
Took longer to configure than I expected. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. Releases come often and the changelog is clear.
Used for Onboarding Q&A for new hires
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 5/5
Would not run this unattended
Gave it a fair shot over two weeks. You can tell it is actively maintained, the rough edges keep getting fixed. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box.
Used for Keeping a team knowledge base tidy
- Setup & docs 2/5
- Auth experience 2/5
- Reliability 2/5
- Maintainer responsiveness 2/5
Struggled to get it stable
Ran into problems pretty quickly. Anything it pulls in I treat as untrusted, prompt injection through content is a real risk here. Filed an issue and got a reply within two days. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. Keeping it to local experiments for now.
Used for Finding the right runbook during incidents
- Setup & docs 1/5
- Auth experience 2/5
- Reliability 2/5
- Maintainer responsiveness 4/5
Surprisingly polished
Installed it on a Friday, it was part of my workflow by Monday. There is no auth layer, so whatever can reach it can use it. I keep it local only. Updates land regularly, and nothing broke when I upgraded. Recommended, with sensible guardrails.
Used for Answering questions from our internal wiki
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Security story needs work
Not what I expected from the description. Local stdio process, easy to start and stop from the client. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. Keeping it to local experiments for now.
Used for Finding the right runbook during incidents
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 4/5
Too much access for my comfort
I wanted to like this one. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out. Watch out for instructions hidden in the data it reads. I review actions before approving them. There is no auth layer, so whatever can reach it can use it. I keep it local only. Not something I would put in production yet.
Used for Pulling up-to-date library docs into prompts
- Setup & docs 1/5
- Auth experience 3/5
- Reliability 1/5
- Maintainer responsiveness 3/5
Decent, not set-and-forget
I like it, with reservations. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box.
Used for Pulling up-to-date library docs into prompts
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Fine for a demo, not for prod
It works in a demo, but things got shaky under real use. Local stdio process, easy to start and stop from the client. Updates land regularly, and nothing broke when I upgraded.
Used for Keeping a team knowledge base tidy
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 2/5
Needs more maintenance love
Gave it a fair shot over two weeks. There is no auth layer, so whatever can reach it can use it. I keep it local only. Watch out for instructions hidden in the data it reads. I review actions before approving them. I will check back in a few releases.
Used for Keeping a team knowledge base tidy
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 1/5
- Maintainer responsiveness 3/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.