Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
MTD Chase — chase clients for MTD records 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.
93/100
tool-list score
20
tools declared
remote
at its publisher
—
calls last 7d
What it does
UK bookkeepers: chase clients for Making Tax Digital quarterly records, upload links, reminders.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mtd-chase-chase-clients-for-mtd-records-mcp https://mtd-chase.smallwright.com/mcp
# 2 — ask your agent for something these tools do
# get_mtd_deadlines, get_started, update_practice and 17 more
MTD Chase — chase clients for MTD records costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SMAll 2 servers
smallwright2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 mtd-chase-chase-clients-for-mtd-records-mcp https://mtd-chase.smallwright.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
20 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.
Returns the four MTD for Income Tax quarterly update periods for a tax year (standard and calendar period ends), each deadline, the final declaration date, and days until the next deadline. Works without signing in. Use this when: someone asks when the next quarterly update is due or what a Quarter covers. Not for: whether a particular Client has sent records (whos_outstanding).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tax_year | string | no | e.g. "2026-27". Default: the current tax year. |
Returns the practice's setup and current position: plan and active Clients vs limit, Clients, open Chases per Quarter, settings still unset, and the next few things the practitioner can say. Use this when: the practitioner asks where they're up to or what to do next.
No parameter schema on file.
Changes what Clients see and how MTD Chase behaves for this practice: name shown to Clients, reply-to email, sign-off, phone shown on the Client's page, how many days before the HMRC deadline Clients are asked to send by (0–30, default 10; applies to Chases started afterwards), how many days after a deadline files are kept (30–365), daily summary email on/off, and the default checklist new Chases
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | — |
| reply_to_email | string | no | — |
| sign_off | string | no | — |
| phone | string | no | UK phone number shown to Clients; empty clears it |
| ask_by_days | number | no | 0–30: days before the HMRC deadline that clients are asked to send by |
| retention_days | number | no | 30–365: days after the HMRC deadline that files are kept |
| daily_summary | boolean | no | — |
| default_checklist | array | no | 1–8 items, each up to 120 characters |
| idempotency_key | string | no | Optional; reuse when retrying so the change happens once. |
Exports everything the practice holds in MTD Chase (Clients, Chases with history, Nudges sent, Records list, requests) as one JSON file; returns a download link for the signed-in practitioner. Use this when: they want a copy of their data or are leaving.
No parameter schema on file.
Files a request with MTD Chase when the user asks for something none of the other tools can do, or adds a vote to a matching open request; returns its ID, status and any workaround with existing tools. No date is promised. Use this when: the practitioner wants a capability MTD Chase doesn't have. Not for: reporting a single Client's problem.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| what_the_user_wanted | string | yes | their own words |
| what_they_were_trying_to_achieve | string | yes | the job behind it |
| closest_existing_tool | string | no | — |
| urgency | string | yes | blocking = they can't do the job today; nice_to_have = a workaround exists |
| idempotency_key | string | no | Optional; reuse when retrying so the change happens once. |
Lists the practice's feature requests with status (open, planned, live, declined), how many times each was asked for, the workaround meanwhile, and for declined ones the reason. Use this when: asked what happened to something they asked for. Not for: asking for something new (request_feature) or what's recently live for everyone (whats_new).
No parameter schema on file.
Lists changes that went live recently in MTD Chase, and which of this practice's requests are now live, with the date each went live and what to say to try it. Use this when: the practitioner asks what's new, or whether something they asked for is live yet.
No parameter schema on file.
Adds Clients (people the practice does MTD quarterly updates for) from a pasted list; matches existing Clients by email, else exact name. confirm:false (default) shows what would be added, skipped as duplicates, or rejected, and the plan-limit effect; confirm:true saves. Max 500. Use this when: setting up or adding MTD clients from a spreadsheet or accounting-software export, or a typed list. Not
| Parameter | Type | Required | Notes |
|---|---|---|---|
| clients | array | yes | — |
| confirm | boolean | no | false (default) = dry run: shows what would happen, changes nothing. true = do it. |
| idempotency_key | string | no | Optional; reuse when retrying so the change happens once. |
Changes one Client's name, email, mobile, period type (standard/calendar), tags or reference. Returns before → after. Use this when: a Client's details change. Not for: stopping chasing someone (archive_client) or pausing nudges (pause_nudges).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client | string | yes | Client name, email or your own reference |
| name | string | no | — |
| string | no | — | |
| mobile | string | no | — |
| period_type | string | no | — |
| tags | array | no | — |
| ref | string | no | — |
| idempotency_key | string | no | Optional; reuse when retrying so the change happens once. |
Archives a Client who has left: their open Chases become skipped and their links stop working; they stop counting towards the plan limit. confirm:false (default) shows what would change. unarchive:true brings them back. Use this when: a Client leaves the practice or comes back.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client | string | yes | Client name, email or your own reference |
| unarchive | boolean | no | — |
| confirm | boolean | no | false (default) = dry run: shows what would happen, changes nothing. true = do it. |
| idempotency_key | string | no | Optional; reuse when retrying so the change happens once. |
Lists Clients with contact details, period type, tags and the status of their Chase for the current Quarter. Use this when: looking up who the practice has, finding a Client's details, or seeing a tagged group (e.g. landlords) with this Quarter's status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | no | part of a name or email |
| tag | string | no | — |
| period_type | string | no | — |
| include_archived | boolean | no | — |
Starts chasing Clients for their records for a Quarter: each gets a personal link (no login, works on a phone) and a first email; then Nudges go out on the practice's plan until they send their records. confirm:false (default) shows who would be chased, who has no email, the checklist and the dates (the date Clients are asked to send by, and the HMRC deadline); confirm:true starts it. Safe to repe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quarter | string | no | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
| clients | yes | "all", or Client names/emails/tags | |
| checklist | array | no | what to send, 1–8 items; default: the practice's checklist (sales and income, receipts and invoices for expenses, bank statements for accounts the practice can't already see) |
| confirm | boolean | no | false (default) = dry run: shows what would happen, changes nothing. true = do it. |
| idempotency_key | string | no | Optional; reuse when retrying so the change happens once. |
Returns each Client's personal records link for a Quarter and a ready-to-paste message for a messaging app or text. Use this when: the practitioner wants to send a link themselves (no email on file, or they prefer a messaging app or text).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quarter | string | no | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
| clients | array | no | names/emails; default all being chased |
Sets one Client's Chase for a Quarter to ready, partial, nothing_to_report, skipped or back to waiting, with an optional note; Nudges stop for ready/nothing_to_report/skipped and resume for waiting/partial. The change is recorded in the Client's history. Use this when: records arrived another way (office, post, email) or a Client should be skipped this Quarter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client | string | yes | Client name, email or your own reference |
| quarter | string | no | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
| status | string | yes | — |
| note | string | no | — |
| recount | boolean | no | true = recount lateness from now |
| idempotency_key | string | no | Optional; reuse when retrying so the change happens once. |
Lists the files (name, size, received) a Client sent through their link for a Quarter — or for every Client in a Quarter — with download links valid 24 hours for the signed-in practitioner, and the Client's note marked as written by the Client. Use this when: asked what a Client sent or to download it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quarter | string | no | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
| client | string | no | Client name, email or your own reference |
Sets when Nudges (reminder emails) go out for every Chase, including ones already running, counted from the date Clients are asked to send by (the ask-by date): days before it, on the day, and days after it, sent at 09:00 UK time on weekdays. A value left out keeps its current setting. Returns the plan in words and this Quarter's remaining nudge dates. Use this when: the practitioner wants reminde
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days_before | array | no | 1–60, up to 6 values: days before the date clients are asked to send by |
| on_the_day | boolean | no | also nudge on the ask-by date itself |
| days_after | array | no | 1–60, up to 6 values: days after it |
| idempotency_key | string | no | Optional; reuse when retrying so the change happens once. |
Sends a Nudge email now to Clients who haven't finished sending records for a Quarter (waiting or partial), at most one per Client per day. confirm:false (default) lists who would get one and who is excluded (no email, nudged today, paused); confirm:true sends. Use this when: chasing up everyone outstanding, or named Clients, now — an extra reminder outside the plan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quarter | string | no | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
| clients | array | no | Client names, emails or references; default: everyone outstanding |
| only_status | string | no | e.g. waiting = only those who've sent nothing |
| confirm | boolean | no | false (default) = dry run: shows what would happen, changes nothing. true = do it. |
| idempotency_key | string | no | Optional; reuse when retrying so the change happens once. |
Stops all Nudges to one Client until a date (YYYY-MM-DD) or until resumed; resume:true restarts them. The result warns if the pause runs past a deadline. Use this when: a Client is ill, away or has asked for no reminders for now. Not for: a Client who has left (archive_client) or has sent their records (mark_chase).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client | string | yes | Client name, email or your own reference |
| until | string | no | YYYY-MM-DD |
| resume | boolean | no | — |
| idempotency_key | string | no | Optional; reuse when retrying so the change happens once. |
Returns the Clients who haven't finished sending records for a Quarter (waiting or partial), with days to/after the date they were asked to send by, last Nudge, whether they opened their link, and counts per status. Use this when: asked who's still outstanding, who's sent what, or how the Quarter is going. Not for: one tagged group (list_clients with tag).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quarter | string | no | Quarter like "2026-27 Q3". Default: the Quarter whose HMRC deadline is next. |
| late_last_quarter | boolean | no | only those who were late last Quarter |
Returns a Client's Chases across Quarters — when they finished and how many days early or late against the date they were asked to send by (and whether before or after the HMRC deadline) — with a one-line summary. Without a client, returns every active Client ranked by how late they usually are. Use this when: asked whether a Client is usually late, how they did last time, or who's always late. No
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client | string | no | Client name, email or your own reference |
Free
$0 forever
- 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 MTD Chase — chase clients for MTD records or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.1.0 · scanned 5 Nov 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest7acbe66d7186c53eca563667bd125a312b320cb07622431e00232d3ca26eb278
Score vectorthreat 100 → client 93
| 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 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
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 |
|---|---|---|
| get_mtd_deadlines | no tags | |
| get_started | no tags | |
| update_practice | state-write | state-write: declares readOnlyHint: false |
| export_practice_data | untrusted-input | untrusted-input: keyword "download" |
| request_feature | state-write | state-write: declares readOnlyHint: false |
| list_my_requests | no tags | |
| whats_new | no tags | |
| add_clients | state-write | state-write: declares readOnlyHint: false |
| update_client | state-write | state-write: declares readOnlyHint: false |
| archive_client | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_clients | no tags | |
| start_chase | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_chase_links | no tags | |
| mark_chase | state-write | state-write: declares readOnlyHint: false |
| list_records | untrusted-input | untrusted-input: keyword "download" |
| set_nudge_plan | state-write | state-write: declares readOnlyHint: false |
| send_nudges_now | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| pause_nudges | state-write | state-write: declares readOnlyHint: false |
| whos_outstanding | no tags | |
| get_client_history | 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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest7acbe66d7186c53e
Scanned2026-11-05
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 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish MTD Chase — chase clients for MTD records can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.