Remote MCP · Endpoint

Untax MCP server

No. Untax answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://untax.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.mooshee/untax
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
448 ms
Tools exposed
81 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Research county property assessments and prepare draft comparisons. (mooshworks.com)
Website
https://untax.io/
Repository
https://github.com/mooshee/untax-mcp
Listing
From the official MCP registry (active).
Recent checks of Untax
CheckedResultHandshake
1 hour agoHandshake completed448 ms
9 days agoHandshake completed119 ms
10 days agoHandshake completed158 ms
11 days agoHandshake completed111 ms
12 days agoHandshake completed86 ms
14 days agoHandshake completed163 ms
14 days agoHandshake completed112 ms
15 days agoHandshake completed91 ms
17 days agoHandshake completed112 ms
19 days agoHandshake completed138 ms
21 days agoHandshake completed99 ms
24 days agoHandshake completed108 ms
26 days agoHandshake completed69 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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