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/ising-tech/isingq-toolkitInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
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.
[](https://agentmods.dev/mcp/ising-tech/isingq-toolkit/isingq)<a href="https://agentmods.dev/mcp/ising-tech/isingq-toolkit/isingq"><img src="https://agentmods.dev/badge/mcp/ising-tech/isingq-toolkit/isingq/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/ising-tech/isingq-toolkit/isingq"><img src="https://agentmods.dev/badge/mcp/ising-tech/isingq-toolkit/isingq.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
isingq 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 2mo 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
{
"isingq": {
"command": "node",
"args": [
"./bin/isingq-mcp.js",
"serve"
],
"cwd": "."
}
}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.
- 2mo ago First seen · 10 lines scan A 8371dcf82765
isingq is an MCP server published in the GitHub repository ising-tech/isingq-toolkit (1 stars, last pushed 11d 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.
Other mcp servers, from other repositories
codex-control-plane-mcp
Durable MCP control plane for long-running Codex Desktop tasks. Runs locally from the codex-control-plane-mcp Python package.
ragmap
DEPRECATED: hosted backend discontinued; npm package deprecated. Formerly a retriever-MCP finder. Runs locally from the @khalidsaidi/ragmap-mcp npm package.
mcp-gateway-service
A token-efficient MCP gateway that provides one unified entry point for multiple downstream MCP services. Runs locally from the @jadchene/mcp-gateway-service npm package.
robinx-mcp
Robinhood Chain MCP server: rug checks, deployer records, measured X callers. For agents and bots. Runs locally from the robinx-mcp npm package. Needs 1 environment variable to run.
404-directory
MCP server "404-directory", hosted remotely at 404.directory, as configured in MM-sheng/404-directory.
xcatcher
Fetch recent public X/Twitter posts by named handle for monitoring, comparison, OSINT, and research. Remote server at xcatcher.top.