Is the Mcp Dir Zapsign MCP server down?

mcp-registry/io.github.mcp-dir/zapsign-mcp · v0.9.387

As of 2026-10-24 00:46 UTC, the Mcp Dir Zapsign MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 62 minutes.

ZapSign electronic document signing via the official API: create documents for signature (from PDF,

claude mcp add --transport http mcp-dir-zapsign-mcp-server https://api.mcp.ai/p_zapsign

{
  "mcpServers": {
    "mcp-dir-zapsign-mcp-server": {
      "type": "http",
      "url": "https://api.mcp.ai/p_zapsign"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (79/100)

What to fix (3)

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.mcp-dir/zapsign-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.mcp-dir/zapsign-mcp"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~6,640 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.15% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• marketplace ~570 tokens
• zapsign_documents_signer_log ~272 tokens
• zapsign_documents_list ~269 tokens
• zapsign_documents_get ~268 tokens
• zapsign_signers_write_add ~232 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mcp-dir%2Fzapsign-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.mcp-dir%2Fzapsign-mcp?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.mcp-dir%2Fzapsign-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mcp-dir%2Fzapsign-mcp.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mcp-dir%2Fzapsign-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.mcp-dir%2Fzapsign-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:244e7af2ffccd6c4…, first seen 2026-10-17, included at leaf 1380 of 55,658. Version history · verify what your client received.

Tools (35)

• authenticate
• connect
• marketplace
• report_bug
• show_version
• toolkit_info
• zapsign_account_plan
• zapsign_account_users
• zapsign_account_write_create_user
• zapsign_account_write_delete_user
• zapsign_checks_get
• zapsign_checks_write_create
• zapsign_documents_get
• zapsign_documents_list
• zapsign_documents_signer_log
• zapsign_documents_write_add_extra_doc
• zapsign_documents_write_create
• zapsign_documents_write_create_from_template
• zapsign_documents_write_delete
• zapsign_documents_write_place_signatures
• zapsign_documents_write_refuse
• zapsign_documents_write_update
• zapsign_list_accounts
• zapsign_signers_get
• zapsign_signers_write_add
• zapsign_signers_write_remove
• zapsign_signers_write_sign
• zapsign_signers_write_update
• zapsign_templates_get
• zapsign_templates_list
• zapsign_templates_write_create
• zapsign_templates_write_delete
• zapsign_templates_write_update
• zapsign_webhooks_write_create
• zapsign_webhooks_write_delete

Compare: most reliable security servers · most reliable marketplace servers · most reliable communication servers · most reliable other servers · most reliable knowledge servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Mcp Dir Zapsign MCP server down right now?

As of 2026-10-24 00:46 UTC, the Mcp Dir Zapsign MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 62 minutes.

How many tools does Mcp Dir Zapsign MCP server provide?

Mcp Dir Zapsign MCP server advertises 35 tools, including authenticate, connect, marketplace, report_bug, show_version.

How do I install Mcp Dir Zapsign MCP server?

Point your MCP client at this streamable-http endpoint: https://api.mcp.ai/p_zapsign

Is the Mcp Dir Zapsign MCP server safe to connect to an AI agent?

Glimind scanned all 35 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Mcp Dir Zapsign MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.