Assinafy
REMOTE · MCP.ASSINAFY.COM.BR · SCANNED SEP 29
Send documents for legally valid e-signature in Brazil, track signers and download signed files.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · mcp.assinafy.com.br
claude mcp add --transport http assinafy-mcp-server 'https://mcp.assinafy.com.br/mcp'
{
"mcpServers": {
"assinafy-mcp-server": {
"url": "https://mcp.assinafy.com.br/mcp"
}
}
} {
"servers": {
"assinafy-mcp-server": {
"type": "http",
"url": "https://mcp.assinafy.com.br/mcp"
}
}
} [mcp_servers.assinafy-mcp-server] url = "https://mcp.assinafy.com.br/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"assinafy-mcp-server": {
"type": "remote",
"url": "https://mcp.assinafy.com.br/mcp",
"enabled": true
}
}
} openclaw mcp add assinafy-mcp-server --url 'https://mcp.assinafy.com.br/mcp' --transport streamable-http
mcp_servers:
assinafy-mcp-server:
url: "https://mcp.assinafy.com.br/mcp" {
"McpServers": {
"assinafy-mcp-server": {
"Transport": "http",
"Url": "https://mcp.assinafy.com.br/mcp"
}
}
} assistant mcp add assinafy-mcp-server -t streamable-http -u 'https://mcp.assinafy.com.br/mcp'
{
"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.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +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.
- 26 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Sept 26 65
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 29 Sept 2026 · Probed https://mcp.assinafy.com.br/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=assinafy.com.br | CN=WE1,O=Google Trust Services,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 16f5627743c8b1400e075f972e86b144 |
| SANs: assinafy.com.br, *.assinafy.com.br, atlassian.assinafy.com.br | ||||||
| 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 mcp.assinafy.com.br. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| br. | present | 38298 | 13 | Verified |
| com.br. | present | 2557 | 13 | Verified |
| assinafy.com.br. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.assinafy.com.br/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.assinafy.com.br/mcp | HTTPS enforced | 301 | https://mcp.assinafy.com.br/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 →
assinafy_check_fields Find and validate fields ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Choose exactly one action; supply only its arguments. |
No output schema declared.
No examples provided.
assinafy_delete_document Delete a document ~54
Delete a document only when the user's instruction explicitly authorizes deletion. Inspect its current state first; Assinafy enforces which documents may be deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | unique document ID to delete |
No output schema declared.
No examples provided.
assinafy_download_document Download a document or page ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Choose exactly one action; supply only its arguments. |
No output schema declared.
No examples provided.
assinafy_find_documents Find and inspect documents ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Choose exactly one action; supply only its arguments. |
No output schema declared.
No examples provided.
assinafy_find_signers Find signers ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Choose exactly one action; supply only its arguments. |
No output schema declared.
No examples provided.
assinafy_find_templates Find saved templates ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Choose exactly one action; supply only its arguments. |
No output schema declared.
No examples provided.
assinafy_follow_up_assignment Follow up on signatures ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Choose exactly one action; supply only its arguments. |
No output schema declared.
No examples provided.
assinafy_prepare_document Prepare a document ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Choose exactly one action; supply only its arguments. |
No output schema declared.
No examples provided.
assinafy_request_signatures Request signatures ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Choose exactly one action; supply only its arguments. |
No output schema declared.
No examples provided.
assinafy_save_signer Save signer contact details ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Choose exactly one action; supply only its arguments. |
No output schema declared.
No examples provided.
assinafy_verify_document Verify a signed document ~56
Verify a signed document using its actual Assinafy SHA-1 signature hash. Public lookup; requires no workspace connection and sends no credential upstream.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | SHA-1 signature hash of the signed document |
No output schema declared.
No examples provided.
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.