iFlow Search MCP server
io.github.zhengyanglsun/iflow-search·v0.1.0·32 starsMCP server for iFlow Search web search, image search, and URL fetch tools.
32 stars33 downloads/wk
Reviews
Write oneNobody has reviewed iFlow Search yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
iFlow Search tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan23 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 113 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How iFlow Search compares
Against every graded Web search MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 72/100
- higher than 40% of 3,470 Web search servers
- GitHub stars
- 32
- more than 91% of 1,786 Web search servers
- Downloads a week
- 33
- more than 19% of 827 Web search servers with a package
Install iFlow Search in Claude Code, Cursor or VS Code
Runs npx -y @iflow-ai/search-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add iflow-search -- npx -y @iflow-ai/search-mcp
What the publisher says
From the iFlow Search repository's README, as published. We do not edit it. Read it on GitHub
iflow-search-js
JavaScript / TypeScript integrations for iFlow Search (心流搜索) — a search API that provides web search, image search, and web page fetching with AI-friendly structured output.
- Product:
- API docs:
- Operator: 杭州星辰千寻科技有限公司
This monorepo contains:
- A framework-agnostic core SDK
- A LangChain JS tool adapter (also usable from LangGraph)
- A LangGraph agent example
- An MCP stdio server for Hermes / Claude Code / Claude Desktop / other MCP clients
Package / usage matrix
Why there is no @iflow-ai/search-langgraph
LangGraph consumes LangChain tools directly. A separate search-langgraph package would be a thin re-export with no added value — use @iflow-ai/search-langchain for both. See examples/langgraph-agent for a working createReactAgent wiring.
Current status
- ✅ @iflow-ai/search-core — implemented, framework-agnostic client
- ✅ @iflow-ai/search-langchain — implemented, three tools (iflowwebsearch, iflowimagesearch, iflowwebfetch)
- ✅ examples/langgraph-agent — implemented, ReAct agent end-to-end smoke validated against real iFlow API
- ❌ no separate @iflow-ai/search-langgraph package (intentional — see above)
- ✅ @iflow-ai/search-mcp — implemented, stdio MCP server with three tools mirroring the LangChain adapter; optional MCP-host attribution via IFLOWMCPCLIENT / IFLOWMCPCLIENT_VERSION
- ✅ plugins/iflow-search — Claude Code Plugin manifest (metadata-only, runs npx -y @iflow-ai/search-mcp); awaiting submission to the Anthropic Plugin Directory. See plugins/iflow-search/README.md.
Workspace development
pnpm install
pnpm -r run typecheck
pnpm -r run build
pnpm -r run testThe workspace pins @langchain/core to ^1.1.44 via pnpm-workspace.yaml overrides: to keep LangGraph's runtime and LangChain's tool types on a single major. Removing this override re-introduces ToolMessage cross-version serialization bugs in LangGraph agent loops; rerun the LangGraph agent tests before you touch it.
Basic usage — core SDK
import { createIFlowSearchClient } from "@iflow-ai/search-core";
const client = createIFlowSearchClient({
apiKey: process.env.IFLOW_API_KEY!,
source: "core",
integrationName: "my-app",
integrationVersion: "1.0.0",
});
const result = await client.webSearch({ query: "flash attention", count: 5 });
if (!result.ok) {
console.error(result.error.code, result.error.message);
} else {
for (const r of result.data.results) console.log(r.title, r.url);
}Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
iFlow Search: common questions
- Is iFlow Search MCP server safe?
- Mostly: it is graded B (72/100). Read the iFlow Search safety report
- How do I install iFlow Search?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does iFlow Search need an API key?
- Yes. The registry entry asks for
IFLOW_API_KEY. - Is iFlow Search maintained?
- The last commit was 151 days ago (2026-06-06). The latest release is v0.1.0.
- What can I use instead of iFlow Search?
- Servers from other publishers that do the same job: Brave Search MCP server, SearXNG Search MCP server and Brave MCP server. Compare all iFlow Search alternatives.
- How does iFlow Search compare with other Web search MCP servers?
- safety score 72/100 (higher than 40% of 3,470 Web search servers); github stars 32 (more than 91% of 1,786 Web search servers); downloads a week 33 (more than 19% of 827 Web search servers with a package). Full comparison.
Alternatives to iFlow Search
Same job from other publishers: the closest match first, then the best rated.
- Brave SearchBrave Search MCP Server: web results, images, videos, rich results, AI summaries, and more.not reviewedEstablishedA
- SearXNG SearchMCP server for SearXNG — privacy-respecting web search with pagination, URL readingnot reviewedEstablishedB
- BraveVisit https://brave.com/search/api/ for a free API key. Search the web, local businesses, images,…not reviewedEstablishedA
- CLIO WebProvider-fixed web search plus transparent URL, DOI, and document fetchingnot reviewedEstablishedA
Zotero MCPSearch, read, annotate, and add to your Zotero research library, local or web.not reviewedWidely usedB