# Stiply MCP by usefulapi (remote · stiply.usefulapi.io)

Read sign requests and signers; send, remind, extend and cancel sign requests in Stiply.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `stiply.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-stiply/stiply.md), [page](https://verifymcp.io/servers/io-usefulapi-stiply/stiply)

## Channel facts

- Endpoint: `https://stiply.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-stiply 'https://stiply.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-stiply": {
      "url": "https://stiply.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-stiply": {
      "type": "http",
      "url": "https://stiply.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-stiply]
url = "https://stiply.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-stiply": {
      "type": "remote",
      "url": "https://stiply.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-stiply --url 'https://stiply.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-stiply:
    url: "https://stiply.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-stiply": {
      "Transport": "http",
      "Url": "https://stiply.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-stiply -t streamable-http -u 'https://stiply.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-stiply": {
      "type": "http",
      "url": "https://stiply.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 18, −47)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 65)

First indexed and scored.

## MCP tools (10)

### `stiply_list_sign_requests` (~136 tokens)

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.

Input parameters:

- `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.

### `stiply_get_sign_request` (~63 tokens)

Get a sign request

Get one sign request by id: status, timestamps, message, reject reason, owner. Stiply API: GET /v2/sign_requests/{id}.

Input parameters:

- `sign_request_id` (integer, required): The sign request id (from stiply_list_sign_requests).

### `stiply_get_sign_request_by_external_key` (~59 tokens)

Get 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}.

Input parameters:

- `external_key` (string, required): The external key given at creation.

### `stiply_get_sign_request_progress` (~77 tokens)

Get 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.

Input parameters:

- `sign_request_id` (integer, required): The sign request id (from stiply_list_sign_requests).

### `stiply_list_signers` (~79 tokens)

List 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.

Input parameters:

- `sign_request_id` (integer, required): The sign request id (from stiply_list_sign_requests).

### `stiply_list_documents` (~62 tokens)

List 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.

Input parameters:

- `sign_request_id` (integer, required): The sign request id (from stiply_list_sign_requests).

### `stiply_create_sign_request` (~194 tokens)

Create 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.

Input parameters:

- `external_key` (string): Your own unique key to find this request later.
- `file_urls` (array, required): Public https URLs of the PDF documents to sign.
- `message` (string): Email message. Basic HTML only; use <br> for newlines.
- `signers` (array, required): 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, required): Title of the sign request.

### `stiply_send_reminder` (~65 tokens)

Send a reminder

WRITE: email a reminder to the signers who have not signed yet. Stiply API: POST /v2/sign_requests/{id}/actions/send_reminder.

Input parameters:

- `sign_request_id` (integer, required): The sign request id (from stiply_list_sign_requests).

### `stiply_extend_term` (~100 tokens)

Extend the term

WRITE: extend the signing term of a sign request. Stiply API: POST /v2/sign_requests/{id}/actions/extend_term.

Input parameters:

- `notify_signers` (boolean): Tell the signers (default true).
- `sign_request_id` (integer, required): The sign request id (from stiply_list_sign_requests).
- `term` (string, required): New term, e.g. 1d, 2w, 3m.

### `stiply_cancel_sign_request` (~93 tokens)

Cancel a sign request

WRITE: cancel a sign request. This cannot be undone. Stiply API: POST /v2/sign_requests/{id}/actions/cancel.

Input parameters:

- `cancellation_message` (string): Optional message shown to the signers.
- `notify_signers` (boolean, required): Whether the signers get a cancellation email.
- `sign_request_id` (integer, required): The sign request id (from stiply_list_sign_requests).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-stiply/stiply#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 18
- 2026-10-31: 65

## Common questions

### 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.

## Links

- Remote endpoint: https://stiply.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/stiply/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-stiply/stiply.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-stiply/stiply/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-stiply/stiply.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-stiply/stiply