Remote MCP · Endpoint

ITINAgents MCP server

No. ITINAgents answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://itinagents.fyi/mcp

The last check completed an MCP handshake.

Registry name
fyi.itinagents/itinagents
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
463 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
9,838 IRS acceptance agents across US, CA, GB and IN.
Listing
From the official MCP registry (active).
Recent checks of ITINAgents
CheckedResultHandshake
2 hours agoHandshake completed463 ms
1 day agoHandshake completed176 ms
3 days agoHandshake completed75 ms
3 days agoHandshake completed510 ms
4 days agoHandshake completed76 ms
5 days agoHandshake completed62 ms
7 days agoHandshake completed212 ms
10 days agoHandshake completed159 ms
12 days agoHandshake completed75 ms
15 days agoHandshake completed1.37 s
17 days agoHandshake completed297 ms
19 days agoHandshake completed137 ms
21 days agoHandshake completed270 ms
23 days agoHandshake completed179 ms
25 days agoHandshake completed167 ms

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

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