Alpaca Trading API integration for Model Context Protocol (MCP)
Quipu MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read contacts, invoices and book entries; create contacts and draft invoices in Quipu.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http quipu-mcp-by-usefulapi https://quipu.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# quipu_list_contacts, quipu_get_contact, quipu_list_invoices and 8 more
Quipu MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http quipu-mcp-by-usefulapi https://quipu.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List contacts (clients and suppliers) of the Quipu account. Filter by kind, tax id, country, email or free text.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | Only clients or only suppliers. |
| tax_id | string | no | Exact NIF/CIF/tax id. |
| country | string | no | Two-letter country code, for example ES. |
| string | no | — | |
| q | string | no | Free-text search (name, tax id, email). |
| sort | string | no | Sort field; prefix with - for descending. |
| page | integer | no | Page number (1-based, default 1). |
| page_size | integer | no | Results per page (1-100, default 25). |
Get one contact by id, with its totals of paid and unpaid incomes and expenses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string/number | yes | Quipu resource id (integer). |
List invoices (issued and received). Filter by kind, period, operation date, payment status or contact. Totals and PDF links are in the attributes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | income = issued invoices, expenses = received invoices. |
| q | string | no | Free-text search. |
| period | string | no | Period such as "2024Q1" or "2024-01". |
| operation_date | string | no | Year (2024), quarter (2024-Q1), month (2024-3) or all. Works with kind=income. |
| operation_date_from | string | no | Start of an explicit range; send with operation_date_to. Works with kind=income. |
| operation_date_to | string | no | End of an explicit range; send with operation_date_from. |
| payment_status | string | no | Payment status. unpaid includes pending and overdue. |
| validation_status | string | no | — |
| contact_id | string/number | no | Only invoices of this contact. |
| include | string | no | Comma-separated related resources to include (for example contact,items). |
| page | integer | no | Page number (1-based, default 1). |
| page_size | integer | no | Results per page (1-100, default 25). |
Get one invoice by id. Income invoices include download_pdf_url and ephemeral_open_download_pdf_url (a temporary PDF link).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_id | string/number | yes | Quipu resource id (integer). |
| include | string | no | Comma-separated related resources to include (for example contact,items). |
List all book entries (invoices, tickets and other accounting entries) in one list. Filter by type, kind, period, dates, payment status or contact.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Entry type filter. |
| kind | string | no | income = issued invoices, expenses = received invoices. |
| q | string | no | Free-text search. |
| period | string | no | Period such as "2024Q1" or "2024-01". |
| operation_date | string | no | Year, quarter, month or all. Works with kind=income. |
| payment_status | string | no | Payment status. unpaid includes pending and overdue. |
| validation_status | string | no | — |
| contact_id | string/number | no | Quipu resource id (integer). |
| include | string | no | Comma-separated related resources to include (for example contact,items). |
| with_detailed_amounts | boolean | no | Add detailed amounts to each entry. |
| sort | string | no | — |
| page | integer | no | Page number (1-based, default 1). |
| page_size | integer | no | Results per page (1-100, default 25). |
List invoice numbering series (prefixes). Use a series id when you create a draft invoice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| applicable_to | string | no | — |
| amending | boolean | no | Only series for amending (credit) invoices. |
| prefix | string | no | — |
| page | integer | no | Page number (1-based, default 1). |
| page_size | integer | no | Results per page (1-100, default 25). |
List accounting categories (chart of accounts groups). Filter by kind, prefix or active state.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | — |
| prefix | string | no | — |
| active | boolean | no | — |
| page | integer | no | Page number (1-based, default 1). |
| page_size | integer | no | Results per page (1-100, default 25). |
List accounting subcategories, optionally for one accounting category.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| accounting_category_id | string/number | no | Quipu resource id (integer). |
| page | integer | no | Page number (1-based, default 1). |
| page_size | integer | no | Results per page (1-100, default 25). |
Create a contact (client or supplier). WRITE: it adds a record to the Quipu account. A tax id is needed before you invoice the contact.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| country_code | string | yes | Two-letter country code, for example ES. |
| tax_id | string | no | NIF/CIF/tax id. |
| document_type | string | no | — |
| string | no | — | |
| phone | string | no | — |
| address | string | no | — |
| town | string | no | — |
| zip_code | string | no | — |
| client_number | string | no | — |
| bank_account_number | string | no | — |
Update fields of one contact. WRITE: it changes the record; only the fields you send change.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string/number | yes | Quipu resource id (integer). |
| name | string | no | — |
| country_code | string | no | — |
| tax_id | string | no | — |
| document_type | string | no | — |
| string | no | — | |
| phone | string | no | — |
| address | string | no | — |
| town | string | no | — |
| zip_code | string | no | — |
| client_number | string | no | — |
| bank_account_number | string | no | — |
Create a DRAFT income invoice for a contact. WRITE: it adds a draft to Quipu. It sends no issue date or number, so Quipu does not issue or register the invoice; finalize it in the Quipu app.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string/number | yes | Id of the client contact. |
| numbering_series_id | string/number | no | Numbering series id (see quipu_list_numbering_series). |
| operation_date | string | no | Date of the delivery or service. |
| payment_method | string | no | For example bank_transfer, cash, card. |
| tags | string | no | — |
| notes | string | no | — |
| items | array | yes | Invoice lines. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Quipu MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| quipu_list_contacts | no tags | |
| quipu_get_contact | no tags | |
| quipu_list_invoices | no tags | |
| quipu_get_invoice | untrusted-input | untrusted-input: keyword "download" |
| quipu_list_book_entries | no tags | |
| quipu_list_numbering_series | no tags | |
| quipu_list_accounting_categories | no tags | |
| quipu_list_accounting_subcategories | no tags | |
| quipu_create_contact | state-write | state-write: declares destructiveHint: true |
| quipu_update_contact | no tags | |
| quipu_create_draft_invoice | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.7.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Quipu MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.