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/koshak01/tidex6Installing this writes the configuration, not the program: `tidex6-mcp-local` has to be on your PATH already, or the server will not start.
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/koshak01/tidex6/tidex6-mcp-local)<a href="https://agentmods.dev/mcp/koshak01/tidex6/tidex6-mcp-local"><img src="https://agentmods.dev/badge/mcp/koshak01/tidex6/tidex6-mcp-local/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/koshak01/tidex6/tidex6-mcp-local"><img src="https://agentmods.dev/badge/mcp/koshak01/tidex6/tidex6-mcp-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tidex6-mcp-local 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
{ "tidex6-mcp-local": { "command": "tidex6-mcp-local", "args": [], "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.
- 2mo ago First seen · 7 lines scan A 8187c8ebcd0c
tidex6-mcp-local is an MCP server published in the GitHub repository koshak01/tidex6 (1 stars, last pushed 6d 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
snap-private-payments
Private agent payments on Solana via ZK proofs: deposit, withdraw, list pools, estimate fees. Runs locally from the snap-mcp-server npm package. Needs 3 environment variables to run.
null-402-mcp
MCP server "null-402-mcp" as configured in shinothelegend/null-402-mcp. Runs locally from the null-402-mcp npm package.
fry-x402-mcp
MCP server "fry-x402-mcp" as configured in Fry-Networks/fry-x402-mcp. Runs locally from the fry-x402-mcp npm package.
pdao-agent-exchange
Solana Mainnet verification, intelligence, machine receipts, and agent logistics through MCP. Remote server at agents.privatedao.org.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
repomix
A tool to pack repository contents to single file for AI consumption. Runs locally from the repomix npm package.