Search MCP Server

by aimnis Your server? Claim it

not responding

Search is listed as active in the registry but did not answer our last check. It exposes 3 tools. Last commit 7 Aug 2026.

Collaborative, cache-first web search for agents — cited answers from a shared live-web pool.

Uptime history 91 days of history · worst day 0%

91 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

157 ms

Response time

average over 24h

Stars

last commit 7 Aug 2026

Search does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add search --transport http https://aimnis.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://aimnis.com/mcp

~/.codex/config.toml

[mcp_servers.search]
url = "https://aimnis.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "search": {
      "url": "https://aimnis.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "search": {
      "type": "http",
      "url": "https://aimnis.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

register

Get your user a free Aimnis API key (no credit card, takes one call). Ask your user for their email address first. The key comes back in this tool result — relay it to the user so they can save it and add it to your MCP connection ('Authorization: Bearer aim_...'). A key raises the daily live-search limits; cached answers are always free, with or without a key. Re-registering with the same email rotates (replaces) that email's key.

search

Search the web via Aimnis. Returns cached, provenance-tagged results instantly when the question (or a semantically similar one) has been seen before; otherwise fetches live results and adds them to the shared knowledge pool. Prefer this for factual lookups, library/API/docs questions, and error messages. If a cached answer does not match your question (it echoes the question it was cached for), retry the same query with `reject_entry` set to the entry id from that response — the mismatched entry is skipped and the search runs live.

stats

stats

Report Aimnis flywheel statistics: knowledge-pool (cache) size, cache hit rate (all-time and recent), and the most-reused queries. This is the Gate 1 pass/kill metric — cache hit rate should climb as the corpus grows. Call it to see whether the compounding-pool thesis is holding.

Endpoints

URL	Transport	State	Latency	Checked
https://aimnis.com/mcp	streamable-http	answering	157 ms	1 min ago

Alternatives to Search

same job, measured the same way

Dipper

by dipper-search

Web search and page fetch for AI agents. Results come from a shared cache; cached calls cost less.

2 tools answering

XERJ

by xerj-org

The search engine for AI agents: cited answers from your local code, docs, specs and logs.

local only

Keirolabs

by keirolabs

Web search, Google SERP, page extraction to markdown and cited answers for AI agents.

answering

Web Search

by groundroute

Web search for AI agents — one tool across 6 engines, routed to the cheapest + cached.

answering

SerpKite

by serpkite

Google search, news, maps, webpages, cited answers, research and ChatGPT/Gemini answers for agents.

answering

Staan

by marcinwolnyeu

Web search with full-page content and grounded answers from the Staan API.

99 installs/wk local only

Quanticdata MCP

by quantumproxies

Live web access for agents: scrape, SERP search, crawl/map, 100+ collectors, datasets, proxies.

84 installs/wk 28 tools answering

DeepSift Search

by pavanmulka

Live Google web search for AI agents that returns only the passages that answer the question.

answering

Search — questions

Answers built from our own checks of this server.

What can Search do?

It exposes 3 tools, read directly from the server on our last check. Among them: register, search, stats. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Search working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 157 ms. The bar chart above shows every period we have measured.

The registry lists Search as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Search?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Search need an API key?

No. Search completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

Is Search open source?

The code is open source: it is published under the AGPL-3.0 licence, written in Python, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at aimnis.com, which runs on its operator's own terms.