ToolsMCP
YaCy peer-to-peer search
Listed in the official MCP Registry with an installable oci package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- pad01g (GitHub)
- Prerequisites
- Install ghcr.io/pad01g/yacy-search-mcp:1.0.0 from oci (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.0.0 · updated
- Official links
Publisher’s description
Web search, crawling and ranking evaluation on your own YaCy peer: no API key, no central service.
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 1.0.0, registry status active. 1 package (oci)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- pad01g (GitHub)
- Version observed
- 1.0.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.pad01g%2Fyacy-search/versions/1.0.0
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
ghcr.io/pad01g/yacy-search-mcp:1.0.0(oci, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.pad01g/yacy-search
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.