Remote MCP · Endpoint
Irs Afr MCP server
No. Irs Afr answered an MCP handshake 20 hours ago.
UpLast checked 20 hours ago
Server URL
https://gateway.pipeworx.io/irs-afr/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.pipeworx-io/irs-afr
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 40 ms
- Tools exposed
- 46 tools
- Uptime, last 30 days
- 100% from 11 checks
- Described by its publisher as
- IRS Applicable Federal Rates (AFR) and the Section 7520 rate.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 20 hours ago | Handshake completed | 40 ms |
| 5 days ago | Handshake completed | 112 ms |
| 8 days ago | Handshake completed | 68 ms |
| 17 days ago | Handshake completed | 1.74 s |
| 17 days ago | Handshake completed | 81 ms |
| 19 days ago | Handshake completed | 72 ms |
| 20 days ago | Handshake completed | 297 ms |
| 21 days ago | Handshake completed | 167 ms |
| 22 days ago | Handshake completed | 93 ms |
| 23 days ago | Handshake completed | 116 ms |
| 24 days ago | Handshake completed | 1.19 s |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.
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 Irs Afr and makes no claim about it beyond what these checks measured.