ComplyEdge TrustLint vs Japan MOF Sanctions List Relay
A side-by-side look at the ComplyEdge TrustLint and Japan MOF Sanctions List Relay MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
J
Japan MOF Sanctions List RelayLegalIs this name on Japan's MOF asset-freeze list? Hosted, list-change history kept. Reference only.39FairAuth: no auth requiredVerdict: choose ComplyEdge TrustLint for legal work as a local process; choose Japan MOF Sanctions List Relay for legal. 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.
JChoose Japan MOF Sanctions List Relay when
- You need dedicated capabilities in the Legal domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | J Japan MOF Sanctions List Relay | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 45/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | 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 | — |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View ComplyEdge TrustLint | View Japan MOF Sanctions List Relay |
Tools & capabilities
ComplyEdge TrustLint tools
No tool names declared yet. Check the project README from the listing page.
Japan MOF Sanctions List Relay 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"
}
}
}
}
Japan MOF Sanctions List Relay
No confirmed install command for Japan MOF Sanctions List Relay yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
ComplyEdge TrustLint is categorized under Legal and uses a local stdio subprocess. Japan MOF Sanctions List Relay belongs to Legal and uses an install path we have not confirmed yet. Pick ComplyEdge TrustLint for legal work and Japan MOF Sanctions List Relay 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. Japan MOF Sanctions List Relay has no confirmed install command yet — follow its own setup instructions.
ComplyEdge TrustLint has no declared pricing — check the project's own site. Japan MOF Sanctions List Relay 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 japan-mof-sanctions-list-relay 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. Japan MOF Sanctions List Relay has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.