# OKSign MCP by usefulapi (remote · oksign.usefulapi.io)

Read documents, signatures, contacts and credits; manage contacts and remove documents.

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

## Components

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

## Channel facts

- Endpoint: `https://oksign.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.8.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 OKSign MCP by usefulapi server?

OKSign MCP by usefulapi is a hosted endpoint at https://oksign.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-oksign 'https://oksign.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-oksign": {
      "type": "http",
      "url": "https://oksign.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-02 (score 18, −49)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [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-11-01 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 66, +3)

- [security improvement] Authorization: partial → pass
- [functional improvement] MCP protocol: fail → pass
- [functional] New prompt “add_or_update_signing_contacts”
- [functional] New prompt “review_delivery_errors_and_account_credits”
- [functional] New prompt “review_documents_awaiting_signatures”
- [functional] New prompt “review_recently_signed_documents”
- [functional] MCP protocol version: 2025-06-18 → 2025-11-25
- [functional] Server version: 1.4.0 → 1.6.0
- [functional] Server version: 1.3.0 → 1.4.0
- [functional] Server version: 1.2.2 → 1.3.0

### 2026-10-30 (score 63, 0)

- [functional] Server version: 1.2.1 → 1.2.2
- [functional] Server version: 1.2.0 → 1.2.1

### 2026-10-29 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-28 (score 62)

First indexed and scored.

## MCP tools (14)

### `oksign_get_credits` (~63 tokens)

Get credits and storage

The account's remaining credits (quantity), when they expire (validuntil), the plan (subscription), whether it is paid, and storage used (account_size) versus the maximum (max_account_size) in bytes. GET /v1/credits/retrieve.

### `oksign_list_users` (~103 tokens)

List users

The users of the OKsign account: name, email, mobile, role, status, language and the immutable signerid (use it to tell who signed). GET /v1/users/retrieve.

Input parameters:

- `limit` (integer): Items to return, 1-500 (default 100). OKsign has no paging; the list is cut here.
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.

### `oksign_list_email_templates` (~96 tokens)

List email templates

The email templates defined in the account: id, name, subject, HTML body, reminder_days and repeat. GET /v1/email-templates/retrieve.

Input parameters:

- `limit` (integer): Items to return, 1-500 (default 100). OKsign has no paging; the list is cut here.
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.

### `oksign_list_contacts` (~92 tokens)

List contacts

The account's contact list: name, email, mobile, actingas (capacity) and group. GET /v1/contacts/retrieve.

Input parameters:

- `limit` (integer): Items to return, 1-500 (default 100). OKsign has no paging; the list is cut here.
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.

### `oksign_list_active_documents` (~206 tokens)

List active documents

Documents in the account's Active Documents tab: docid, filename, creator, createdate, signatures required/valid, orgtoken, status (1 active, 10 briefcase, 11 document in a briefcase, 12 reusable, 14 template), viaapi and signed_docid when signed. OKsign allows this call only once every 3 minutes (429 otherwise). GET /v1/documents/active.

Input parameters:

- `filename_contains` (string): Only documents whose filename contains this text (case-insensitive).
- `limit` (integer): Items to return, 1-500 (default 100). OKsign has no paging; the list is cut here.
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `orgtoken` (string): Only documents uploaded with this organizational token.
- `signed` (boolean): true = only documents that have a signed copy, false = only those without.

### `oksign_list_signed_documents` (~171 tokens)

List signed documents

Documents uploaded through the API that were signed between two moments: signed_docid, source_docid, filename, signerid, signing source, signature counts, completed fields, credits per signer and timestamp. Keep the window short; OKsign allows this call only once every 3 minutes (429 otherwise). GET /v1/documents/signed.

Input parameters:

- `end` (string, required): End of the window, ISO 8601 with a timezone.
- `limit` (integer): Items to return, 1-500 (default 100). OKsign has no paging; the list is cut here.
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `start` (string, required): Start of the window, ISO 8601 with a timezone.

### `oksign_list_notification_errors` (~176 tokens)

List email and SMS delivery errors

Email and SMS delivery problems (hard_bounce, soft_bounce, blocked, spam, invalid_email, deferred) for signing invitations sent between two moments: recipient, source_docid, reason, orgtoken and timestamp. Only error events are reported. OKsign allows this call only once every 3 minutes (429 otherwise). GET /v1/webhooks/retrieve.

Input parameters:

- `end` (string, required): End of the window, ISO 8601 with a timezone.
- `limit` (integer): Items to return, 1-500 (default 100). OKsign has no paging; the list is cut here.
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `start` (string, required): Start of the window, ISO 8601 with a timezone.

### `oksign_document_exists` (~91 tokens)

Check a document exists

Whether a (signed) document still exists on the platform; returns its filename and whether it is a template. GET /v1/document/exists.

Input parameters:

- `docid` (string, required): OKsign document id (docid, source_docid or signed_docid) like 670816-483B7F54-8591-DDF9-FA77-9042AED3E8FD.

### `oksign_get_document_metadata` (~113 tokens)

Get signed document metadata

Metadata of a signed document (pass the signed_docid): filename, size, signatures required/valid, who signed, and the values of all completed fields (can contain personal data). Metadata v2. GET /v2/metadata/retrieve.

Input parameters:

- `signed_docid` (string, required): OKsign document id (docid, source_docid or signed_docid) like 670816-483B7F54-8591-DDF9-FA77-9042AED3E8FD.

### `oksign_get_form_descriptor` (~121 tokens)

Get a document's form descriptor

The form descriptor of an uploaded document: its signature and form fields (type, page, position, signer, required, signing options) and the signing URL of each signer. The URLs let their holders sign, so share them only with the signer. GET /v1/formdesc/retrieve.

Input parameters:

- `docid` (string, required): OKsign document id (docid, source_docid or signed_docid) like 670816-483B7F54-8591-DDF9-FA77-9042AED3E8FD.

### `oksign_get_linked_document` (~123 tokens)

Find the source or signed copy of a document

Given a source_docid, the signed_docid of its signed copy (absent if not signed yet) and the timestamp; given a signed_docid, the source_docid. An empty result means the document never existed here or was removed. GET /v1/linkedlist/retrieve.

Input parameters:

- `docid` (string, required): OKsign document id (docid, source_docid or signed_docid) like 670816-483B7F54-8591-DDF9-FA77-9042AED3E8FD.

### `oksign_upsert_contacts` (~77 tokens)

Add or update contacts

WRITE: add contacts to the account's contact list, or update them when a contact with the same email AND name exists (its other fields are replaced). Existing contacts are never cleared. Contacts OKsign rejects are skipped and reported. POST /v1/contacts/upload.

Input parameters:

- `contacts` (array, required): Contacts to add or update.

### `oksign_remove_contacts` (~67 tokens)

Remove contacts

WRITE: permanently remove contacts from the account's contact list. A contact is identified by its email AND name. Cannot be undone (re-add with oksign_upsert_contacts). POST /v1/contacts/remove.

Input parameters:

- `contacts` (array, required): Contacts to remove (email and name).

### `oksign_remove_document` (~114 tokens)

Remove a document

WRITE: permanently remove a (signed) document from the OKsign platform. This deletes the file and its pending webhook events and cannot be undone. A signed document removed right after its callback may answer 'Too soon': retry later. DELETE /v1/document/remove.

Input parameters:

- `docid` (string, required): OKsign document id (docid, source_docid or signed_docid) like 670816-483B7F54-8591-DDF9-FA77-9042AED3E8FD.

## Diagnostics

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

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 67
- 2026-10-31: 66
- 2026-10-30: 63
- 2026-10-29: 63
- 2026-10-28: 62

## Common questions

### What is the OKSign MCP by usefulapi server?

OKSign MCP by usefulapi is listed in the public MCP registry as io.usefulapi/oksign. Read documents, signatures, contacts and credits; manage contacts and remove documents. This page covers its hosted endpoint (https://oksign.usefulapi.io/mcp).

### Is the OKSign MCP by usefulapi server safe to use?

OKSign 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 OKSign MCP by usefulapi server expose?

OKSign MCP by usefulapi exposes 14 tools: oksign_get_credits, oksign_list_users, oksign_list_email_templates, oksign_list_contacts, oksign_list_active_documents, and 9 more. Their descriptions and schemas cost roughly 1,613 tokens of context every time the server is loaded.

### Does the OKSign MCP by usefulapi server require authentication?

Its publisher declares no required credentials for OKSign 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 OKSign MCP by usefulapi server still maintained?

OKSign 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 OKSign MCP by usefulapi server?

VerifyMCP ran 4 checks on OKSign 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 OKSign 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://oksign.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/oksign/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-oksign/oksign.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-oksign/oksign/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-oksign/oksign.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-oksign/oksign