Remote MCP · Endpoint
SEFAZ RS: NFC-e Resumida MCP server
No. SEFAZ RS: NFC-e Resumida answered an MCP handshake 5 hours ago.
UpLast checked 5 hours ago
Server URL
https://api.mcp.ai/p_sefaz_rs_nfce_resumida
The last check completed an MCP handshake.
- Registry name
- io.github.mcp-dir/sefaz_rs_nfce_resumida-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.24 s
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 88.9% from 18 checks
- Described by its publisher as
- SEFAZ RS: NFC-e Resumida, official-source lookup. Platform-hosted, pay per query with prepaid credit
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Handshake completed | 1.24 s |
| 1 day ago | Handshake completed | 180 ms |
| 3 days ago | Failed - the request timed out | — |
| 3 days ago | Handshake completed | 56 ms |
| 4 days ago | Handshake completed | 83 ms |
| 6 days ago | Handshake completed | 103 ms |
| 8 days ago | Handshake completed | 57 ms |
| 10 days ago | Handshake completed | 47 ms |
| 13 days ago | Handshake completed | 288 ms |
| 15 days ago | Handshake completed | 95 ms |
| 17 days ago | Handshake completed | 252 ms |
| 19 days ago | Handshake completed | 47 ms |
| 21 days ago | Handshake completed | 45 ms |
| 23 days ago | Failed - the request timed out | — |
| 25 days ago | Handshake completed | 69 ms |
| 27 days ago | Handshake completed | 3.92 s |
| 28 days ago | Handshake completed | 41 ms |
| 29 days ago | Handshake completed | 63 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 28.
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 SEFAZ RS: NFC-e Resumida and makes no claim about it beyond what these checks measured.