mcpbeat Sign in

Getsign MCP Server

answering

Getsign MCP is answering right now. Last checked 4 min ago.

Send, track, and complete e-signature workflows on monday.com boards.

Uptime history 53 days of history · worst day 93%
53 days agonow
98.9%
Uptime 24h
90 of 91 checks
—
Tools
hidden behind auth
485 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Getsign MCP missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add getsign-mcp --transport http https://mcp.getsign.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.getsign.io/mcp
~/.codex/config.toml
[mcp_servers.getsign-mcp]
url = "https://mcp.getsign.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "getsign-mcp": {
      "url": "https://mcp.getsign.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "getsign-mcp": {
      "type": "http",
      "url": "https://mcp.getsign.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.getsign.io/mcp streamable-http sign-in 448 ms 4 min ago

Alternatives to Getsign MCP

same job, measured the same way
DottedSign
by dottedsign-official

Automate eSignature workflows and signing tasks via natural language commands.

answering
n8n MCP Server
by rpgmais

The most complete MCP server for n8n — 43 tools for workflows, data tables, and more.

47 installs/wk local only
Okdoc
by okdocai

E-signature & document automation: create, send, track and sign documents with payments. 38 tools.

answering
Volanea
by pankaj-bit361

Email infrastructure on Volanea: build templates, segments and workflows, send and check email.

27 tools answering
Proletariat CLI
by chrismcdermut

Agent orchestration platform - multi-agent spawning, tickets, boards, and workflows

462 installs/wk local only
Ami Survey
by speedofred

Measures the cost, tokens and duration of a completed agent workflow from its session log.

73 installs/wk local only
SignNow MCP Server
by signnow

A MCP server that gives AI agents access to SignNow eSignature workflows over STDIO.

313 installs/wk local only
Source Parts
by sourceparts

Electronic component sourcing, BOM management, and PCB design workflows.

188 installs/wk answering

Getsign MCP — questions

Answers built from our own checks of this server.

Why is there no tool list for Getsign MCP?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 98.9% of checks in the last 24 hours got a reply.
Is Getsign MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 485 ms. The bar chart above shows every period we have measured.
How do I connect Getsign MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Getsign MCP?
No API key is involved. Getsign MCP answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Getsign MCP?
It answers our handshake in 485 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.