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.
git clone --depth 1 https://github.com/yokingma/one-search-mcpWrote 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.
[](https://agentmods.dev/mcp/yokingma/one-search-mcp/one-search-mcp)<a href="https://agentmods.dev/mcp/yokingma/one-search-mcp/one-search-mcp"><img src="https://agentmods.dev/badge/mcp/yokingma/one-search-mcp/one-search-mcp/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.
<a href="https://agentmods.dev/mcp/yokingma/one-search-mcp/one-search-mcp"><img src="https://agentmods.dev/badge/mcp/yokingma/one-search-mcp/one-search-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
one-search-mcp 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 11d 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.
What it actually says
{
"one-search-mcp": {
"command": "npx",
"args": [
"-y",
"one-search-mcp"
],
"env": {
"SEARCH_PROVIDER": "",
"SEARCH_API_URL": "",
"SEARCH_API_KEY": "",
"YDC_API_KEY": "",
"ALLOW_PRIVATE_NETWORK": ""
}
}
}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.
- 11d ago First seen · 16 lines scan A befd4aae8f36
one-search-mcp is an MCP server published in the GitHub repository yokingma/one-search-mcp (140 stars, last pushed 1mo ago), licensed MIT. 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-30.
Other mcp servers, from other repositories
dompruner-mcp
Strips layout noise via DOM AST; with a query, BM25 filters to relevant sections. No model or API. Runs locally from the dompruner-mcp npm package.
stdio-full
MCP server "stdio-full" as configured in apify/apify-mcp-server. Runs dist/stdio.js with node. Needs 2 environment variables to run.
apify-mcp-server
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡. Remote server at mcp.apify.com.
charlotte
Renders web pages into structured, agent-readable representations using headless Chromium. Runs locally from the @ticktockbent/charlotte npm package.
RivalSearchMCP
MCP server "RivalSearchMCP", hosted remotely at rivalsearchmcp.fastmcp.app, as configured in damionrashford/RivalSearchMCP.
vessel-browser
AI-native browser runtime for autonomous agents with human-in-the-loop supervision. Runs locally from the @quanta-intellect/vessel-browser npm package.