A
licenseNot graded
qualityD
maintenanceMCP tool server that gives any AI agent the ability to search, scrape, and analyze content across the internet.
42
MIT
srezai-mcp
Officialby srezai-team
Related Servers
Alternatives to srezai-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to search the web and extract clean Markdown content, with support for JavaScript rendering, structured data extraction, and screenshots.1-
- AlicenseAqualityAmaintenanceAn MCP server providing web search, image search, and page scraping tools to LLMs without requiring API keys.312MIT
- AlicenseAqualityBmaintenanceMCP server that exposes SearXNG search and HTTP fetch tools for AI agents, enabling web search and clean page text extraction via natural language.4MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that provides web search and web page content extraction tools using Tavily's API, enabling agents to retrieve current information from the web.-
- AlicenseBqualityDmaintenanceMCP server providing search, extract, map, and crawl tools powered by Tavily for real-time web data access.411 npmMIT
TDQS
A4.7/5.0
Scored across 8 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: deep_research for synthesized multi-source answers, web_search for ranked results, image_search for images, read_url for single-page text, read_urls for batch reading, fetch_page for visual screenshots, extract for structured data, and get_usage for account info. No two tools overlap in a way that would confuse an agent.
Naming Consistency4/5
Most tools follow a verb_noun snake_case pattern (web_search, read_url, read_urls, fetch_page, get_usage), but 'deep_research' is an adjective_noun compound and 'extract' is a bare verb. This is a minor deviation from an otherwise consistent and predictable convention.
Tool Count5/5
With 8 tools, the server is well-scoped for its stated purpose of web research and data extraction. Each tool earns its place, covering search, reading, extraction, and account management without any redundant or bloated additions.
Completeness5/5
The tool surface covers the full research workflow: discovering sources (web_search, image_search), deep investigation (deep_research), reading content (read_url, read_urls, fetch_page), structured extraction (extract), and operational monitoring (get_usage). There are no obvious gaps within the domain.
Maintenance
ActivityMaintained
ResponsivenessNo issues