A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Signdocs Brasil is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
95/100
trust score
7
downloads a day
local
runs on your machine
442
downloads in 30d
What it does
Model Context Protocol (MCP) server for the SignDocs Brasil e-signature API — lets AI agents create signing sessions, manage envelopes, verify documents and more. Local stdio, remote HTTP, and AWS Lambda transports.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'SIGNDOCS_CLIENT_ID=${SIGNDOCS_CLIENT_ID}' --env 'SIGNDOCS_CLIENT_SECRET=${SIGNDOCS_CLIENT_SECRET}' --transport stdio signdocs-brasil-mcp '--' npx -y --package=@signdocs-brasil/mcp-server signdocs-mcp
# 2 — ask your agent for something these tools do
# upload_document, download_document, create_envelope and 23 more
It needs SIGNDOCS_CLIENT_ID, SIGNDOCS_CLIENT_SECRET: this reads them from your environment, so export them first.
Signdocs Brasil costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SBAll 1 server
@signdocs-brasil1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Signdocs Brasil as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads SIGNDOCS_CLIENT_ID (OAuth2 client ID from app.signdocs.com.br → API), SIGNDOCS_CLIENT_SECRET (OAuth2 client secret from app.signdocs.com.br → API) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx SIGNDOCS_CLIENT_ID …, setx SIGNDOCS_CLIENT_SECRET … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'SIGNDOCS_CLIENT_ID=${SIGNDOCS_CLIENT_ID}' --env 'SIGNDOCS_CLIENT_SECRET=${SIGNDOCS_CLIENT_SECRET}' --transport stdio signdocs-brasil-mcp '--' npx -y --package=@signdocs-brasil/mcp-server signdocs-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: SIGNDOCS_CLIENT_ID — OAuth2 client ID from app.signdocs.com.br → API; SIGNDOCS_CLIENT_SECRET — OAuth2 client secret from app.signdocs.com.br → API. You set them in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
26 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Upload a base64-encoded PDF to an existing transaction (≤10MB inline; use presign for larger).
No parameter schema on file.
Get presigned download URLs for a transaction’s document and signed artifacts.
No parameter schema on file.
No parameter schema on file.
Get envelope details including per-signer session summaries and completion counts.
No parameter schema on file.
No parameter schema on file.
Generate the combined stamped PDF (all signers) for a COMPLETED envelope and return a download URL.
No parameter schema on file.
Retrieve the cryptographic evidence (hashes, step proofs, evidenceId) for a completed transaction.
No parameter schema on file.
No parameter schema on file.
Poll the current status of a signing session (ACTIVE/COMPLETED/CANCELLED/EXPIRED/FAILED).
No parameter schema on file.
Get full bootstrap data for a signing session (signer, steps, document, appearance).
No parameter schema on file.
List signing sessions filtered by status, with cursor pagination.
No parameter schema on file.
No parameter schema on file.
Resend the OTP challenge for a signing session, optionally over a specific channel (email/sms).
No parameter schema on file.
Search transactions by status, signer external ID, document group, or date range (cursor pagination).
No parameter schema on file.
Get full details of a single transaction, including its steps and results.
No parameter schema on file.
No parameter schema on file.
Get a one-time drag-and-drop upload page URL to give the user so they can upload a PDF
No parameter schema on file.
Publicly verify a completed signature by its evidenceId. Returns status, document/evidence hashes,
No parameter schema on file.
Publicly verify all signers of an envelope and get consolidated download URLs.
No parameter schema on file.
No parameter schema on file.
Register an HTTPS endpoint to receive event notifications. The response returns a signing secret
No parameter schema on file.
List all registered webhooks for the tenant.
No parameter schema on file.
No parameter schema on file.
Send a sample payload to a registered webhook and return the delivery result.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Signdocs Brasil or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 95 / 100
Release 0.11.2 · scanned 15 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score95
Findings1 threat · 1 capability
Capabilitymoderate
Coveragesource
Verificationnone
Surface digeste3672be2346ec58314725ce60d9c29e8b437707d4caa070315afab5e2ce34f9a
Score vectorthreat 100 → client 95
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (26 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_my_account | no tags | |
| create_signing_session | no tags | |
| create_envelope | no tags | |
| get_signing_session_status | no tags | |
| get_envelope | no tags | |
| cancel_signing_session | no tags | |
| cancel_envelope | no tags | |
| download_document | untrusted-input | untrusted-input: keyword "download" |
| get_evidence | no tags | |
| verify_evidence | no tags | |
| verify_envelope | untrusted-input | untrusted-input: keyword "download" |
| verify_document | no tags | |
| upload_document | no tags | |
| add_session_to_envelope | no tags | |
| get_envelope_combined_stamp | untrusted-input | untrusted-input: keyword "download" |
| get_signing_session | no tags | |
| list_signing_sessions | no tags | |
| resend_signing_session_otp | no tags | |
| list_transactions | no tags | |
| get_transaction | no tags | |
| cancel_transaction | no tags | |
| request_document_upload | no tags | |
| register_webhook | external-sink | external-sink: keyword "webhook" |
| list_webhooks | no tags | |
| delete_webhook | external-sink | external-sink: keyword "webhook" |
| test_webhook | external-sink | external-sink: keyword "webhook" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digeste3672be2346ec583
Scanned2026-10-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.11.2. Pin a release below and the command asks for exactly that one.
0.11.2
7 Sep 2026
latestNo release note was published with this version.
0.11.1
5 Sep 2026
No release note was published with this version.
0.11.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Signdocs Brasil can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.