FreeSign — Free e-signature
REMOTE · FREE-SIGN.COM · SCANNED SEP 25
Free e-signature for humans and AI agents — zero-document PDF signing from hashes only.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 421 tokens (~84/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the FreeSign — Free e-signature MCP server?
FreeSign — Free e-signature is a hosted endpoint at https://free-sign.com/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 · free-sign.com
claude mcp add --transport http com-free-sign-signing 'https://free-sign.com/mcp'
{
"mcpServers": {
"com-free-sign-signing": {
"url": "https://free-sign.com/mcp"
}
}
} {
"servers": {
"com-free-sign-signing": {
"type": "http",
"url": "https://free-sign.com/mcp"
}
}
} [mcp_servers.com-free-sign-signing] url = "https://free-sign.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-free-sign-signing": {
"type": "remote",
"url": "https://free-sign.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-free-sign-signing --url 'https://free-sign.com/mcp' --transport streamable-http
mcp_servers:
com-free-sign-signing:
url: "https://free-sign.com/mcp" {
"McpServers": {
"com-free-sign-signing": {
"Transport": "http",
"Url": "https://free-sign.com/mcp"
}
}
} assistant mcp add com-free-sign-signing -t streamable-http -u 'https://free-sign.com/mcp'
{
"mcpServers": {
"com-free-sign-signing": {
"type": "http",
"url": "https://free-sign.com/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.
- 25 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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 Jul 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
- 26 Jul 26 0
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 25 Sept 2026 · Probed https://free-sign.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=free-sign.com | CN=WE1,O=Google Trust Services,C=US | 12 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ad38566ea7cdcbe50e7bc6d3721e2a26 |
| SANs: free-sign.com, www.free-sign.com, *.www.free-sign.com | ||||||
| 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 free-sign.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| free-sign.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), publickey-credentials-get=(self), publickey-credentials-create=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://free-sign.com/mcp | Verified | 200 | |
| http (plaintext) | http://free-sign.com/mcp | HTTPS enforced | 301 | https://free-sign.com/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 →
create_signing_envelope Create signing envelope ~128
Create a FreeSign envelope from a PDF SHA-256 hash. Do not send PDF bytes. The created envelope is NOT yet session-bound — the browser that opens the returned signing_url generates an ECDSA P-256 keypair locally and POSTs the public JWK to /api/envelopes/{id}/session-bind before any protected request will succeed. AI agents calling this tool just hand the signing_url to a human, who continues in a browser.
| Name | Type | Req | Description |
|---|---|---|---|
| document_sha256 | string | yes | SHA-256 of the original PDF bytes, computed locally by the user or agent. |
| Name | Type | Req | Description |
|---|---|---|---|
| envelope_id | string | yes | – |
| expires_at | string | yes | – |
| session_binding_required | boolean | – | True when the envelope still needs the browser to call /api/envelopes/{id}/session-bind. Always true for MCP-created envelopes. |
| signing_url | string | yes | – |
No examples provided.
get_ots_proof Get OpenTimestamps proof ~109
Return the .ots proof (base64) for a given OpenTimestamps anchor on an envelope. Use the official `ots-cli` to verify offline against Bitcoin block headers. Each seal has two anchors: `kind: "byterange"` commits to the signed document, `kind: "signed_attrs"` commits to SHA-256 of the CMS SignedAttributes (which carry the post-quantum key commitment).
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | – |
| envelope_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | – |
| anchored_hash | string | yes | – |
| btc_block_hash | string|null | – | – |
| btc_block_height | integer|null | – | – |
| calendar_urls | array | – | – |
| envelope_id | string | yes | – |
| kind | string | – | – |
| proof_base64 | string | yes | Complete .ots file bytes, base64. |
| status | string | yes | – |
No examples provided.
get_receipt Get receipt ~58
Return the envelope record (including final_pdf_sha256, final_signature_base64url, final_payload_json), per-signer signing receipts, and OpenTimestamps anchor metadata. Evidence only, never PDF bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | – |
| ots_anchors | array | yes | – |
| receipts | array | yes | – |
No examples provided.
verify_audit_chain Verify audit chain ~95
Return an envelope's append-only audit-event hash chain together with a server-computed integrity verdict: every event_hash is recomputed from its canonical material, and the prev_event_hash linkage and per-envelope seq contiguity are checked. Evidence only, never PDF bytes. The raw events are included verbatim so the caller can independently re-derive the verdict instead of trusting `chain.valid`.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attested_audit_chain_head_hash | string|null | yes | The audit-chain head derived from the signer-signed v2 final payload (G-01), fed into the verdict's head cross-check. NULL until the envelope is finalized. |
| attested_head_signature_verified | boolean | yes | True when the final-payload signature carrying the attested head was re-verified against the signer's on-file public key. False when not finalized or the signature did not verify. |
| chain | object | yes | – |
| envelope_id | string | yes | – |
| events | array | yes | – |
No examples provided.
verify_document_hash Verify document hash ~31
Find FreeSign receipts matching a local document SHA-256 hash.
| Name | Type | Req | Description |
|---|---|---|---|
| document_sha256 | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | yes | – |
No examples provided.
What is the FreeSign — Free e-signature MCP server?
FreeSign — Free e-signature is an MCP server listed in the public MCP registry as com.free-sign/signing. Free e-signature for humans and AI agents, zero-document PDF signing from hashes only. This page covers its hosted endpoint (https://free-sign.com/mcp).
Is the FreeSign — Free e-signature MCP server safe to use?
FreeSign — Free e-signature scores 77 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 FreeSign — Free e-signature MCP server expose?
FreeSign — Free e-signature exposes 5 tools: create_signing_envelope, verify_document_hash, get_receipt, get_ots_proof, verify_audit_chain. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.
Does the FreeSign — Free e-signature MCP server require authentication?
No. We connected to FreeSign — Free e-signature without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FreeSign — Free e-signature MCP server still maintained?
FreeSign — Free e-signature is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.