Money Magician
REMOTE · MCP.MONEYMAGICIAN.EU
Money Magician: AI accounting. Connect agents to your invoices, expenses, bank data, taxes & profit.
Available components
Last scanned (19 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1813 tokens (~139/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Nov 26 +38
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 14 Nov 26 39
First indexed and scored.
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 21 Nov 2026 · Probed https://mcp.moneymagician.eu
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=moneymagician.eu | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9c7af05b11f6569b0e374e40c909d358 |
| SANs: moneymagician.eu, mcp.moneymagician.eu, *.mcp.moneymagician.eu | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.moneymagician.eu. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | DS published | 35926 | 8 | Verified |
| moneymagician.eu. | DS published | 2371 | 13 | Verified |
| mcp.moneymagician.eu. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Money Magician MCP", resource_metadata="https://mcp.moneymagician.eu/.well-known/oauth-protected-resource"
Bearer realm="Money Magician MCP", resource_metadata="https://mcp.moneymagician.eu/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Protected resource metadata
| Document | https://mcp.moneymagician.eu/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.moneymagician.eu |
| Authorisation server | https://mcp.moneymagician.eu |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.moneymagician.eu | Verified | 200 | |
| http (plaintext) | http://mcp.moneymagician.eu | HTTPS enforced | 301 | https://mcp.moneymagician.eu/ |
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 →
calculate_taxes ~98
Calculate tax information for invoices within a date range, providing breakdown by tax rate. Both date_from and date_to are required. Requires the Start or Business plan.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | yes | Start date (YYYY-MM-DD) |
| date_to | string | yes | End date (YYYY-MM-DD) |
| tax_regime | string | – | Tax regime to apply (default: 'simple'). Falls back to the user's default tax regime when omitted. |
No output schema declared.
No examples provided.
get_expenses_by_category ~87
Get total expenses grouped by category/tag for creating pie charts and expense analysis. Returns pre-aggregated data with both gross and net totals per category, invoice counts, and colors. Much faster than fetching individual invoices when you need category summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start date (YYYY-MM-DD) |
| date_to | string | – | End date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
get_financial_summary ~67
Get a comprehensive financial summary including total invoices, amounts by currency (both gross and net), and top vendors with both gross and net spending totals
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start date (YYYY-MM-DD) |
| date_to | string | – | End date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
get_invoice_details ~145
Get detailed information about a specific invoice including all extracted data, payments, and tags. Returns top-level "currency", "comparable" (true if matches primary currency), "converted_to_primary", and "currency_warning" fields. Has TWO status fields: "processing_status" (OCR workflow stage) and "payment_status" (paid/unpaid). Amounts include both total_gross and total_net values in the amounts object. converted_to_primary is null when no conversion data exists, or { amount, currency, source } when a bank reconciliation has recorded the actual settlement amount. Requires the Start or Business plan.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | The UUID of the invoice |
No output schema declared.
No examples provided.
get_profitability_metrics ~207
Get profitability analysis including Gross Profit (Net Revenue - COGS), Gross Margin, Net Result (Total Income - Total Expenses), expense breakdown by COGS vs OpEx, and quarterly COGS/OpEx breakdown. Includes bank and Wise transactions with COGS categories. Note: Gross Profit (Net Revenue - COGS) is distinct from Net Result (Total Income - Total Expenses). COGS = Cost of Goods Sold (Inventory, Production Labor, Direct Contractors, Shipping). OpEx = Operating Expenses (everything else). For calendar-year periods, date_from is YYYY-01-01 and date_to is YYYY-12-31. Returns quarterly_breakdown array with COGS/OpEx per quarter.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start date (YYYY-MM-DD). For calendar year queries use YYYY-01-01 |
| date_to | string | – | End date (YYYY-MM-DD). For calendar year queries use YYYY-12-31 |
No output schema declared.
No examples provided.
get_reconciliation_status ~94
Get reconciliation/matching status for invoices and transactions. Shows how many expense invoices, sales invoices, bank transactions, and Wise transactions are matched, unmatched, partial, or ignored. Useful for year-end cleanup and understanding what remains to be reconciled. Requires the Start or Business plan.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start date (YYYY-MM-DD) |
| date_to | string | – | End date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
get_tax_position ~100
Get comprehensive tax position metrics including cash-basis tax (collected vs paid), VAT timing impact (float advantage vs cash tied up), and true tax position. Matches the Tax Position section on Dashboard. Useful for VAT/GST reporting, cash flow optimization, and understanding tax obligations. Requires the Start or Business plan.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start date (YYYY-MM-DD) |
| date_to | string | – | End date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
get_top_customers ~87
Get top customers by sales revenue with both gross and net amounts. Shows which customers generated the most revenue in a period. Requires the Start or Business plan.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start date (YYYY-MM-DD) |
| date_to | string | – | End date (YYYY-MM-DD) |
| limit | number | – | Number of top customers to return (default: 10) |
No output schema declared.
No examples provided.
get_top_vendors ~209
Get top vendors by expense spending. Returns a UNIFIED vendor list where every entry has an explicit "currency" field, a "comparable" flag (true = primary currency, false = foreign), and "converted_to_primary" field. converted_to_primary is null when no conversion data exists, or { amount, currency, invoices_converted, invoices_total, source } when bank reconciliation has recorded actual settlement amounts. Includes a top-level "currency_warning". Amounts in different currencies are NOT comparable or summable. For calendar-year periods, date_from is YYYY-01-01 and date_to is YYYY-12-31. Requires the Start or Business plan.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start date (YYYY-MM-DD). For year queries use YYYY-01-01 |
| date_to | string | – | End date (YYYY-MM-DD). For year queries use YYYY-12-31 |
| limit | number | – | Number of top vendors to return (default: 10) |
No output schema declared.
No examples provided.
get_vendor_summary ~178
Get a detailed financial summary for a specific vendor. Returns authoritative net/gross/tax totals in the user's primary currency with "comparable: true", individual invoice list (each with explicit "currency", "comparable", and "converted_to_primary" fields), and foreign currency totals marked with "comparable: false". converted_to_primary is null when no conversion data exists, or { amount, currency, source } when bank reconciliation has recorded actual settlement amounts. Includes a top-level "currency_warning". Totals are authoritative and more reliable than manually summing query_invoices results. Requires the Start or Business plan.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start date (YYYY-MM-DD) |
| date_to | string | – | End date (YYYY-MM-DD) |
| vendor | string | yes | Vendor name to look up (case-insensitive partial match) |
No output schema declared.
No examples provided.
list_created_invoices ~92
List invoices that you have created and sent to customers, with optional filtering. Returns both gross (incl. tax) and net (excl. tax) amounts for each invoice. Requires the Start or Business plan.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Filter by customer UUID |
| limit | number | – | Maximum number of results (default: 10) |
| status | string | – | Filter by invoice status |
No output schema declared.
No examples provided.
query_invoices ~312
Search and filter invoices by various criteria. Returns a response with top-level "primary_currency" and "currency_warning" fields. Each invoice includes explicit "currency", "comparable" (true if matches primary currency), and "converted_to_primary" fields alongside separate numeric "amount_gross", "amount_net", and "tax_amount" values. Also has TWO status fields: "processing_status" (pending/processing/completed/paid) and "payment_status" (paid/unpaid). Amounts in different currencies are NOT directly comparable or summable. Also includes tags/categories for each invoice in the response. converted_to_primary is null when no conversion data exists, or { amount, currency, source } when a bank reconciliation has recorded the actual settlement amount in the user's primary currency. Requires the Start or Business plan.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start date (YYYY-MM-DD) |
| date_to | string | – | End date (YYYY-MM-DD) |
| limit | number | – | Maximum number of results (default: 10) |
| max_amount | number | – | Maximum invoice amount (gross) |
| min_amount | number | – | Minimum invoice amount (gross) |
| status | string | – | Filter by processing_status (OCR workflow stage). Note: completed means OCR is done but NOT necessarily paid; the payment_status field in results reflects the actual payment state. |
| tag | string | – | Filter by a single tag name (partial match) |
| vendor | string | – | Filter by vendor name (partial match) |
No output schema declared.
No examples provided.
search_customers ~61
Search for customers by name, company name, or email Requires the Start or Business plan.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results (default: 10) |
| search | string | – | Search term for customer name, company name, or email |
No output schema declared.
No examples provided.
How do I install the Money Magician MCP server?
Money Magician is a hosted endpoint at https://mcp.moneymagician.eu/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.moneymagician.eu
claude mcp add --transport http eu-moneymagician-mcp 'https://mcp.moneymagician.eu/'
What is the Money Magician MCP server?
Money Magician is an MCP server listed in the public MCP registry as eu.moneymagician/mcp. Money Magician: AI accounting. Connect agents to your invoices, expenses, bank data, taxes & profit. This page covers its hosted endpoint (https://mcp.moneymagician.eu).
Is the Money Magician MCP server safe to use?
Money Magician scores 77 out of 100 on VerifyMCP. 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 Money Magician MCP server expose?
Money Magician exposes 13 tools: query_invoices, get_invoice_details, search_customers, get_financial_summary, calculate_taxes, and 8 more. Their descriptions and schemas cost roughly 1,737 tokens of context every time the server is loaded.
Does the Money Magician MCP server require authentication?
Yes. Money Magician asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Money Magician MCP server still maintained?
Money Magician is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Money Magician MCP server?
VerifyMCP ran 13 checks on Money Magician, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.