Remote MCP · Endpoint

Pass-through tax rules MCP server

Yes, as of 4 days ago: the server returned an HTTP error.

DownLast checked 4 days ago

Server URL

https://passthroughtax.com/api/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.passthroughtax/pass-through-tax-rules
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
4 tools
Uptime, last 30 days
91.7% from 12 checks
Described by its publisher as
Cited, tax-year-dated rules for state PTET, the federal SALT cap, and bonus-depreciation conformity.
Listing
From the official MCP registry (active).
Recent checks of Pass-through tax rules
CheckedResultHandshake
4 days agoFailed - the server returned an HTTP error—
7 days agoHandshake completed106 ms
16 days agoHandshake completed729 ms
17 days agoHandshake completed710 ms
19 days agoHandshake completed178 ms
19 days agoHandshake completed100 ms
21 days agoHandshake completed143 ms
22 days agoHandshake completed141 ms
22 days agoHandshake completed266 ms
24 days agoHandshake completed175 ms
26 days agoHandshake completed281 ms
29 days agoHandshake completed147 ms

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

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 Pass-through tax rules and makes no claim about it beyond what these checks measured.