Remote MCP · Endpoint

NotaMCP MCP server

No. NotaMCP answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://notamcp.com.br/mcp

The last check completed an MCP handshake.

Registry name
io.github.CssEoCAO/notamcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
692 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Issue Brazilian service invoices (NFS-e Nacional) from your AI, with preview and confirmation.
Listing
From the official MCP registry (active).
Recent checks of NotaMCP
CheckedResultHandshake
3 hours agoHandshake completed692 ms
4 days agoHandshake completed305 ms
14 days agoHandshake completed260 ms
15 days agoHandshake completed334 ms
15 days agoHandshake completed359 ms
17 days agoHandshake completed457 ms
18 days agoHandshake completed730 ms
19 days agoHandshake completed286 ms
20 days agoHandshake completed281 ms
21 days agoHandshake completed353 ms
23 days agoHandshake completed686 ms

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