ComplyEdge TrustLint vs Ny Omig Exclusions
A side-by-side look at the ComplyEdge TrustLint and Ny Omig Exclusions MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ComplyEdge TrustLint for legal work as a local process; choose Ny Omig Exclusions for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose ComplyEdge TrustLint when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
COMPLYEDGE_API_KEY.
Choose Ny Omig Exclusions when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 45/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | COMPLYEDGE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View ComplyEdge TrustLint | View Ny Omig Exclusions |
Tools & capabilities
ComplyEdge TrustLint tools
No tool names declared yet. Check the project README from the listing page.
Ny Omig Exclusions tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
ComplyEdge TrustLint
{
"mcpServers": {
"complyedge-trustlint": {
"command": "npx",
"args": [
"-y",
"@complyedge/mcp"
],
"env": {
"COMPLYEDGE_API_KEY": "YOUR_COMPLYEDGE_API_KEY_HERE"
}
}
}
}
Ny Omig Exclusions
{
"mcpServers": {
"ny-omig-exclusions": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-ny-omig-exclusions"
]
}
}
}
Frequently asked questions
ComplyEdge TrustLint is categorized under Legal and uses a local stdio subprocess. Ny Omig Exclusions belongs to Legal and uses a local stdio subprocess. Pick ComplyEdge TrustLint for legal work and Ny Omig Exclusions for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
ComplyEdge TrustLint has no declared pricing — check the project's own site. Ny Omig Exclusions is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add complyedge-trustlint and ny-omig-exclusions as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ComplyEdge TrustLint has a quality signal of 45/100 (Fair) with 2 views, 0 installs and 4 GitHub stars. Ny Omig Exclusions has 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.