
Dark Search Protocol
io.github.parnasheps-engPublished by GitHub account parnasheps-engv0.8.0Updated Oct 24, 2026
161 dark data sources, 25+ domains, 6-step pipeline, Streamable HTTP + stdio
Overview
Runs a local search pipeline across many dark data sources and domains, exposing results to an assistant over stdio.
- What you can do
- Dark Search Protocol is a local MCP server distributed as the npm package dark-search-mcp-server and started with npx over stdio. Its description states it covers 161 dark data sources across 25 or more domains and runs a 6-step pipeline, and that it supports Streamable HTTP in addition to stdio. No individual tools are listed in the manifest, so the exact operations an assistant can call are not documented here.
- When to use it
- Consider it when an assistant needs to query sources that are not part of the ordinary indexed web and the user is willing to run a local process. It is a desktop-only server, so it is not usable from a browser-based client. Because the tool list is not published, verify the actual capabilities before relying on it.
- Requirements
- A local Node.js runtime able to run the npm package dark-search-mcp-server with npx, on a desktop machine. The manifest declares no authentication, no environment variables and no headers, so no credentials are documented as required. Network access is implied by the search function but is not stated.
Installation
In SourceWeft
- Open Dark Search Protocol in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.8.0LatestSep 16, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.