Terminal Tax MCP server
tax.terminal/filingterminal.taxstreamable-httpv0.338.0Scanned
Tax software: your AI agent sends the facts, we calculate and e-file; you review and sign.
3 tools: 2 can delete or cancel things and 1 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Terminal Tax MCP server can do
The Terminal Tax MCP server is published by terminal.tax, a domain the MCP Registry verified. It has 3 tools. It can delete or cancel things (2 tools: create_filing_session and continue_filing_session). 1 tool only reads.
3 tools bring in text other people can write (create_filing_session, get_packet_schema and continue_filing_session).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 6 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 0.338.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Deletes or cancels 2Claude Code: deny
continue_filing_sessionChecks the taxpayer's completed draft packet for a federal return and, when it passes, holds it as an unsigned draft and returns the link to the filing page; otherwise returns a li…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Checks the taxpayer's completed draft packet for a federal return and, when it passes, holds it as an unsigned draft and returns the link to the filing page; otherwise returns a list of problems to correct. This call files nothing and sends nothing to the IRS: the taxpayer reviews, signs and files on the filing page. Inputs: the filing session's continuationHandle, completedReturnPacketJson (the whole packet as one JSON string, in this server's packet schema) and packetSchemaSha256 (that schema's digest); other arguments are refused by name. The tax year is return.taxYear=2025 inside the packet. The packet carries the facts the taxpayer stated in this chat and the figures printed on documents the taxpayer gave in it; a fact the taxpayer has not stated is left out rather than written as no, none or 0, and a required fact that is left out comes back as a blocker asking for the taxpayer's answer. Output: status filing_session_ready with a filingSessionUrl when the packet is accepted; the taxpayer opens that link to give permission, review the return and sign it. Otherwise, blockers (each with a path, a rule and a plain detail) and no link; that packet is not kept, and the same handle accepts a corrected packet. Nothing is filed or charged through a link that expires or is left unfinished, and the same packet sent again with a new filing session's handle returns a fresh link. An accepted packet is held until the taxpayer gives permission on the filing page; declining there, or expiry, erases it. Federal returns: no state, territory or local return is filed. The return has no taxpayer identity fields: the taxpayer's own details go in the packet's separate, required agentIdentity section, which the filing page shows for the taxpayer to confirm. Business identifiers printed on each source form, such as an employer's or payer's name and EIN, are packet fields.
Annotations the server declares
- title: Continue filing session
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
create_filing_sessionStarts a filing session for a US federal individual income tax return when the taxpayer asks to file.Reads text others writeNo findings
Why it is in this group
- The name "create_filing_session" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Starts a filing session for a US federal individual income tax return when the taxpayer asks to file. Input: none. Output: a continuationHandle that identifies this filing session in later calls, and packetRules, the packet rules as text. This call receives no tax facts and creates no return and no link; the filing link comes with an accepted packet. A new filing session is also how a fresh link replaces one that expired or was left unfinished, through which nothing was filed or charged: the same packet sent on the new handle returns the new link. Covered returns: one original tax year 2025 US federal individual income tax return (Form 1040 or 1040-SR, and some Form 1040-SS and Form 1040-NR situations), with no state or local return. The packet rules this call returns list each covered and refused situation.
Annotations the server declares
- title: Start filing session
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Only reads 1Show 1 read-only tool
get_packet_schemaTakes the filing session's continuationHandle.Reads text others writeNo findings
Why it is in this group
- The name "get_packet_schema" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Takes the filing session's continuationHandle. Returns the packet schema a completed return packet is checked against (the packet holds no Social Security number, ITIN or PIN: the taxpayer types those on the filing page): requestPacketSchema=true returns the schema digest (packetSchemaSha256, sent with the completed packet), an outline whose larger parts are named sections, the section list and the packetStarterTemplates list; packetSchemaSection=<name> returns one section and packetStarterTemplate=<id> one complete starter packet, in which each taxpayer-specific value is the placeholder REPLACE_WITH_TAXPAYER_VALUE, refused by path until replaced, with its askTheTaxpayer messages (the questions for the taxpayer) and each preset answer listed in presets with how it is settled. Read-only: no tax facts are sent here and no return is written. The tax year is return.taxYear=2025 inside the packet, not a tool argument; any other argument is refused by name.
Annotations the server declares
- title: Get packet schema
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:19 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 destructive). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.terminal.tax/v1/hosted-mcp: tools/list returned 3 tools to an anonymous client, including create_filing_session (destructive), continue_filing_session (destructive)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:get_packet_schemaOnly readsinputSchema
Tools1 changed.~1 changedView diff
- Changed:get_packet_schemaOnly readsinputSchema
Tools1 changed.~1 changedView diff
- Changed:get_packet_schemaOnly readsinputSchema
Tools1 changed.~1 changedView diff
- Changed:get_packet_schemaOnly readsinputSchema
Tools1 changed.~1 changedView diff
- Changed:create_filing_sessionDeletes or cancelsdescription
Tools1 removed, 2 changed.−1 removed~2 changedView diff
- Removed:get_filing_status
- Changed:continue_filing_sessionDeletes or cancelsdescriptioninputSchema
- Changed:create_filing_sessionDeletes or cancelsdescription
Install
Pinned to version 0.338.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http filing https://mcp.terminal.tax/v1/hosted-mcpclaude mcp add --transport http filing https://mcp.terminal.tax/v1/hosted-mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__filing__get_packet_schema"
],
"ask": [],
"deny": [
"mcp__filing__create_filing_session",
"mcp__filing__continue_filing_session"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as filing. Review it before you use it.
Capability tags behind 3 rules
- mcp__filing__create_filing_session untrusted-input
- mcp__filing__get_packet_schema untrusted-input
- mcp__filing__continue_filing_session untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/tax.terminal/filing/verify?hash=aafac89b35321d19cceb95bbff181a6cd7908986606dff261944bf35e4e16fbf" | jq -e '.changed == false'Pinned hash aafac89b3532, from Nov 20, 2026, 00:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/tax.terminal/filing/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/tax.terminal/filing)Source: MCP Registry · repository. Synced Nov 6, 2026, 00:18 UTC.
Terminal Tax MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Terminal Tax MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Terminal Tax MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: create_filing_session and continue_filing_session.
Can the Terminal Tax MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Terminal Tax MCP server have?
- 3 tools: 2 destructive, 1 read. create_filing_session, continue_filing_session and get_packet_schema.
Does the Terminal Tax MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Terminal Tax MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Terminal Tax MCP server changed its tools?
- Yes, 6 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.