ai-usage-mcp (MohitBansal321/ai-usage-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 8 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

ai-usage-mcp

A local-first MCP server that answers, from real data on your machine: How many tokens have I used, from which client, model and session — and what did it cost?

→ MohitBansal321/ai-usage-mcp· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

MohitBansal321

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAI_USAGE_CLAUDE_PROJECTSPath to Claude Code's projects/ directory
configAI_USAGE_DBWhere to keep our database
configAI_USAGE_FRESHNESS_MSHow long a sync stays fresh before a tool call re-syncs (default 30000)
configAI_USAGE_HOMERelocates both the database and the config dir in one go
configAI_USAGE_OPENCODE_DBPath to opencode.db
configAI_USAGE_PRICING_FILEPricing override file
configAI_USAGE_SQLITE_DRIVERForce node:sqlite or better-sqlite3; unset picks the best available
configCLAUDE_CONFIG_DIR
configXDG_CONFIG_HOME
configXDG_DATA_HOMENote: the database path deliberately ignores . A sandboxed launcher (the
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

8/8 tools missing one or more hints — client_usage (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); counterfactual_cost (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); daily_usage (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/mohitbansal321/ai-usage-mcp)](https://m8ven.ai/mcp/mohitbansal321/ai-usage-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6d229227b68ac18c02d30b27212aa87947e2f53c
code hash: 101f51511ee4b258c727b0c34a489b861e9238188d9a581d0681c741712edc50
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client