SignNow API Helper MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_signnow_api_infoB | Get information about SignNow API. This is documentation for API usage. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool clearly describes its purpose of retrieving SignNow API documentation.
The single tool follows a consistent verb_noun naming convention (get_signnow_api_info), which is clear and predictable.
With only one tool serving as documentation, the server feels extremely thin for the stated purpose. A single trivial tool is at the extreme low end of the scale.
The server provides only documentation and no actual API interaction tools, leaving significant gaps for any real SignNow workflow (e.g., document creation, signing, etc.). It is severely incomplete as an API helper.