Remote MCP · Endpoint

Terminal Tax MCP server

No. Terminal Tax answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://mcp.terminal.tax/v1/hosted-mcp

The last check completed an MCP handshake.

Registry name
tax.terminal/filing
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
151 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Tax software: your AI agent sends the facts, we calculate and e-file; you review and sign.
Listing
From the official MCP registry (active).
Recent checks of Terminal Tax
CheckedResultHandshake
57 minutes agoHandshake completed151 ms
3 days agoHandshake completed159 ms
12 days agoHandshake completed138 ms
13 days agoHandshake completed1.90 s
15 days agoHandshake completed154 ms
15 days agoHandshake completed158 ms
17 days agoHandshake completed465 ms
18 days agoHandshake completed1.65 s
18 days agoHandshake completed162 ms
20 days agoHandshake completed147 ms
22 days agoHandshake completed55 ms
25 days agoHandshake completed63 ms
27 days agoHandshake completed134 ms
29 days agoHandshake completed132 ms

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

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 Terminal Tax and makes no claim about it beyond what these checks measured.