Splitifi Intelligence MCP

io.github.mysplitifiPublished by GitHub account mysplitifiv2.1.1Updated Oct 24, 2026

Outcome predictions and judge profiles from 2,741 ML models trained on 30.3M court records.

VerifiedSTDIODesktop onlyData & AnalyticsAI & ML

Overview

AI-generated overview

Splitifi Intelligence MCP gives an assistant access to outcome predictions and judge profiles derived from court records via a local npm process.

What you can do
This local MCP server connects an assistant to the Splitifi Intelligence backend, which the provider describes as offering outcome predictions and judge profiles from 2,741 ML models trained on 30.3M court records. The manifest does not list individual tools, so the exact operations are not documented here. It runs as a local stdio process started from the npm package splitifi-mcp.
When to use it
Consider it when an assistant needs predictive or profile information about court outcomes or judges as part of a legal research or analysis workflow. It is not useful if you do not have a Splitifi API key or do not need this kind of prediction data.
Requirements
Node.js to run the npm package splitifi-mcp locally over stdio. A Splitifi API key in the environment variable SPLITIFI_API_KEY, obtained from the provider's developer site; keys begin with sk_live_ for production or sk_test_ for a sandbox with synthetic responses. Network access to the backend, whose URL can be overridden with SPLITIFI_API_URL. Desktop only.
Before you install
The server requires a secret API key (SPLITIFI_API_KEY); keep it out of logs and shared configuration, and note that a production key may incur usage or cost. Requests send your queries to the provider's backend, so treat the data as third-party processed. The manifest lists no tools, so review what the server actually calls before relying on it.

Installation

In SourceWeft

  1. Open Splitifi Intelligence MCP 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. v2.1.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.