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/walichat/mcp-walichatWrote 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/walichat/mcp-walichat/mcp-walichat)<a href="https://agentmods.dev/mcp/walichat/mcp-walichat/mcp-walichat"><img src="https://agentmods.dev/badge/mcp/walichat/mcp-walichat/mcp-walichat/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/walichat/mcp-walichat/mcp-walichat"><img src="https://agentmods.dev/badge/mcp/walichat/mcp-walichat/mcp-walichat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-walichat 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 10d 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
{ "mcp-walichat": { "command": "npx", "args": [ "-y", "mcp-walichat" ] } }
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.
- 10d ago First seen · 9 lines scan A 83ad5914b365
mcp-walichat is an MCP server published in the GitHub repository walichat/mcp-walichat (1 stars, last pushed 1y 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-31.
Other mcp servers, from other repositories
mcp-odoo
Odoo MCP for AI agents — 41 tools, gated writes, multi-instance. Free hosted product: ERPipe (mcp.erpipe.com). Runs locally from the odoo-mcp Python package. Needs 4 environment variables to run.
RivalSearchMCP
MCP server "RivalSearchMCP", hosted remotely at rivalsearchmcp.fastmcp.app, as configured in damionrashford/RivalSearchMCP.
one-search-mcp
Web search, URL discovery, scraping & extraction with agent-browser and search providers. Runs locally from the one-search-mcp npm package. Needs 5 environment variables to run.
mcp-telegram
MCP server for Telegram userbot — messages, media, reactions, polls & more. Built on GramJS/MTProto. Runs locally from the @overpod/mcp-telegram npm package. Needs 2 environment variables to run.
mcp-memory-server
Hosted memory for AI agents that learns from outcomes — one key across Claude, Cursor & ChatGPT. Runs locally from the @mnemoverse/mcp-memory-server npm package. Needs 2 environment variables to run.
obsidian-everywhere
Graph context, semantic search, guarded edits, and reviewable Git for local Obsidian vaults. Runs locally from the obsidian-everywhere npm package.