Korala MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Korala agreement drafting, sending and signing-status tools: Do send/void opt-ins and signer-token omission persist while the agent remains unable to sign for a person?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Drafting and preparing e-signature workflows with explicit review/send controls.

What we know

Document-signing MCP with draft-only, hosted OAuth and local API-key modes for agreements, templates, signers, fields, uploads, sends, status and voiding.

Maintenance / activity evidence

@korala/mcp 0.9.0 published 2026-09-25T08:21:36.505Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Document/template/signature read/write authority; send/void gated by explicit permission. Writes: Create/edit templates/docs; Upload files; Add/remove signers/fields; Fill fields; Send signing requests; Void documents.
OAuth consent or API key/secret.
Sensitive access: Legal agreements, Signer identities/contact details, PDFs, Signature status

Legal-document actions can contact signers or void documents; keep binding permissions off by default.
Draft-only links are not private secrets.
Test-mode live-document gap is documented.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do send/void opt-ins and signer-token omission persist while the agent remains unable to sign for a person?

The bounded review of the publisher's documented Korala agreement drafting, sending and signing-status tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Legal-document actions can contact signers or void documents; keep binding permissions off by default.
Draft-only links are not private secrets.
Test-mode live-document gap is documented.
Document/template/signature read/write authority; send/void gated by explicit permission.
OAuth consent or API key/secret.
Documents, PDFs, signer names/emails and signature status are processed by Korala; draft-link content can be accessible to anyone with the URL.
Reviewed write actions: Create/edit templates/docs; Upload files; Add/remove signers/fields; Fill fields; Send signing requests; Void documents
Sensitive access: Legal agreements, Signer identities/contact details, PDFs, Signature status
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
public repository identity
full privacy/retention policy
general pricing
Send/void are destructive/binding operations and require explicit permission.
Draft links are readable by anyone with the link and should use example data.
Test-mode keys have a documented gap allowing access to live documents by ID.
No public repository was declared in npm metadata.

Original activity observations

@korala/mcp 0.9.0 published 2026-09-25T08:21:36.505Z

Technical identity

npm/@korala/mcp

Exact implementation source: https://www.npmjs.com/package/@korala/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@korala/mcp
Service endpoint: https://api.korala.ai/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@korala/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
docs.korala.ai/ai-agents
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
docs.korala.ai/ai-agents/tools
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
docs.korala.ai/ai-agents/api-key
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Remote OAuth preferred; local API-key route uses KORALA_API_KEY_ID and KORALA_API_SECRET; sending disabled unless explicitly enabled.
publisher install or stdio launch · Claude Code only · Publisher instructions
claude mcp add --transport http korala https://api.korala.ai/mcp
Configure / authenticate
MCP100 setup guide
Publisher recommends remote MCP URL at https://api.korala.ai/mcp; disconnected under Korala connected-agent/settings interface. Do not install npm package unless local integration specifically required.
Check connection
Suggested check
Use https://api.korala.ai/mcp remote connector and OAuth, then list read-only tools. Avoid sending signing links.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `korala`, run `claude mcp remove korala` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate provider credential revocation · publisher documented: Korala documents Settings → AI Assistants for disconnecting hosted AI agents. API-key local route uses Settings → API Keys; treat API-key deletion as issuer action and do not claim an exact key-delete button not observed.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove korala

Official Documentation & Sources

What it does

Document-signing MCP with draft-only, hosted OAuth and local API-key modes for agreements, templates, signers, fields, uploads, sends, status and voiding.

Capability: Productivity & Collaboration
Resource type: MCP Server
Industry: Legal & Compliance
Best fit: Drafting and preparing e-signature workflows with explicit review/send controls.

Representative uses

Draft agreements and review links
Create/reuse templates
Prepare/upload PDFs and signer fields
Send signing requests
Track or void documents

Limitations

Send/void are destructive/binding operations and require explicit permission.
Draft links are readable by anyone with the link and should use example data.
Test-mode keys have a documented gap allowing access to live documents by ID.
No public repository was declared in npm metadata.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: OAuth consent or API key/secret.
Permissions: Document/template/signature read/write authority; send/void gated by explicit permission.
Data handling: Documents, PDFs, signer names/emails and signature status are processed by Korala; draft-link content can be accessible to anyone with the URL.
Cost: plan_based
Risk and cautions: Legal-document actions can contact signers or void documents; keep binding permissions off by default.

Access scope and cautions

Write actions: Create/edit templates/docs Upload files Add/remove signers/fields Fill fields Send signing requests Void documents
Sensitive access: Legal agreements Signer identities/contact details PDFs Signature status
Risk level: high
Security notes: Draft-only links are not private secrets. Test-mode live-document gap is documented.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Draft agreements and review links; Create/reuse templates; Prepare/upload PDFs and signer fields; Send signing requests; Track or void documents.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @korala/mcp. Recorded endpoint: https://api.korala.ai/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: KORALA_API_KEY_ID (local); KORALA_API_SECRET (local); KORALA_MCP_ALLOW_SEND (optional); KORALA_API_URL (optional); KORALA_WEB_URL (optional). No configuration values are supplied here. Prerequisites: MCP client; Korala account for live/connected flows. Client notes: Keep send/void disabled unless explicitly authorized; test-mode keys should still be treated as able to reach live docs. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Hosted OAuth/consent, local API key, or no-account draft-only mode.

Can it modify data or perform write operations?

Documented write actions include: Create/edit templates/docs; Upload files; Add/remove signers/fields; Fill fields; Send signing requests; Void documents. Recorded permission boundary: Document/template/signature read/write authority; send/void gated by explicit permission.

What data-handling boundary should I consider?

Documents, PDFs, signer names/emails and signature status are processed by Korala; draft-link content can be accessible to anyone with the URL. Recorded sensitive-access context: Legal agreements; Signer identities/contact details; PDFs; Signature status.

What limitations and risks should I check before use?

Legal-document actions can contact signers or void documents; keep binding permissions off by default. Send/void are destructive/binding operations and require explicit permission. Draft links are readable by anyone with the link and should use example data. Test-mode keys have a documented gap allowing access to live documents by ID. No public repository was declared in npm metadata. Draft-only links are not private secrets. Test-mode live-document gap is documented. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Korala is listed as First-party MCP in MCP100’s current evidence.