Home / MCP registry index / ca.swiftsign/mcp
ca.swiftsign/mcp
ca.swiftsign/mcp in the official MCP registry.
Endpoint https://swiftsign.ca/mcp. Source: github.com/shahdadk/swiftsign.
The registry describes it as: E-signatures for agents: mint a sandbox key, send PDFs, track status, download the sealed result.
We read its 10 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
swiftsign_send_envelope swiftsign_confirm_send swiftsign_send_from_template swiftsign_check_status swiftsign_list_envelopes swiftsign_void_envelope swiftsign_download_signed_pdf swiftsign_upgrade swiftsign_create_embedded_url swiftsign_list_templates
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ca-swiftsign-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.