Stiply MCP by usefulapi
REMOTE · STIPLY.USEFULAPI.IO
Read sign requests and signers; send, remind, extend and cancel sign requests in Stiply.
Available components
Last scanned (4 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://stiply.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of stiply.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stiply.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/stiply/ |
| http (plaintext) | http://stiply.usefulapi.io/mcp | Inconclusive | 302 | http://stiply.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
stiply_cancel_sign_request Cancel a sign request ~93
WRITE: cancel a sign request. This cannot be undone. Stiply API: POST /v2/sign_requests/{id}/actions/cancel.
| Name | Type | Req | Description |
|---|---|---|---|
| cancellation_message | string | – | Optional message shown to the signers. |
| notify_signers | boolean | yes | Whether the signers get a cancellation email. |
| sign_request_id | integer | yes | The sign request id (from stiply_list_sign_requests). |
No output schema declared.
No examples provided.
stiply_create_sign_request Create and send a sign request ~194
WRITE: create a sign request and SEND it. Stiply downloads each PDF from file_urls and emails the signers at once, so confirm the signers with the user first. Stiply API: POST /v2/sign_requests.
| Name | Type | Req | Description |
|---|---|---|---|
| external_key | string | – | Your own unique key to find this request later. |
| file_urls | array | yes | Public https URLs of the PDF documents to sign. |
| message | string | – | Email message. Basic HTML only; use <br> for newlines. |
| signers | array | yes | Who receives the request. |
| signing_sequence_type | string | – | – |
| subject | string | – | Email subject for the signers. |
| term | string | – | How long signers have, e.g. 1d, 2w, 3m. Default: the account setting. |
| title | string | yes | Title of the sign request. |
No output schema declared.
No examples provided.
stiply_extend_term Extend the term ~100
WRITE: extend the signing term of a sign request. Stiply API: POST /v2/sign_requests/{id}/actions/extend_term.
| Name | Type | Req | Description |
|---|---|---|---|
| notify_signers | boolean | – | Tell the signers (default true). |
| sign_request_id | integer | yes | The sign request id (from stiply_list_sign_requests). |
| term | string | yes | New term, e.g. 1d, 2w, 3m. |
No output schema declared.
No examples provided.
stiply_get_sign_request Get a sign request ~63
Get one sign request by id: status, timestamps, message, reject reason, owner. Stiply API: GET /v2/sign_requests/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| sign_request_id | integer | yes | The sign request id (from stiply_list_sign_requests). |
No output schema declared.
No examples provided.
stiply_get_sign_request_by_external_key Get a sign request by external key ~59
Find a sign request by the external_key set when it was created. Stiply API: GET /v2/sign_requests/by_key/{external_key}.
| Name | Type | Req | Description |
|---|---|---|---|
| external_key | string | yes | The external key given at creation. |
No output schema declared.
No examples provided.
stiply_get_sign_request_progress Get sign request progress ~77
Get the audit trail of a sign request: each action (sent, opened, signed, ...) with time, IP, location and email status. Stiply API: GET /v2/sign_requests/{id}/progress.
| Name | Type | Req | Description |
|---|---|---|---|
| sign_request_id | integer | yes | The sign request id (from stiply_list_sign_requests). |
No output schema declared.
No examples provided.
stiply_list_documents List documents of a sign request ~62
List the documents attached to a sign request (metadata only, no file download). Stiply API: GET /v2/sign_requests/{id}/documents.
| Name | Type | Req | Description |
|---|---|---|---|
| sign_request_id | integer | yes | The sign request id (from stiply_list_sign_requests). |
No output schema declared.
No examples provided.
stiply_list_sign_requests List sign requests ~136
List sign requests (documents sent for e-signing) with status, title, sent/expiry/signed timestamps. Filter by status (draft, published, all_signed, completed, rejected, canceled, expired, ...). Stiply API: GET /v2/sign_requests.
| Name | Type | Req | Description |
|---|---|---|---|
| orderby | string | – | Sort order, e.g. 'created_at desc'. |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (max 100). |
| status | string | – | Filter by status, e.g. published, completed, rejected, canceled, expired. |
No output schema declared.
No examples provided.
stiply_list_signers List signers ~79
List the signers of a sign request with email, name, role (signer/approver/cc/dc), authentication method and sign URL. Stiply API: GET /v2/sign_requests/{id}/signers.
| Name | Type | Req | Description |
|---|---|---|---|
| sign_request_id | integer | yes | The sign request id (from stiply_list_sign_requests). |
No output schema declared.
No examples provided.
stiply_send_reminder Send a reminder ~65
WRITE: email a reminder to the signers who have not signed yet. Stiply API: POST /v2/sign_requests/{id}/actions/send_reminder.
| Name | Type | Req | Description |
|---|---|---|---|
| sign_request_id | integer | yes | The sign request id (from stiply_list_sign_requests). |
No output schema declared.
No examples provided.
How do I install the Stiply MCP by usefulapi server?
Stiply MCP by usefulapi is a hosted endpoint at https://stiply.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · stiply.usefulapi.io
claude mcp add --transport http io-usefulapi-stiply 'https://stiply.usefulapi.io/mcp'
What is the Stiply MCP by usefulapi server?
Stiply MCP by usefulapi is listed in the public MCP registry as io.usefulapi/stiply. Read sign requests and signers; send, remind, extend and cancel sign requests in Stiply. This page covers its hosted endpoint (https://stiply.usefulapi.io/mcp).
Is the Stiply MCP by usefulapi server safe to use?
Stiply MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Stiply MCP by usefulapi server expose?
Stiply MCP by usefulapi exposes 10 tools: stiply_list_sign_requests, stiply_get_sign_request, stiply_get_sign_request_by_external_key, stiply_get_sign_request_progress, stiply_list_signers, and 5 more. Their descriptions and schemas cost roughly 928 tokens of context every time the server is loaded.
Does the Stiply MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Stiply MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Stiply MCP by usefulapi server still maintained?
Stiply MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Stiply MCP by usefulapi server?
VerifyMCP ran 4 checks on Stiply MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Stiply MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.