Remote MCP · Endpoint

Ziptax Sales Tax API MCP server

No. Ziptax Sales Tax API answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://mcp.zip-tax.com/

The last check completed an MCP handshake.

Registry name
tax.zip/ziptax
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
32 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Real-time US and Canadian sales and use tax rates by address or geo coordinates.
Listing
From the official MCP registry (active).
Recent checks of Ziptax Sales Tax API
CheckedResultHandshake
10 hours agoHandshake completed32 ms
3 days agoHandshake completed31 ms
12 days agoHandshake completed25 ms
13 days agoHandshake completed20 ms
14 days agoHandshake completed23 ms
15 days agoHandshake completed42 ms
16 days agoHandshake completed27 ms
17 days agoHandshake completed23 ms
18 days agoHandshake completed20 ms
20 days agoHandshake completed23 ms
22 days agoHandshake completed28 ms
25 days agoHandshake completed35 ms
27 days agoHandshake completed27 ms
30 days agoHandshake completed23 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 22 responding of 22.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Ziptax Sales Tax API and makes no claim about it beyond what these checks measured.