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/cachet-jp/ln-agent-poc-v2Wrote 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/cachet-jp/ln-agent-poc-v2/purchasing-agent)<a href="https://agentmods.dev/mcp/cachet-jp/ln-agent-poc-v2/purchasing-agent"><img src="https://agentmods.dev/badge/mcp/cachet-jp/ln-agent-poc-v2/purchasing-agent.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
purchasing-agent 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 7d 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
{
"purchasing-agent": {
"command": "bash",
"args": [
"-ilc",
"cd purchasing-agent && exec pnpm dev"
],
"env": {
"NODE_ENV": "development"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 7d ago First seen · 12 lines scan A 78eb84e67b6d
purchasing-agent is an MCP server published in the GitHub repository cachet-jp/ln-agent-poc-v2 (4 stars, last pushed 3d 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
402-mcp
AI agents discover, pay for, and consume any Lightning-gated API autonomously. Runs locally from the 402-mcp npm package. Needs 2 environment variables to run.
catalogapi
Check reward coverage by country, search real catalog items, and ask how CatalogAPI works. Remote server at api.catalogapi.com.
mcp
Agent-to-agent Lightning commerce & messaging: buy, sell, discover, send encrypted files. Runs locally from the @hypawave/mcp npm package. Needs 3 environment variables to run.
roastify-mcp
Roastify Developer API MCP Service — Tollbooth DPYC monetization. Remote server at roastify-mcp.fastmcp.app.
mcp-shopify-admin
MCP server for the Shopify Admin API: products, orders, customers, inventory, discounts. Runs locally from the mcp-shopify-admin npm package. Needs 9 environment variables to run.
gunbroker
GunBroker MCP Pack — wraps the GunBroker firearms-marketplace API. Remote server at gateway.pipeworx.io.