
Inmigreat Mcp
io.github.djangelo88Published by GitHub account djangelo88v0.1.2Updated Oct 24, 2026
Immigration case intelligence for attorneys. Case tracking, judge analytics, AI predictions.
Overview
A local MCP server offering immigration case intelligence for attorneys, with case tracking, judge analytics and AI predictions.
- What you can do
- Track immigration cases and their status through the server's case tools, as described in its registry entry. Review judge analytics to compare how judges handle cases. Get AI-generated predictions about case outcomes. The manifest lists no individual tools, so the exact operations are not documented; the capabilities above come only from the short registry description.
- When to use it
- Worth considering for immigration attorneys or legal teams who want an assistant to help track cases, look at judge-level analytics, or explore predicted case outcomes. It is a narrow, domain-specific tool, so it is not useful outside immigration legal work.
- Requirements
- Runs as a local process on the user's machine via the npm package inmigreat-mcp over stdio, so Node.js and npm are needed. The manifest declares no authentication, environment variables or headers. Desktop only; no web executable.
Installation
In SourceWeft
- Open Inmigreat Mcp in the dashboard and add it to a workspace.
- 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
0Version history
1- v0.1.2LatestSep 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.