Developer · Local MCP server
SearchForge
Free open-source web search and page reading for LLMs, AI agents, and RAG.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.divyanshu-iitian/searchforge- Version
- 0.2.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-07-24
- Updated
- 2026-07-24
- Publisher
- divyanshu-iitian (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/divyanshu-iitian) · how
- Website
- divyanshu-iitian.github.io/SearchForge/
- Repository
- github.com/divyanshu-iitian/SearchForge
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/divyanshu-iitian/searchforge-mcp:0.2.0 | - | stdio |
How to connect SearchForge
SearchForge runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/divyanshu-iitian/searchforge-mcp:0.2.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e SEARCHFORGE_SEARXNG_URL -e GITHUB_TOKEN -e CROSSREF_MAILTO -e BRAVE_SEARCH_API_KEY ghcr.io/divyanshu-iitian/searchforge-mcp:0.2.0. It reads these environment variables: SEARCHFORGE_SEARXNG_URL, GITHUB_TOKEN (secret), CROSSREF_MAILTO and BRAVE_SEARCH_API_KEY (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"searchforge": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SEARCHFORGE_SEARXNG_URL",
"-e",
"GITHUB_TOKEN",
"-e",
"CROSSREF_MAILTO",
"-e",
"BRAVE_SEARCH_API_KEY",
"ghcr.io/divyanshu-iitian/searchforge-mcp:0.2.0"
],
"env": {
"SEARCHFORGE_SEARXNG_URL": "<value>",
"GITHUB_TOKEN": "<secret>",
"CROSSREF_MAILTO": "<value>",
"BRAVE_SEARCH_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| SealGateAdd passkeys to an existing login (made in Japan). Manage projects, API keys, passkeys, audit logs. | Remote · HTTPLive check: sign-in required |
| sealgate.aiMCP gateway with runtime security policy, tool-call-level control, and audit of agent actions. | Remote · HTTPLive check: sign-in required |
| SEARBenchmark-first release surface with a read-only MCP endpoint and operator CLI. | Remote · HTTPLive check: ✓ handshake |
| Search Console MCPGoogle Search Console for any MCP client - 30-second login, no Google Cloud project. Read-only. | Local · stdio |
| Sec 13fSEC 13F - institutional ownership, asked security-first. | Remote · HTTPLive check: ✓ handshake |
| secdim.comPersonalised developer security learning pathways from SecDim's challenges and courses. | Remote · HTTPLive check: ✓ handshake |
| Secenv MCPCentralized secrets manager MCP server. Generate.env files, rotate keys, sync to GitHub Actions. | Local · stdio |
| SecHelixEvidence-first security review of authorized repositories. Read-only, root-confined, no shell. | Local · stdio |