Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers and agent operators who already have MCP servers in circulation and need real cost visibility before tool sprawl quietly turns into an unbudgeted spend problem.
Who should use it
Who should skip it
Skip andreisirbu91-lab/MCPSpend if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
andreisirbu91-lab/MCPSpend is tracked by RepoRadar as a mcp tool in the MCP / Tooling section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, andreisirbu91-lab/MCPSpend is strongest on workflow potential (9.8) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned andreisirbu91-lab/MCPSpend a composite score of 8.3 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The init flow rewrites MCP client configs and inserts a proxy layer, so first rollout should stay limited to a disposable config with the generated backup checked before wider use; Usage metadata streams to the hosted MCPSpend dashboard, so teams handling sensitive project names or tool paths should review the privacy surface before enabling it.