Copilot Money (ignaciohermosillacornejo) MCP Server

copilot-money-mcp npm v2.3.0 Source verified

Published by ignaciohermosillacornejo — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for Copilot Money — query personal finances locally (14 cache-mode read tools), opt into GraphQL-backed live reads with --live-reads (21 read tools: 8 cache + 13 live), and manage data via Copilot's GraphQL API (17 write tools, opt-in with --wr

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 98 − adoption risk = 92/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 1.8 = 98. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.8 Hardcoded Google API key in server code ×2 MTC-SRC-008 exfiltration

2. Client adoption risk — 98 − 6 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 4

high Dynamic code execution in server code (dist/cli.js)MTC-SRC-001

In the server's implementation (`dist/cli.js:2892`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const makeValidate = new Function(`${names_1.default.self}`, `${names_1.default.scope}`, sourceCode); const val

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli.js

high Dynamic code execution in server code (dist/server.js)MTC-SRC-001

In the server's implementation (`dist/server.js:2891`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const makeValidate = new Function(`${names_1.default.self}`, `${names_1.default.scope}`, sourceCode); const val

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/server.js

low Hardcoded Google API key in server code (dist/cli.js)MTC-SRC-008

A hardcoded Google API key (a public Firebase/web API key) appears in `dist/cli.js:40964`. Verify whether this is a real credential; if so, remove and rotate it.

Evidence: Google API key: AIza…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server dist/cli.js

low Hardcoded Google API key in server code (dist/server.js)MTC-SRC-008

A hardcoded Google API key (a public Firebase/web API key) appears in `dist/server.js:40963`. Verify whether this is a real credential; if so, remove and rotate it.

Evidence: Google API key: AIza…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server dist/server.js

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.3.0 latest A 92/100 4 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/copilot-money-mcp/badge.svg)](https://mcptrustchecker.com/registry/copilot-money-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/copilot-money-mcp"><img src="https://mcptrustchecker.com/registry/copilot-money-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/copilot-money-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan copilot-money-mcp --online

Use the free API → How scoring works

Other implementations of Copilot Money 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Finance & Commerce