io.github.mutonby/aikount-mcp
PYPI · AIKOUNT-MCP · 2 COMPONENTS
Contabilidad española con IA: facturas, gastos por OCR, conciliación bancaria e impuestos AEAT.
Available components
Last scanned (19 hours ago)
Scores higher than 92% of PyPI servers
Category Finance and Payments
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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mutonby/aikount-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 54 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2005 tokens (~87/item across 23 items; 23 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (4% 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 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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
- Security disclosure: unverified → fail ▼ functional
- 20 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Nov 26 +1
- Stability: 0.97 → pass security
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed pypi/aikount-mcp@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mutonby/aikount-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mutonby/aikount-mcp/.github/workflows/publish.yml@refs/tags/v0.1.2 |
| Rekor log index | 2978833704 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:7f596f3be8491a4800bf4eee73bdfe6c5c69940f68dcfacd887ed5fcb223d367 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
api_request ~149
Call any Aikount API endpoint not covered by a dedicated tool. The full surface is documented at https://api.aikount.com/openapi.json — fetch it (e.g. api_request('GET', '/../openapi.json')) when you need an endpoint this server doesn't wrap. Args: method: GET / POST / PATCH / DELETE. path: API path relative to the base, e.g. '/invoices' or '/contacts/<uuid>'. Leading slash optional. params: query parameters. body: JSON body (for POST/PATCH).
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| method | string | yes | – |
| params | – | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
create_contact ~81
Create a contact. `country` is an ISO-3166 alpha-2 code (e.g. 'ES').
| Name | Type | Req | Description |
|---|---|---|---|
| country | – | – | – |
| – | – | – | |
| is_customer | boolean | – | – |
| is_supplier | boolean | – | – |
| legal_name | – | – | – |
| name | string | yes | – |
| notes | – | – | – |
| vat | – | – | – |
No output schema declared.
No examples provided.
create_invoice ~255
Create a DRAFT sales invoice (call issue_invoice to assign a number). Money is in MAJOR units (euros as decimals), e.g. unit_price 1200.00 — NOT cents. Each line is a dict: { "description": "Consultoría mayo", # required "quantity": 1, # default 1 "unit_price": 1200.00, # default 0, euros "tax_type_id": "<uuid>", # from list_tax_types; omit # to inherit the contact/ # product default "discount_pct": 0, # optional, 0-100 "irpf_rate": 0 # optional override, 0-100 } Args: contact_id: customer UUID (see list_contacts / create_contact). doc_date: ISO 'YYYY-MM-DD'. series_id: optional numbering-series override (UUID).
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | – |
| currency | string | – | – |
| doc_date | string | yes | – |
| due_date | – | – | – |
| lines | array | yes | – |
| notes | – | – | – |
| series_id | – | – | – |
No output schema declared.
No examples provided.
get_ingest_job ~33
Poll the status/result of an AI ingest job (see ingest_purchase_pdf).
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
get_invoice ~25
Fetch one sales invoice in full by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | – |
No output schema declared.
No examples provided.
get_purchase ~25
Fetch one purchase document in full by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | – |
No output schema declared.
No examples provided.
ingest_purchase_pdf ~160
Queue a purchase PDF/image for AI extraction (OCR -> deduped purchase). The AI reads the supplier, lines and taxes and creates the purchase doc, deduplicating by invoice identity (contact + supplier_invoice_number, fallback total + date) so the same invoice never lands twice. Runs async: this returns a job immediately — poll get_ingest_job(job_id) until its status is done, then read result for the created document. Args: file_path: local path to a PDF / JPG / PNG / WebP / HEIC. force: bypass dedup and ingest anyway (use only when you are sure it is a genuinely distinct invoice).
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | – |
| force | boolean | – | – |
No output schema declared.
No examples provided.
issue_invoice ~58
Issue a draft invoice — assigns the next sequential legal number. Irreversible-ish: issued numbers must stay contiguous, so do not delete issued invoices to "renumber". Confirm with the user before issuing.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | – |
No output schema declared.
No examples provided.
ledger ~105
Read ledger movements for ONE PGC account. Args: account_id: the account's UUID (required). Resolve it from list_accounts — e.g. find the account whose code is '572' (bancos) and pass its id here. from_date / to_date: ISO date bounds.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
| from_date | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| to_date | – | – | – |
No output schema declared.
No examples provided.
list_accounts ~108
List the Spanish PGC chart of accounts (code, name, UUID, balance). Use this to resolve an account's UUID for `ledger`, or to browse by `group` (1-7, the leading PGC digit: 5 = financial accounts, 4 = receivables/payables, …) or free-text `search` (code or name).
| Name | Type | Req | Description |
|---|---|---|---|
| group | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| search | – | – | – |
No output schema declared.
No examples provided.
list_bank_movements ~116
List bank movements, optionally scoped to one treasury. Args: treasury_id: restrict to a single treasury (UUID). status: e.g. 'unreconciled' / 'reconciled'. from_date / to_date: ISO date bounds. search: free-text match on the movement description.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| search | – | – | – |
| status | – | – | – |
| to_date | – | – | – |
| treasury_id | – | – | – |
No output schema declared.
No examples provided.
list_contacts ~92
List contacts (customers and suppliers). Args: search: free-text match on name / legal name / VAT. kind: 'customer' or 'supplier' to filter; omit for both. limit: page size (1-500, default 50). offset: pagination offset.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| search | – | – | – |
No output schema declared.
No examples provided.
list_invoices ~104
List sales invoices. Lifecycle: draft -> issued -> paid. Args: status: e.g. 'draft', 'issued', 'paid'. contact_id: filter to one customer (UUID). from_date / to_date: ISO 'YYYY-MM-DD' bounds on doc_date.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | – | – | – |
| from_date | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| status | – | – | – |
| to_date | – | – | – |
No output schema declared.
No examples provided.
list_products ~32
List catalog products/services.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| search | – | – | – |
No output schema declared.
No examples provided.
list_purchases ~50
List purchase documents (supplier invoices / expenses).
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | – | – | – |
| from_date | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| to_date | – | – | – |
No output schema declared.
No examples provided.
list_tax_types ~82
List the tenant's tax types (IVA/IGIC/IPSI/IRPF), each with its UUID. Invoice/purchase lines reference a tax by `tax_type_id` (a UUID from this list), not by a string code — call this to resolve which UUID is the 21% IVA, the 10% reducido, exento, etc.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_treasuries ~67
List treasuries (bank / Stripe / PayPal accounts) with balances. Stripe/PayPal treasuries return a live balance pulled on read; bank-feed treasuries return the last synced snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
modelo_303_csv ~118
Modelo 303 backing detail for one quarter as CSV text. Returns the per-transaction breakdown (one row per invoice/purchase line: date, doc, contact, base, rate, iva, input/output) that the quarter's VAT figures are built from — useful for auditing the numbers. For the aggregated box totals, use modelo_303_summary. Args: year: e.g. 2026. quarter: 1-4.
| Name | Type | Req | Description |
|---|---|---|---|
| quarter | integer | yes | – |
| year | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
modelo_303_summary ~79
Modelo 303 (quarterly VAT) — JSON summary of every quarter with activity. One row per (year, quarter): sales base, output VAT, rectified VAT, input VAT, and the net amount to pay. Use this for a machine-readable overview; use modelo_303_csv for the AEAT-format file of one quarter.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reconcile_movement ~57
Manually match a bank movement to an invoice/purchase document. Args: movement_id: bank movement UUID. document_id: invoice or purchase UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | – |
| movement_id | string | yes | – |
No output schema declared.
No examples provided.
reconciliation_board ~52
Get the reconciliation board: suggested movement<->document matches. The system auto-reconciles matches with confidence >= 0.95; everything below is a suggestion to confirm (reconcile_movement) or dismiss.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trial_balance ~61
Balance de sumas y saldos (trial balance) across every account. A one-shot overview of all account balances — no account_id needed. Args: at_date: ISO date to compute balances as of (default: today).
| Name | Type | Req | Description |
|---|---|---|---|
| at_date | – | – | – |
No output schema declared.
No examples provided.
whoami ~96
Verify the token and return the active tenant (id, name, VAT, currency…). Call this first. A 200 confirms the token works; a 401/403 means it is missing, revoked, or malformed. Note: with an 'agl_' API key this reads /tenants/me. The /auth/me endpoint is reserved for interactive session logins (onboarding/membership flow) and deliberately rejects API keys.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.mutonby/aikount-mcp server?
io.github.mutonby/aikount-mcp runs locally as a PyPI package, launched with uvx aikount-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · aikount-mcp
claude mcp add mutonby-aikount-mcp -- uvx aikount-mcp
What is the io.github.mutonby/aikount-mcp server?
io.github.mutonby/aikount-mcp is listed in the public MCP registry as io.github.mutonby/aikount-mcp. Contabilidad española con IA: facturas, gastos por OCR, conciliación bancaria e impuestos AEAT. This page covers its PyPI package (aikount-mcp).
Is the io.github.mutonby/aikount-mcp server safe to use?
io.github.mutonby/aikount-mcp scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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.mutonby/aikount-mcp server expose?
io.github.mutonby/aikount-mcp exposes 23 tools: whoami, list_contacts, create_contact, list_tax_types, list_products, and 18 more. Their descriptions and schemas cost roughly 2,005 tokens of context every time the server is loaded.
Is the io.github.mutonby/aikount-mcp server still maintained?
io.github.mutonby/aikount-mcp 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 licence is the io.github.mutonby/aikount-mcp server under?
io.github.mutonby/aikount-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.mutonby/aikount-mcp server?
VerifyMCP ran 16 checks on io.github.mutonby/aikount-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.