Libelus

ai.libelusPublished by libelus.aiOfficial publisherv0.1.2Updated Oct 24, 2026

Andamento de processos pelo número CNJ, prazos, CPF/CNPJ e jurisprudência (planos).

VerifiedStreamable HTTPWeb executableKnowledge & MemoryBusiness & Commerce

Overview

AI-generated overview

Lets an assistant look up Brazilian court case progress by CNJ number, deadlines, CPF/CNPJ, and case law, subject to subscription plans.

What you can do
Libelus is a remote MCP server for Brazilian legal research. According to its registry description, it provides case progress tracking by CNJ number, deadlines, CPF/CNPJ lookups, and jurisprudence search. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Worth considering for assistants that support Brazilian legal work: monitoring case progress, checking deadlines, looking up parties by CPF/CNPJ, or searching jurisprudence. Less relevant outside Brazilian legal practice.
Requirements
A remote streamable HTTP endpoint at the provider's server, with OAuth authentication required. No packages, environment variables, or headers are declared. Access appears to depend on a paid plan.
Before you install
The description mentions plans, so use may require a paid subscription. Queries involve CNJ case numbers and CPF/CNPJ identifiers, which are sensitive personal and legal data sent to a third-party service; confirm how that data is handled before use.

Installation

In SourceWeft

  1. Open Libelus in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.libelus%2Fconector/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "libelus": {
      "type": "http",
      "url": "https://mcp.libelus.ai/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.2LatestOct 11, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.