A side-by-side look at the OFACScreen Sanctions Screening and Star Wars MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OFACScreen Sanctions Screening for developer tools work; choose Star Wars MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | O OFACScreen Sanctions Screening | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 37/100 · Fair | 47/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View OFACScreen Sanctions Screening | View Star Wars MCP |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for OFACScreen Sanctions Screening yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"star-wars-mcp": {
"command": "npx",
"args": [
"-y",
"@openapitools/openapi-generator-cli"
]
}
}
}