Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.GillMacedo/chargescout

NPM · CHARGESCOUT

Find subscriptions, price increases and double charges in a bank statement CSV, on your machine.

Available components

74 Trust /100

Last scanned (7 hours ago)

Scores higher than 48% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 257 tokens (~128/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +16
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.1.0 → 0.2.0 functional
  • 31 Oct 26 56

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/chargescout@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~257 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
subscriptions_find ~187

Finds subscriptions and other recurring charges in a bank or card statement CSV, with billing cycle, yearly cost, price increases and possible double charges. Use to audit spending or find what to cancel. Read-only, and never uses the network. Results include merchant names and amounts from the file, so they reach the model. It can't cancel anything.

NameTypeReqDescription
columnsobject–Column names by field (date, amount, credit, debit, description), when detection fails
date_formatstring–dmy or mdy, needed only if the tool reports that dates are ambiguous
limitnull|integer–Most findings to return, default 100. 0 returns only the totals
pathstringyesPath to the bank or card statement CSV
positive_outboolean–Set if the file shows charges as positive numbers, as many card statements do
NameTypeReqDescription
active_countintegeryes–
active_yearly_totalstringyes–
finding_countintegeryes–
findingsnull|arrayyes–
skipped_rowsnull|arrayyes–
statement_endstringyes–
truncatedbooleanyes–
warningsnull|arrayyes–

No examples provided.

subscriptions_inspect_csv ~70

Shows which columns chargescout detects in a statement CSV and how many rows it can read, without returning row contents. Use if the file is unfamiliar or nothing was found.

NameTypeReqDescription
date_formatstring–dmy or mdy
pathstringyesPath to the statement CSV
NameTypeReqDescription
columnsobjectyes–
date_formatstringyes–
skipped_rowsintegeryes–
transactionsintegeryes–
warningsnull|arrayyes–

No examples provided.

Install

How do I install the io.github.GillMacedo/chargescout MCP server?

io.github.GillMacedo/chargescout runs locally as an npm package, launched with npx -y chargescout. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · chargescout

# add to Claude Code
claude mcp add gillmacedo-chargescout -- npx -y chargescout
Common questions

What is the io.github.GillMacedo/chargescout MCP server?

io.github.GillMacedo/chargescout is an MCP server listed in the public MCP registry as io.github.GillMacedo/chargescout. Find subscriptions, price increases and double charges in a bank statement CSV, on your machine. This page covers its npm package (chargescout).

Is the io.github.GillMacedo/chargescout MCP server safe to use?

io.github.GillMacedo/chargescout scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.GillMacedo/chargescout MCP server expose?

io.github.GillMacedo/chargescout exposes 2 tools: subscriptions_find, subscriptions_inspect_csv. Their descriptions and schemas cost roughly 257 tokens of context every time the server is loaded.

Is the io.github.GillMacedo/chargescout MCP server still maintained?

io.github.GillMacedo/chargescout is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.GillMacedo/chargescout MCP server under?

io.github.GillMacedo/chargescout declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.