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/Nishant-Chaudhary5338/mcp-toolkitWrote 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/nishant-chaudhary5338/mcp-toolkit/mcp-react-toolkit)<a href="https://agentmods.dev/mcp/nishant-chaudhary5338/mcp-toolkit/mcp-react-toolkit"><img src="https://agentmods.dev/badge/mcp/nishant-chaudhary5338/mcp-toolkit/mcp-react-toolkit/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/nishant-chaudhary5338/mcp-toolkit/mcp-react-toolkit"><img src="https://agentmods.dev/badge/mcp/nishant-chaudhary5338/mcp-toolkit/mcp-react-toolkit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-react-toolkit 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.
What it actually says
{
"mcp-react-toolkit": {
"command": "npx",
"args": [
"-y",
"mcp-react-toolkit"
],
"env": {}
}
}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.
- 1mo ago First seen · 10 lines scan A 770b027d03d6
mcp-react-toolkit is an MCP server published in the GitHub repository Nishant-Chaudhary5338/mcp-toolkit (3 stars, last pushed 26d 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
oorep-mcp
MCP server and TypeScript SDK for OOREP homeopathic repertory and materia medica reference data. Runs locally from the oorep-mcp npm package.
mcp-harness-fme
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package.
jsc-typescript-ast-mcp
AST for TypeScript, supports creating JSON representations of React components. Runs locally from the jsc-typescript-ast-mcp npm package. Needs 1 environment variable to run.
codely-mcp-server
TypeScript execution environment and REPL for node.js, with source map support. Runs locally from the ts-node npm package. Needs 1 environment variable to run.
vdiff-mcp
Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes. Runs locally from the vdiff-mcp npm package. Needs 1 environment variable to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.