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/AndrewAvery7/promptspendWrote 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/andrewavery7/promptspend/promptspend)<a href="https://agentmods.dev/mcp/andrewavery7/promptspend/promptspend"><img src="https://agentmods.dev/badge/mcp/andrewavery7/promptspend/promptspend.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
promptspend 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
{
"promptspend": {
"command": "npx",
"args": [
"-y",
"@promptspend/mcp"
],
"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.
- 7d ago First seen · 10 lines scan A 95b55ef5dfdc
promptspend is an MCP server published in the GitHub repository AndrewAvery7/promptspend (0 stars, last pushed today), 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
statlyte
Live LLM pricing, context windows and model ids, read from each vendor's own page every 3 hours. Runs locally from the statlyte npm package.
llmkit
AI cost tracking: 11 tools for spend, budgets, and Claude Code + Cursor + Cline costs. Runs locally from the @f3d1/llmkit-mcp-server npm package. Needs 2 environment variables to run.
mcp-firefly-iii
Security-first, self-hosted MCP server for Firefly III — 152 operations behind 5 scoped tools. Runs locally from the @yakupemreyerli/firefly-mcp npm package. Needs 2 environment variables to run.
bench
Discover public AI agents, reusable recipes, and trusted benchmark evidence by task. Remote server at bench.virajmishratakehome.workers.dev.
llm-cost-guard
Track LLM costs, set budget limits, get alerts. One command to install, one line to use. Runs locally from the @wimoron/llm-cost-guard npm package.
mcp-server
WasmAgent MCP server — WASM-sandboxed code execution with capability manifests and Tasks API. Runs locally from the @wasmagent/mcp-server npm package.