Alpaca Trading API integration for Model Context Protocol (MCP)
taxtrace 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
Masked, read-only views of a local tax workspace: documents, form checks and to-dos.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user taxtrace-mcp '--' uvx --with 'mcp>=2.2' 'taxtrace[mcp]' mcp
# 2 — ask your agent for something these tools do
# get_status, list_documents, get_document_outline and 2 more
taxtrace 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. This one runs on your machine: your client starts taxtrace as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user taxtrace-mcp '--' uvx --with 'mcp>=2.2' 'taxtrace[mcp]' mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take TAXTRACE_HOME (Path to your tax workspace folder (documents by tax year, todo.md). Defaults to ~/TaxData. Outside any git repository.) if you want to set it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
5 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
What the person's workspace holds, as counts: tax years (folders named for one), each folder's number of documents, how many documents taxtrace has read, how many files it saved per kind of reading, and whether a to-do list exists. Names are masked. Start here; for the documents themselves use…
Takes no parameters.
The workspace's documents, each with an id, its folder and file name (masked), its kind (pdf, csv, ...) and whether it was read. Nothing is opened, so no password is asked for. The id is what get_document_outline and get_form_checks take. For counts only use get_status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| only | no | all (default), read (taxtrace has saved something from it) or unread (nothing saved yet: the ones still to read). |
A document's pages, each with its first lines masked: which forms and worksheets it holds, and in what order. A password-protected document is reported as locked, not opened (taxtrace's own commands read it with a password from the Keychain). To see how the forms in it checked out use…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | yes | — | |
| start | integer | no | The first page to list (default 1). |
| limit | integer | no | How many pages to list from start (default 40, at most 200). |
| lines | integer | no | How many of each page's first lines to show, masked (default 2: on a tax form they name the form). |
Read the forms of one kind in the workspace's PDFs and report how their checks came out, never a value: per form its document id, page, tax year, how many checks passed of how many, the ones that failed and the questions it leaves the person (box names and masked quotes). Every value taxtrace…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| form | yes | Which form to read: 1098 (mortgage interest), 1099 (the 1099-DIVs and 1099-INTs on a broker's statement) or k1 (the federal Schedule K-1 face). | |
| id | integer | no | Only this document (its id from list_documents). Omit to read every PDF in the workspace, which can take a while. |
The person's open money and tax to-dos from todo.md in their workspace, soonest first: section, due date, days left, group (overdue, today, week, later, undated), and the text, notes and sub-tasks masked (the dates are real; the wording is masked, so ask the person what an item says if it…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Only the overdue items and those due within this many days from today. Omit for every open item, soonest first, undated last. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 taxtrace 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 | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tools were statically extracted from the published source (5 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_status | no tags | |
| list_documents | no tags | |
| get_document_outline | no tags | |
| get_form_checks | no tags | |
| get_todo | no tags |
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
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 taxtrace 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.