Library
com.siftdexPublished by siftdex.comOfficial publisherv0.1.0Updated Oct 24, 2026
Verified doc corpora for agents: grep-first retrieval, hashed pages, Merkle+RFC-3161 receipts
Overview
Gives an assistant grep-style retrieval over verified document corpora, with hashed pages and Merkle plus RFC-3161 receipts.
- What you can do
- This remote server exposes verified document corpora to an agent. Its stated approach is grep-first retrieval, so the assistant searches corpus text directly rather than relying on embeddings. Pages are hashed, and results come with Merkle and RFC-3161 receipts that let a caller check the retrieved content against a recorded state. No individual tools are listed in the manifest.
- When to use it
- Worth adding when an assistant needs to search a curated document collection and the provenance or integrity of the retrieved text matters. Less useful for general web search or for corpora that are not already published through this service. The manifest lists no tools, so confirm the available operations before depending on it.
- Requirements
- A remote MCP endpoint at over streamable HTTP. No packages, environment variables, headers, or authentication are declared, so no local runtime or credentials appear to be needed; network access to the endpoint is required.
Installation
In SourceWeft
- Open Library in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.siftdex%2Flibrary/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"library": {
"type": "http",
"url": "https://library.siftdex.com/mcp"
}
}
}Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.