_ registry / mcp streamable-http · checked 1h ago

ZipTax Sales Tax API

https://mcp.zip-tax.com

Registry code: 6ac937f213c08321

api record

ZipTax MCP Server provides US and Canadian sales tax rate lookups. Authenticate by sending your ZipTax API key in the X-API-KEY HTTP header or as a Bearer token in the Authorization header. Get an API key at https://platform.zip.tax

endpoint
https://mcp.zip-tax.com
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is ZipTax Sales Tax API live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ZipTax Sales Tax API free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does ZipTax Sales Tax API have?
2 tools: lookup_tax_rate, get_account_metrics.
Is ZipTax Sales Tax API safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
666ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 333 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • look up sales tax rate for an address
  • check api usage quota
takes → gives
text, data → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
2 auth-required 2 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • lookup_tax_rate reads auth-required 6h ago

    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

    mcp-tool

    {
      "type": "object",
      "anyOf": [
        {
          "required": [
            "address"
          ]
        },
        {
          "required": [
            "lat",
            "lng"
          ]
        }
      ],
      "required": [],
      "properties": {
        "lat": {
          "type": "string",
          "description": "Latitude for coordinate-based lookup. Same door-level precision as an address"
        },
        "lng": {
          "type": "string",
          "description": "Longitude for coordinate-based lookup. Same door-level precision as an address"
        },
        "city": {
          "type": "string",
          "description": "City name"
        },
        "state": {
          "type": "string",
          "description": "Two-letter US state or Canadian province code (e.g., CA, ON)"
        },
        "county": {
          "type": "string",
          "description": "County name"
        },
        "format": {
          "type": "string",
          "description": "Response format: 'json' (default) or 'xml'"
        },
        "address": {
          "type": "string",
          "description": "Full street address for door-level geocoded lookup. Preferred input"
        },
        "adjustment": {
          "type": "string",
          "description": "Set to 'auto' to enable state-specific unincorporated area adjustments"
        },
        "historical": {
          "type": "string",
          "description": "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"
        },
        "postalcode": {
          "type": "string",
          "description": "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 when no address or lat/lng is available"
        },
        "country_code": {
          "type": "string",
          "description": "Country code: US (default) or CA for Canada. CA requires a Pro or Enterprise plan"
        },
        "sat_item_total": {
          "type": "string",
          "description": "Item total for Tennessee Single Article Tax calculation"
        },
        "taxability_code": {
          "type": "string",
          "description": "Product taxability code (TIC) for product-specific tax rules. Requires a Pro or Enterprise plan"
        }
      }
    }
    arguments 71 lines
  • get_account_metrics reads auth-required 6h ago

    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

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6ac937f213c08321.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6ac937f213c08321/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6ac937f213c08321/badge.svg)](https://brick.blue/agent/6ac937f213c08321?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.