MCPSpend
Tracks actual MCP infrastructure costs by tool and project, preventing runaway spend on agent-driven workloads and enabling accurate chargeback to teams or c…
Real-time cost observability for Model Context Protocol (MCP) tool calls. Wraps any MCP server, attributes spend per tool/project/customer. Free tier 25K calls/mo. EU-hosted
- Track API costs by team member and project to identify spending patterns.
- Monitor real-time expenses from MCP tool calls across your development environment.
- Attribute costs to specific customers or internal projects for accurate billing.
Tracks actual MCP infrastructure costs by tool and project, preventing runaway spend on agent-driven workloads and enabling accurate chargeback to teams or customers.
DevOps and platform teams managing multi-tenant MCP deployments with cost allocation requirements.
https://github.com/andreisirbu91-lab/MCPSpend
By andreisirbu91-lab
How to Get It
claude mcp add MCPSpend -- npx -y MCPSpend
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
Once it’s connected, paste this into Claude:
Help me track API costs by team member and project to identify spending patterns
Trust Signals Auto-scanned
Data & Access
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 86 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 86 GitHub stars; contributors unknown; last commit 0d ago; license MIT.