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/BackTrackCo/tenjin-agentWrote 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/backtrackco/tenjin-agent/tenjin-router)<a href="https://agentmods.dev/mcp/backtrackco/tenjin-agent/tenjin-router"><img src="https://agentmods.dev/badge/mcp/backtrackco/tenjin-agent/tenjin-router/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/backtrackco/tenjin-agent/tenjin-router"><img src="https://agentmods.dev/badge/mcp/backtrackco/tenjin-agent/tenjin-router.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
router 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 today.
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- today First seen · 9 lines scan A a7e854b6ae91
router is an MCP server published in the GitHub repository BackTrackCo/tenjin-agent (16 stars, last pushed today), with no licence file. 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-10-16.
Other mcp servers, from other repositories
xenarch-mcp
Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2. Runs locally from the @xenarch/agent-mcp npm package. Needs 4 environment variables to run.
t2000
MCP server "t2000", hosted remotely at mcp.t2000.ai, as configured in mission69b/t2000.
nano-pay
Feeless x402 micropayments for AI agents — self-custodied XNO wallet, pay-per-call client, merchant server with railHint, faucet, and MCP server. Runs locally from the feeless402 Python package.
fiatdock
A marketplace where AI agents discover MCP services and buy them from other agents per call in USDC via x402, auto-paid from your wallet — plus a non-custodial USDC-to-bank cash-out (licensed provider), first-party Base chain data and token safety. Runs locally from the fiatdock-mcp npm package. Needs 3 environment…
intelligence-mcp
Agent payments ecosystem intelligence. Scans GitHub/HN/npm across AP2, ACP, x402, MPP, UCP. Runs locally from the @goodmeta/intelligence-mcp npm package. Needs 2 environment variables to run.
x402-mcp-bridge
Put a wallet in front of any x402-paid MCP server: pay per call, or buy time and ride a ZEAM :: Pass line. Stock MCP clients cannot construct x402 payments; this one does, and proxies your existing client through it. Runs locally from the @zeam-labs/x402-mcp-bridge npm package.