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.

Ziptax Sales Tax API

REMOTE · MCP.ZIP-TAX.COM

Real-time US and Canadian sales and use tax rates by address or geo coordinates.

Available components

+3 this week 77 Trust /100

Last scanned (21 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 22 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 525 tokens (~262/item across 2 items; 2 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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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.

  • 21 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.

  • 19 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.

  • 17 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.

  • 15 Oct 26 +1

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

  • 13 Oct 26 +1

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

  • 12 Oct 26 +1

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

  • 9 Oct 26 71

    First indexed and scored.

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 22 Oct 2026 · Probed https://mcp.zip-tax.com/

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.zip-tax.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 13 Aug 2026 26 Feb 2027 RSA 2048 SHA256-RSA 7b0471eb158f891b6a5205f2f22c189
SANs: mcp.zip-tax.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.zip-tax.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
zip-tax.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.zip-tax.com/ Verified 200
http (plaintext) http://mcp.zip-tax.com/ HTTPS enforced 301 https://mcp.zip-tax.com:443/
MCP tools · 2 exposed · ~469 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
get_account_metrics ~64

Get account usage metrics and quota information for the authenticated ZipTax account. Returns current request counts, limits, and entitlements. Requires a valid ZipTax API key sent in the X-API-KEY header or Authorization header. Get a key at https://platform.zip.tax

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_tax_rate ~405

Look up sales and use tax rates for a US or Canadian location. Provide a full street address for door-level accuracy, or a lat/lng pair for a geographic point lookup. Returns tax rates broken down by jurisdiction (state, county, city, district). Requires a valid ZipTax API key sent in the X-API-KEY header or Authorization header. Get a key at https://platform.zip.tax

NameTypeReqDescription
addressstring–Full street address for door-level geocoded lookup. Preferred input
adjustmentstring–Set to 'auto' to enable state-specific unincorporated area adjustments
citystring–City name
country_codestring–Country code: US (default) or CA for Canada. CA requires a Pro or Enterprise plan
countystring–County name
formatstring–Response format: 'json' (default) or 'xml'
historicalstring–Historical period in YYYYMM format (e.g., 202601 for January 2026); lookback is limited to the past 12 months. Requires a Pro or Enterprise plan
latstring–Latitude for coordinate-based lookup. Same door-level precision as an address
lngstring–Longitude for coordinate-based lookup. Same door-level precision as an address
postalcodestring–US ZIP code (5-digit) or Canadian postal code. Least precise option: returns every rate overlapping the ZIP rather than one authoritative rate, with no adjustment for unincorporated areas. Use only w…
sat_item_totalstring–Item total for Tennessee Single Article Tax calculation
statestring–Two-letter US state or Canadian province code (e.g., CA, ON)
taxability_codestring–Product taxability code (TIC) for product-specific tax rules. Requires a Pro or Enterprise plan

No output schema declared.

No examples provided.

Install

How do I install the Ziptax Sales Tax API MCP server?

Ziptax Sales Tax API is a hosted endpoint at https://mcp.zip-tax.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.zip-tax.com

# add to Claude Code
claude mcp add --transport http tax-zip-ziptax 'https://mcp.zip-tax.com/'
Common questions

What is the Ziptax Sales Tax API MCP server?

Ziptax Sales Tax API is an MCP server listed in the public MCP registry as tax.zip/ziptax. Real-time US and Canadian sales and use tax rates by address or geo coordinates. This page covers its hosted endpoint (https://mcp.zip-tax.com/).

Is the Ziptax Sales Tax API MCP server safe to use?

Ziptax Sales Tax API scores 77 out of 100 on VerifyMCP. 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 Ziptax Sales Tax API MCP server expose?

Ziptax Sales Tax API exposes 2 tools: get_account_metrics, lookup_tax_rate. Their descriptions and schemas cost roughly 469 tokens of context every time the server is loaded.

Does the Ziptax Sales Tax API MCP server require authentication?

No. We connected to Ziptax Sales Tax API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ziptax Sales Tax API MCP server still maintained?

Ziptax Sales Tax API is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.