ToolsMCP
web-retrieval-mcp
Listed in the official MCP Registry with an installable pypi package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- velvetsp (GitHub)
- Prerequisites
- Install web-retrieval-mcp from pypi (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.1.2 · updated
- Official links
Publisher’s description
MCP web search + tiered web fetch for AI agents (Exa, Firecrawl), SSRF-guarded, cross-platform.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.2, registry status active. 1 package (pypi)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- velvetsp (GitHub)
- Version observed
- 0.1.2
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.VelvetSP%2Fweb-retrieval-mcp/versions/0.1.2
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Search the web with sources | Publisher description mentions “web search”. | No connection check or task run. Capability is as described by the publisher. | Rule web-search matched: “web search”. Rule web-search. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
web-retrieval-mcp(pypi, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.VelvetSP/web-retrieval-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.