Remote MCP · Endpoint

Assinafy MCP server

No. Assinafy answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.assinafy.com.br/mcp

The last check completed an MCP handshake.

Registry name
io.github.assinafy/mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
105 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Send documents for legally valid e-signature in Brazil, track signers and download signed files.
Listing
From the official MCP registry (active).
Recent checks of Assinafy
CheckedResultHandshake
2 hours agoHandshake completed105 ms
2 days agoHandshake completed182 ms
4 days agoHandshake completed115 ms
6 days agoHandshake completed104 ms
8 days agoHandshake completed103 ms
9 days agoHandshake completed110 ms
11 days agoHandshake completed152 ms
11 days agoHandshake completed140 ms
14 days agoHandshake completed117 ms
15 days agoHandshake completed127 ms
17 days agoHandshake completed103 ms
19 days agoHandshake completed99 ms
20 days agoHandshake completed158 ms
21 days agoHandshake completed95 ms
22 days agoHandshake completed218 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 Assinafy and makes no claim about it beyond what these checks measured.