Ebenova Legal Docs

io.github.dgtalquantumleap-aiPublished by GitHub account dgtalquantumleap-aiv1.5.1Updated Oct 24, 2026

Generate 27 legal document types across 18 jurisdictions via Ebenova API.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Lets an assistant generate legal documents across multiple document types and jurisdictions through the Ebenova API.

What you can do
This local MCP server connects an assistant to the Ebenova API so it can produce legal documents. According to the registry description, it covers 27 legal document types across 18 jurisdictions. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to draft or produce legal paperwork spanning several document types or jurisdictions, and you already use the Ebenova service. It is a desktop-only local process, so it is not suited to browser-based or hosted use.
Requirements
Runs as a local process over stdio, installed from the npm package ebenova-legal-docs-mcp, so Node.js is needed. It requires the secret environment variable EBENOVA_API_KEY, described as an Ebenova API key from the provider's dashboard. Network access to the Ebenova API is implied.
Before you install
The server requires the secret EBENOVA_API_KEY; store it securely and avoid exposing it in logs or shared configuration. Document content you submit is sent to the third-party Ebenova API, so avoid confidential material unless that is acceptable. The manifest lists no tools, so review what the server can do before relying on it.

Installation

In SourceWeft

  1. Open Ebenova Legal Docs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.5.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.