# Assinafy (remote · mcp.assinafy.com.br)

Send documents for legally valid e-signature in Brazil, track signers and download signed files.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `mcp.assinafy.com.br`: 66/100 (this document), [markdown](https://verifymcp.io/servers/assinafy-mcp-server/mcp.md), [page](https://verifymcp.io/servers/assinafy-mcp-server/mcp)

## Channel facts

- Endpoint: `https://mcp.assinafy.com.br/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.0.7`

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

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: this server exposes a tool marked destructive (assinafy_delete_document) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1331 tokens (~121/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Assinafy MCP server?

Assinafy is a hosted endpoint at https://mcp.assinafy.com.br/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 assinafy-mcp-server 'https://mcp.assinafy.com.br/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "assinafy-mcp-server": {
      "url": "https://mcp.assinafy.com.br/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "assinafy-mcp-server": {
      "type": "http",
      "url": "https://mcp.assinafy.com.br/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.assinafy-mcp-server]
url = "https://mcp.assinafy.com.br/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "assinafy-mcp-server": {
      "type": "remote",
      "url": "https://mcp.assinafy.com.br/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add assinafy-mcp-server --url 'https://mcp.assinafy.com.br/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  assinafy-mcp-server:
    url: "https://mcp.assinafy.com.br/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "assinafy-mcp-server": {
      "Transport": "http",
      "Url": "https://mcp.assinafy.com.br/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add assinafy-mcp-server -t streamable-http -u 'https://mcp.assinafy.com.br/mcp'
```

### Other

```json
{
  "mcpServers": {
    "assinafy-mcp-server": {
      "type": "http",
      "url": "https://mcp.assinafy.com.br/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-09-28 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 66, +1)

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

### 2026-09-26 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-25 (score 65)

First indexed and scored.

## MCP tools (11)

### `assinafy_check_fields` (~78 tokens)

Find and validate fields

Prepare template values or collect field placements. list finds reusable definitions; get inspects one field; validate checks values without creating a document. Match definitions to template placement field_id, ask about ambiguous names, and check each validation result's success before requesting signatures.

Input parameters:

- `action` (string, required): Choose exactly one action; supply only its arguments.

### `assinafy_delete_document` (~54 tokens)

Delete a document

Delete a document only when the user's instruction explicitly authorizes deletion. Inspect its current state first; Assinafy enforces which documents may be deleted.

Input parameters:

- `document_id` (string, required): unique document ID to delete

### `assinafy_download_document` (~83 tokens)

Download a document or page

Retrieve bytes only when needed. artifact downloads original (default), certificated, certificate-page, pades or bundle; wait for certificated status and artifact availability before downloading the signed PDF. page downloads a preview using a page_id returned by find_documents. Results contain base64 bytes.

Input parameters:

- `action` (string, required): Choose exactly one action; supply only its arguments.

### `assinafy_find_documents` (~86 tokens)

Find and inspect documents

Find a document or check signing progress. Use list to search; get to inspect status, assignment, signer IDs and artifacts; activities for the event timeline; notifications for WhatsApp delivery history. Read before retrying a send or following up. 100% signatures does not mean certification is finished.

Input parameters:

- `action` (string, required): Choose exactly one action; supply only its arguments.

### `assinafy_find_signers` (~62 tokens)

Find signers

Resolve a recipient to a workspace signer ID. list searches the directory; get inspects a known signer. Check exact contact details and ask about ambiguous matches before sending invitations.

Input parameters:

- `action` (string, required): Choose exactly one action; supply only its arguments.

### `assinafy_find_templates` (~74 tokens)

Find saved templates

Discover saved templates before requesting signatures. list returns roles, pages, field_id and placement labels; get inspects one template where the compatibility endpoint is supported. Match field names with check_fields. Template authoring stays in Assinafy.

Input parameters:

- `action` (string, required): Choose exactly one action; supply only its arguments.

### `assinafy_follow_up_assignment` (~88 tokens)

Follow up on signatures

Follow up on an existing assignment after checking find_documents. resend sends a reminder to one authorized pending signer and may consume notification credits. set_expiration changes the expiry using an explicit RFC 3339 timestamp. Use returned document, assignment and signer IDs; never repeat a reminder just because progress is unchanged.

Input parameters:

- `action` (string, required): Choose exactly one action; supply only its arguments.

### `assinafy_prepare_document` (~69 tokens)

Prepare a document

Prepare a PDF before requesting signatures. upload accepts PDF bytes and returns a document ID without invitations. rename changes a document's name before an assignment exists. Continue with find_documents and request_signatures action from_document.

Input parameters:

- `action` (string, required): Choose exactly one action; supply only its arguments.

### `assinafy_request_signatures` (~134 tokens)

Request signatures

Send a document for signature using exactly one source. from_pdf uploads new PDF bytes, waits for processing and creates or reuses email signers. from_document uses an existing document_id and signer IDs; inspect the document first and do not repeat an existing assignment. from_template generates a document and assignment from a saved template; discover roles and field IDs first. These actions send invitations and can consume credits: use recipients authorized by the user. After a partial failure, inspect the retained document ID and continue from_document instead of uploading again.

Input parameters:

- `action` (string, required): Choose exactly one action; supply only its arguments.

### `assinafy_save_signer` (~85 tokens)

Save signer contact details

create adds a workspace contact without sending invitations; find_signers first to avoid duplicates. update corrects a shared contact subject to Assinafy's verification restrictions. Changing an unverified channel invalidates old links; follow up only after the correction succeeds and the user has authorized a reminder.

Input parameters:

- `action` (string, required): Choose exactly one action; supply only its arguments.

### `assinafy_verify_document` (~56 tokens)

Verify a signed document

Verify a signed document using its actual Assinafy SHA-1 signature hash. Public lookup; requires no workspace connection and sends no credential upstream.

Input parameters:

- `hash` (string, required): SHA-1 signature hash of the signed document

## Diagnostics

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

## Score history

- 2026-09-29: 66
- 2026-09-28: 66
- 2026-09-27: 66
- 2026-09-26: 65
- 2026-09-25: 65

## Common questions

### What is the Assinafy MCP server?

Assinafy is an MCP server listed in the public MCP registry as io.github.assinafy/mcp-server. Send documents for legally valid e-signature in Brazil, track signers and download signed files. This page covers its hosted endpoint (https://mcp.assinafy.com.br/mcp).

### Is the Assinafy MCP server safe to use?

Assinafy scores 66 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 Assinafy MCP server expose?

Assinafy exposes 11 tools: assinafy_check_fields, assinafy_delete_document, assinafy_download_document, assinafy_find_documents, assinafy_find_signers, and 6 more. Their descriptions and schemas cost roughly 869 tokens of context every time the server is loaded.

### Does the Assinafy MCP server require authentication?

No. We connected to Assinafy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Assinafy MCP server still maintained?

Assinafy is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.assinafy.com.br/mcp
- Repository: https://github.com/assinafy/mcp-server
- Website: https://www.assinafy.com.br/api
- Changelog RSS feed: https://verifymcp.io/servers/assinafy-mcp-server/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/assinafy-mcp-server/mcp.json
- HTML version of this page: https://verifymcp.io/servers/assinafy-mcp-server/mcp