Remote MCP · Endpoint

Signatoro MCP server

No. Signatoro answered an MCP handshake 40 minutes ago.

UpLast checked 40 minutes ago

Server URL

https://signatoro.com/mcp

The last check completed an MCP handshake.

Registry name
com.signatoro/signatoro
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
176 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
The agentic email signature platform: one saved signature for your people and your AI agents.
Listing
From the official MCP registry (active).
Recent checks of Signatoro
CheckedResultHandshake
40 minutes agoHandshake completed176 ms
3 days agoHandshake completed298 ms
12 days agoHandshake completed134 ms
12 days agoHandshake completed110 ms
14 days agoHandshake completed71 ms
15 days agoHandshake completed74 ms
16 days agoHandshake completed74 ms
17 days agoHandshake completed160 ms
18 days agoHandshake completed80 ms
19 days agoHandshake completed114 ms
22 days agoHandshake completed149 ms
25 days agoHandshake completed207 ms
27 days agoHandshake completed152 ms
29 days agoHandshake completed105 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.

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