Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentTax

NPM · @AGENTTAX/MCP-SERVER

US sales/use tax, nexus thresholds, capital gains and 1099-DA tools for AI agent transactions.

+2 this week 83 Trust /100

Last scanned (4 hours ago)

Scores higher than 76% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to AgentTax/agenttax-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2449 tokens (~163/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 −1
    • Schema quality: 126 → 163 ▼ functional
    • Package version: 1.2.0 → 1.3.0 functional
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
Diagnostics

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 5 Nov 2026 · Analysed npm/@agenttax/mcp-server@1.3.0

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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo AgentTax/agenttax-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/AgentTax/agenttax-mcp/.github/workflows/publish.yml@refs/tags/v1.3.0
Rekor log index 3657794588
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d4011daefec0d221f6414c7d9d318a22f6826ce7115bc57a422a1a7a8795feb8a117ee5c7f693724f281f37fb7b3bdfcac2d6030ada0fb8854c96af3c

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~2,449 tokens

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 →

Tool Tokens
calculate_tax ~1,000

Calculate US sales tax (seller) or use tax (buyer) for an AI agent transaction. Returns tax amount, rate, jurisdiction, audit trail, confidence score, and advisories. Sellers get $0 sales tax in states without configured nexus (see configure_nexus); a $0 total means no collection obligation, not necessarily no tax, so read nexus_warning and advisories. work_type and transaction_type are sent as you give them and treated as declared facts (e.g. consulting is exempt in Arizona), so do not guess them. The response carries resolution.location / resolution.nexus / resolution.taxability, each with status resolved, partial or unknown plus a basis; total_tax is always returned, so if you want "unknown means do not charge", branch on resolution.*.status. Pass intent "estimate" to quote before a wallet signs: nothing is saved to history or nexus revenue, but it counts toward your monthly quota. Without intent (or with "record"), a keyed call is logged to your history, which is why this tool is annotated as writing even for estimates.

NameTypeReqDescription
amountnumberyesTransaction amount in USD
buyer_statestringyes2-letter US state code of the buyer (or DC)
buyer_zipstring–Buyer's 5-digit zip code for local rate lookup
counterparty_idstringyesIdentifier for the other party (letters, digits and _-.:@ only)
custom_software_attestationobject–Required with work_type custom_software; without a complete attestation the sale is answered as prewritten software / SaaS. Complete = written_for_buyer true, not_offered_to_others true, deliverable…
digital_content_typestring–With transaction_type digital_good: what the download is. Several states tax e-books, music and video but not digital art or printables
includes_prewritten_software_accessboolean–With transaction_type web_hosting: true when the plan gives the buyer vendor prewritten software beyond an incidental control panel or file manager (site builder, CMS or app platform, email or office…
intentstring–"estimate" = quote before a wallet signs; nothing is saved to history or nexus revenue; counts toward your quota. "record" (the default with an API key) logs the calculation. Keyless demo calls are a…
is_b2bboolean–Business-to-business transaction (triggers state B2B rules, e.g. IA, MD)
it_support_scopestring–With transaction_type or work_type it_support: what the remote IT support engagement is. Absent = managed_bundle, the per-state default; some states answer specific scopes differently
maintenance_contractobject–With transaction_type software_maintenance: facts about a maintenance contract on prewritten software. Every field is optional; a missing fact is answered conservatively (updates assumed included). s…
payment_provider_typestring–With transaction_type payment_processing_fee: who provides the payment processing. Changes the answer in some states; absent = the conservative answer. Your representation, recorded with the transact…
rolestringyesYour role in the transaction
seller_remittingboolean–Buyer side: whether the seller is already collecting the tax
seller_state––Seller's 2-letter state code (needed for origin-sourced intrastate sales)
seller_zip––Seller's 5-digit zip. Required for TX/UT/AZ/TN origin-sourced intrastate sales and intrastate OH license/digital_good sales
transaction_typestringyesType of transaction
use_contextstring–Maryland only, with is_b2b=true: whether the purchase is solely for use in an enterprise computer system
work_typestring–What the agent's work is economically; drives per-state taxability (compute, research, information_service, content, consulting, trading, payment_processing, web_hosting, software_maintenance, it_sup…

No output schema declared.

No examples provided.

check_health ~25

Check AgentTax API health, available endpoints, pricing tiers, and registry validation status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

configure_nexus ~84

Set which US states you have economic nexus in. Sellers must configure nexus to get non-zero sales tax results. Merge semantics: only the states you send change; send hasNexus:false to remove one. Requires API key.

NameTypeReqDescription
nexusobjectyesState codes as keys, e.g. { TX: { hasNexus: true, reason: '...' } }

No output schema declared.

No examples provided.

export_1099_da ~86

Export a DRAFT IRS Form 1099-DA payload for realized digital-asset gains from your logged trades: payer and recipient blocks, per-trade lines (boxes 1a–5), and a short/long-term summary. Draft only; not a filed return. Requires API key.

NameTypeReqDescription
yearinteger–Tax year; defaults to the current year

No output schema declared.

No examples provided.

get_capital_gains_rates ~75

Get state capital gains rates (short and long term) with federal context and per-state caveats, for all states or one. No API key needed.

NameTypeReqDescription
explainboolean–With state: add an explanation block
statestring–2-letter state code. Omit for all states.

No output schema declared.

No examples provided.

get_local_rate ~61

Get the combined state + local sales tax rate for a US zip code, with the breakdown and self-administered locality flags (e.g. Colorado home-rule cities). No API key needed.

NameTypeReqDescription
zipstringyes5-digit US zip code

No output schema declared.

No examples provided.

get_nexus ~37

List the states where you have told AgentTax you have nexus, with each state's rate and how nexus monitoring measures thresholds. Requires API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_nexus_thresholds ~87

Get each state's economic nexus threshold (revenue and transaction count), whether it has sales tax, marketplace-facilitator and origin-sourcing rules, notes, and the state DOR source link. Use it to see where your sales could require registration. No API key needed.

NameTypeReqDescription
statestring–2-letter state code. Omit for all 51 jurisdictions.

No output schema declared.

No examples provided.

get_pricing ~36

Get AgentTax's machine-readable pricing contract: tiers, call limits, and the x402 per-call price. No API key needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_rates ~104

Get US state sales tax rates with digital-goods taxability, SaaS notes, and verification metadata, for all 51 jurisdictions or one state. No API key needed.

NameTypeReqDescription
explainboolean–Include human-readable explanations for the rate and taxability
formatstring–default: full; compact: machine-optimized; verified: with verification details
statestring–2-letter state code for a single state. Omit for all states.

No output schema declared.

No examples provided.

ingest_transactions ~62

Bulk-log up to 100 transactions (e.g. purchases from third-party x402 sellers) into your AgentTax history in one call. Idempotent on external_tx_id. Requires API key.

NameTypeReqDescription
recordsarrayyesTransactions to log (max 100)

No output schema declared.

No examples provided.

list_trades ~58

List trades you have logged, with realized gains on sells. Requires API key.

NameTypeReqDescription
asset_symbolstring––
limitinteger–Default 50
offsetinteger––
trade_typestring––

No output schema declared.

No examples provided.

list_transactions ~85

List your logged transactions with a running summary (seller/buyer counts, total taxable, total tax). Requires API key.

NameTypeReqDescription
limitinteger––
rolestring––
sincestring–ISO 8601 date or date-time lower bound, e.g. 2026-08-01
statestring–Filter to one state

No output schema declared.

No examples provided.

log_trade ~272

Log a buy or sell trade for capital gains tracking. Sell trades return realized gain/loss with cost basis, holding period, and federal/state estimates. Feeds the 1099-DA export. Requires API key.

NameTypeReqDescription
accounting_methodstring–Cost basis method (default: fifo)
asset_classstring–stock/security/equity enables wash-sale tracking; digital_asset/crypto do not
asset_symbolstringyesAsset ticker: equity (AAPL), crypto (BTC), or token (COMPUTE-TOKEN)
estimated_annual_incomenumber–Enables bracket-aware federal estimate and NIIT detection
fee_amountnumber–Fees in USD (default 0)
filing_statusstring––
notesstring–Free-text notes about the trade
price_per_unitnumberyesPrice per unit in USD
quantitynumberyesNumber of units
resident_statestring–Resident state for the state capital gains estimate
specific_lot_idstring–Lot ID, required when accounting_method is specific_id
tax_entity_typestring––
trade_datestring–ISO 8601 trade timestamp; defaults to now
trade_typestringyesBuy or sell

No output schema declared.

No examples provided.

track_payment ~377

Track a payment you received and calculate your sales tax liability. Call this after receiving any payment — Stripe, x402, or direct. Calculates tax owed and logs it to your AgentTax account (requires API key for history). Pass work_type when you know what you sold, for an exact answer; it is the only way to get the consulting exemption (AI consulting is exempt in Arizona) or the trading exemption. Without it the sale is classified from description: a description that looks like consulting or trading is taxed as SaaS, never exempt; one that looks like compute or research keeps that classification, which can tax less than SaaS in some states (e.g. CT, MD, SC, TN, WV).

NameTypeReqDescription
amountnumberyesPayment amount in USD
buyer_statestringyes2-letter US state where the buyer is located (e.g. TX, NY, CA)
buyer_zipstring–Buyer's 5-digit zip code for local tax rates (more precise)
descriptionstring–What you sold (e.g. 'API access', 'MCP tool subscription', 'compute credits'). Used only when work_type is not given; a guess never takes the consulting or trading exemption
is_b2bboolean–Buyer is a business (affects rates in MD, IA, NJ, OH). Omit if unknown: false declares a consumer
payment_idstring–Your payment reference ID (Stripe payment_intent ID, x402 receipt, invoice number); letters, digits and _-.:@ only
sourcestring–Payment processor used
work_typestring–What you sold, declared: compute, research, information_service, content, consulting, trading. Overrides description. consulting is an exempt professional service in Arizona

No output schema declared.

No examples provided.

Install

How do I install the AgentTax MCP server?

AgentTax runs locally as an npm package, launched with npx -y @agenttax/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @agenttax/mcp-server

# add to Claude Code
claude mcp add agenttax-agenttax-mcp -- npx -y @agenttax/mcp-server
Common questions

What is the AgentTax MCP server?

AgentTax is an MCP server listed in the public MCP registry as io.github.AgentTax/agenttax-mcp. US sales/use tax, nexus thresholds, capital gains and 1099-DA tools for AI agent transactions. This page covers its npm package (@agenttax/mcp-server).

Is the AgentTax MCP server safe to use?

AgentTax scores 83 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 AgentTax MCP server expose?

AgentTax exposes 15 tools: calculate_tax, track_payment, ingest_transactions, list_transactions, log_trade, and 10 more. Their descriptions and schemas cost roughly 2,449 tokens of context every time the server is loaded.

Is the AgentTax MCP server still maintained?

AgentTax is still listed as active in the MCP registry. We last reached this channel on 5 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 AgentTax MCP server under?

AgentTax declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.