pingen-mcp-server
Related Servers
Alternatives to pingen-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables sending physical letters (including registered mail) from PDFs via the Pingen API, with tools to manage drafts, submit, track, and cancel letters.918 npmMIT

DocuQueue MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables creating professional documents (invoices, contracts, certificates, proposals, reports) via the DocuQueue API, with tools for template management, filling, previewing, and PDF generation.28 npm1MIT- AlicenseNot gradedqualityBmaintenanceEnables authenticated management of email, drafts, sending, domains, contacts, templates, campaigns, workflows, and webhooks through typed MCP tools backed by a REST API.MIT
- FlicenseNot gradedqualityBmaintenanceEnables access to all DocuSign product APIs through curated tools and raw API calls, with OAuth support for hosted MCP clients.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to prepare, price, review, pay for, and send real physical letters and postcards via a hosted MCP server.-
- AlicenseBqualityDmaintenanceEnables sending transactional emails, managing templates, suppression lists, sending domains, webhooks, subaccounts, and retrieving account metrics via the SparkPost API.20356 npmMIT
TDQS
Scored across 49 tools
Each tool maps to a distinct REST endpoint and the resource prefix (letters, emails, ebills, batches, webhooks, organisations) plus action suffix usually makes selection clear. A few pairs need care — organisation-wide event feeds (organisations_letters_events_sent) versus per-letter events (letters_events), and files_file_upload which actually only fetches upload metadata rather than uploading anything.
All names are snake_case and mostly follow a resource_action shape, but the verb vocabulary is inconsistent (list vs index, show vs get, delete vs destroy, edit vs update) and the ordering flips between resource-first (letters_list) and path-first (organisations_letters_events_delivered, files_file_upload). Readable, but not predictable enough for an agent to guess names.
49 tools is well beyond a comfortable working set for an agent, even though it mirrors a real API surface of three delivery channels times roughly ten operations each. Much of the weight comes from repetitive per-channel variants (file, events, events_image, send, cancel) that could be consolidated.
CRUD plus lifecycle actions (send, cancel, file, events, statistics) are covered for letters, emails, ebills and batches, along with organisations, user, associations and webhooks. Minor gaps: no webhook update or webhook delivery/event listing, no letter or email edit operation, and no price calculator for channels other than letters.