Remote MCP · Endpoint

SEFAZ RS: NFC-e (SVRS) MCP server

No. SEFAZ RS: NFC-e (SVRS) answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://api.mcp.ai/p_sefaz_rs_nfce_svrs

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/sefaz_rs_nfce_svrs-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.25 s
Tools exposed
7 tools
Uptime, last 30 days
83.3% from 18 checks
Described by its publisher as
SEFAZ RS: NFC-e (SVRS), official-source lookup. Platform-hosted, pay per query with prepaid credit.
Repository
https://github.com/mcp-dir/sefaz_rs_nfce_svrs-mcp
Listing
From the official MCP registry (active).
Recent checks of SEFAZ RS: NFC-e (SVRS)
CheckedResultHandshake
7 hours agoHandshake completed1.25 s
1 day agoHandshake completed168 ms
3 days agoFailed - the request timed out—
3 days agoHandshake completed45 ms
4 days agoHandshake completed71 ms
6 days agoHandshake completed59 ms
8 days agoHandshake completed219 ms
10 days agoHandshake completed40 ms
13 days agoFailed - the request timed out—
15 days agoHandshake completed78 ms
17 days agoHandshake completed203 ms
19 days agoHandshake completed75 ms
21 days agoHandshake completed47 ms
23 days agoFailed - the request timed out—
25 days agoHandshake completed56 ms
27 days agoHandshake completed3.76 s
28 days agoHandshake completed52 ms
29 days agoHandshake completed58 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 25 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.

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 SEFAZ RS: NFC-e (SVRS) and makes no claim about it beyond what these checks measured.