OKSign MCP by usefulapi
REMOTE · OKSIGN.USEFULAPI.IO
Read documents, signatures, contacts and credits; manage contacts and remove documents.
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.
- 2 Nov 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +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.
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- 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 functional
- 30 Oct 26 0
- Server version: 1.2.1 → 1.2.2 functional
- Server version: 1.2.0 → 1.2.1 functional
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.0 → 1.1.0 functional
- 28 Oct 26 62
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://oksign.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 oksign.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://oksign.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/oksign/ |
| http (plaintext) | http://oksign.usefulapi.io/mcp | Inconclusive | 302 | http://oksign.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 →
oksign_document_exists Check a document exists ~91
Whether a (signed) document still exists on the platform; returns its filename and whether it is a template. GET /v1/document/exists.
| Name | Type | Req | Description |
|---|---|---|---|
| docid | string | yes | OKsign document id (docid, source_docid or signed_docid) like 670816-483B7F54-8591-DDF9-FA77-9042AED3E8FD. |
No output schema declared.
No examples provided.
oksign_get_credits Get credits and storage ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
oksign_get_document_metadata Get signed document metadata ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| signed_docid | string | yes | OKsign document id (docid, source_docid or signed_docid) like 670816-483B7F54-8591-DDF9-FA77-9042AED3E8FD. |
No output schema declared.
No examples provided.
oksign_get_form_descriptor Get a document's form descriptor ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| docid | string | yes | OKsign document id (docid, source_docid or signed_docid) like 670816-483B7F54-8591-DDF9-FA77-9042AED3E8FD. |
No output schema declared.
No examples provided.
oksign_get_linked_document Find the source or signed copy of a document ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| docid | string | yes | OKsign document id (docid, source_docid or signed_docid) like 670816-483B7F54-8591-DDF9-FA77-9042AED3E8FD. |
No output schema declared.
No examples provided.
oksign_list_active_documents List active documents ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
oksign_list_contacts List contacts ~92
The account's contact list: name, email, mobile, actingas (capacity) and group. GET /v1/contacts/retrieve.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
oksign_list_email_templates List email templates ~96
The email templates defined in the account: id, name, subject, HTML body, reminder_days and repeat. GET /v1/email-templates/retrieve.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
oksign_list_notification_errors List email and SMS delivery errors ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | 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 | yes | Start of the window, ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
oksign_list_signed_documents List signed documents ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | 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 | yes | Start of the window, ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
oksign_list_users List users ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
oksign_remove_contacts Remove contacts ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | Contacts to remove (email and name). |
No output schema declared.
No examples provided.
oksign_remove_document Remove a document ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| docid | string | yes | OKsign document id (docid, source_docid or signed_docid) like 670816-483B7F54-8591-DDF9-FA77-9042AED3E8FD. |
No output schema declared.
No examples provided.
oksign_upsert_contacts Add or update contacts ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | Contacts to add or update. |
No output schema declared.
No examples provided.
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.
remote · oksign.usefulapi.io
claude mcp add --transport http io-usefulapi-oksign 'https://oksign.usefulapi.io/mcp'
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.