infoseek-search

infoseek-search is an MCP server for Claude Code, Codex, Cursor, Gemini CLI, OpenCode from GYINT/ZeroQ. Its token cost is not measured, scanned A, original, Apache-2.0.

An MCP server configuration for infoseek-search, a search service from the ZeroQ project. It starts a Python server and specifies where its program, database, and archives are located.

In plain words
What is it for?
It is for setting up infoseek-search in an MCP client with its installation path, local database path, and archive directory.
Why use it?
It provides the file paths and launch command needed for the search service to run locally.

MCP server for Claude CodeCodexCursorGemini CLIOpenCode

Written for no agent in particular: it speaks MCP, so any client can run it. Also seen: listed in a Claude config.

One of 2 entries in .mcp.json upstream. Installing this one merges just its entry into your config; the other 1 are separate, each on its own page.

Good fit It is for setting up infoseek-search in an MCP client with its installation path, local database path, and archive directory.

Compare 6 mcp servers from other repositories ↓
Install with agentmods
npx agentmods add mcp/gyint/zeroq/infoseek-search

Installing this writes the configuration, not the program: `${INFOSEEK_ROOT}/scripts/infoseek_mcp_server.py` has to be on your PATH already, or the server will not start.

View source ↗ GYINT/ZeroQ
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/GYINT/ZeroQ

Installing this writes the configuration, not the program: `${INFOSEEK_ROOT}/scripts/infoseek_mcp_server.py` has to be on your PATH already, or the server will not start.

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for infoseek-search

README.md
[![agentmods](https://agentmods.dev/badge/mcp/gyint/zeroq/infoseek-search/github.svg)](https://agentmods.dev/mcp/gyint/zeroq/infoseek-search)
Your own site
<a href="https://agentmods.dev/mcp/gyint/zeroq/infoseek-search"><img src="https://agentmods.dev/badge/mcp/gyint/zeroq/infoseek-search/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for infoseek-search

Your own site · 80×15
<a href="https://agentmods.dev/mcp/gyint/zeroq/infoseek-search"><img src="https://agentmods.dev/badge/mcp/gyint/zeroq/infoseek-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

infoseek-search scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.mcp.json · 14 lines

What it actually says

{
  "infoseek-search": {
    "command": "${INFOSEEK_ROOT}/scripts/infoseek_mcp_server.py",
    "args": [
      "--transport",
      "stdio"
    ],
    "env": {
      "INFOSEEK_ROOT": "${INFOSEEK_ROOT}",
      "INFOSEEK_DB": "${HOME}/.infoseek/infoseek_db.json",
      "INFOSEEK_ARCHIVE": "${HOME}/infoseek-archives"
    }
  }
}
Same file

What else .mcp.json configures

This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 14 lines scan A 92ee330a4fcb

Subscribe to this mod's changes

infoseek-search is an MCP server published in the GitHub repository GYINT/ZeroQ (0 stars, last pushed 1mo ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.