io.usefulapiPublished by usefulapi.ioOfficial publisherv1.6.4Updated Nov 7, 2026
Read sign requests and signers; send, remind, extend and cancel sign requests in Stiply.
The publisher's own server: Ably MCP by usefulapi
Hosted MCP server for Stiply e-signing: read sign requests, signers and audit trails, and send, remind, extend or cancel them.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.usefulapi%2Fstiply/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"stiply-by-usefulapi": {
"type": "http",
"url": "https://stiply.usefulapi.io/mcp"
}
}
}Use your Stiply account from Claude, Cursor, or any MCP client. Read sign requests, signers and audit trails, and send, remind, extend or cancel sign requests. Hosted, no local install: connect with your own credentials.
Live endpoint: https://stiply.usefulapi.io/mcp · Homepage: https://usefulapi.io
https://stiply.usefulapi.io/mcp.claude mcp add --transport http stiply https://stiply.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Stiply credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/stiply/
On first connect you provide a Stiply Personal Access Token (Stiply → Settings → API). The server validates it and stores it per user. No keys go in config files.
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with stiply_upgrade (it returns a Stripe Checkout link). Cancel any time with stiply_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running stiply_upgrade before then undoes the cancel. Or write to [email protected].
MIT — see LICENSE. Documentation only; the server is hosted.
Source: servers/stiply/README.md at commit 4046075
List sign requests
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.
pagestatusorderbypage_sizeGet a sign request
Get one sign request by id: status, timestamps, message, reject reason, owner. Stiply API: GET /v2/sign_requests/{id}.
sign_request_idrequiredGet a sign request by external key
Find a sign request by the external_key set when it was created. Stiply API: GET /v2/sign_requests/by_key/{external_key}.
external_keyrequiredGet sign request progress
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.
sign_request_idrequiredList signers
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.
sign_request_idrequiredList documents of a sign request
List the documents attached to a sign request (metadata only, no file download). Stiply API: GET /v2/sign_requests/{id}/documents.
sign_request_idrequiredCreate and send a sign request
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.
termtitlerequiredmessagesignersrequiredsubjectfile_urlsrequiredexternal_keysigning_sequence_typeSend a reminder
WRITE: email a reminder to the signers who have not signed yet. Stiply API: POST /v2/sign_requests/{id}/actions/send_reminder.
sign_request_idrequiredExtend the term
WRITE: extend the signing term of a sign request. Stiply API: POST /v2/sign_requests/{id}/actions/extend_term.
termrequirednotify_signerssign_request_idrequiredCancel a sign request
WRITE: cancel a sign request. This cannot be undone. Stiply API: POST /v2/sign_requests/{id}/actions/cancel.
notify_signersrequiredsign_request_idrequiredcancellation_message100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
io.usefulapiOfficial publisher
Hosted MCP server for Ably realtime messaging: inspect channel history, presence and occupancy, publish messages, and review app usage and configuration.
io.usefulapiOfficial publisher
Hosted read-only MCP server that lets an assistant look up Woffu company users, employment contracts, departments and offices.
io.usefulapiOfficial publisher
Hosted MCP server for White Label Loyalty: browse rewards, read a customer's points wallet and tier progress, and buy rewards with points.
io.usefulapiOfficial publisher
Hosted Weekdone connector that lets an assistant read weekly reports, teams, objectives and KPIs, and add report items, comments and KPI values.
io.usefulapiOfficial publisher
Hosted read-only MCP server that lets an assistant list WebinarKit webinars, their dates, series, meetings and white-label sub-accounts.
{ "mcpServers": { "stiply": { "url": "https://stiply.usefulapi.io/mcp" } }}