MCP servers for web fetching, search engines, crawling and content extraction. Each entry is scanned with the deterministic Capability-Flow Trust Model — grades are computed, never self-reported.
Firecrawl’s official MCP server: scrape, crawl and extract structured data from websites.
Tavily’s official MCP server: AI-grade web search, extraction and crawling.
Security scan results for the Trello MCP server.
Security scan results for the Zuplo MCP server.
Exa’s official MCP server: semantic web search built for AI agents.
Fetches web content with automatic image saving and optional AI display.
Modular, extensible integration with DataForSEO API endpoints, supporting both HTTP and SSE transports.
Security scan results for the Polaris MCP server.
Security scan results for the Ticketmaster MCP server.
Google Search Console server with 20 SEO analysis tools including quick wins, traffic drops, content decay, cannibalisation, CTR opportunities, and multi-site dashboards; supports OAuth and service accounts.
Security scan results for the Jira MCP server.
Server for interacting with MediaWiki wikis.
Fetches deepwiki.com content and converts it into LLM-readable markdown.
Security scan results for the Morphmcp MCP server.
Security scan results for the Apple Doc MCP server.
Fetches and processes web content for AI assistants.
Real-time U.S. National Park Service data including park details, alerts, and activities.
Security scan results for the Tmdb MCP server.
Security scan results for the Hyperbrowser MCP server.
Security scan results for the Spartan Ng MCP server.
Security scan results for the Brapi MCP server.
Integrates with Jina AI APIs to provide web page reading and web search tools.
Security scan results for the Toolkit MCP server.
Security scan results for the Web Probe MCP server.
A search index queried mid-conversation, a page fetched and stripped to clean text, a headless browser rendering JavaScript that no plain HTTP request could reach — that is the territory this category covers. These MCP servers use the Model Context Protocol to expose search engines and APIs like Brave Search, Tavily, Exa and SearXNG, simple fetch utilities, browser-automation stacks such as Playwright and Puppeteer, and Firecrawl-style crawling frameworks as tools that Claude, Cursor and other LLM clients can call directly. The result is an assistant that answers from the live web instead of stale training data. Browse the full MCP Trust Registry to compare candidates side by side.
Every fetched page is untrusted input, which makes this the category most exposed to prompt injection: a poisoned page can smuggle hidden instructions into the model's context, right next to yours. An over-permissioned fetch tool also doubles as a server-side request forgery hazard, reaching localhost services, internal dashboards or cloud metadata endpoints unless URLs are restricted. Attacker-shaped links can quietly exfiltrate conversation data through query strings, and headless-browser servers pile form submission and arbitrary script execution on top. Each listing therefore carries a Trust Score from the deterministic scoring engine, which reads the published package, maps its capability blast radius and toxic-flow paths, and grades it A–F — identical input always yields the identical grade, and no ranking can be bought.
Look for tight network scoping first: domain allowlists, no write-capable tools bundled beside fetch, and a strong Trust Score backed by clean security findings. Treat everything a server retrieves as data, never as instructions to follow. Reviewing the evidence attached to each registry listing before installing takes minutes and rules out the worst offenders.