ContractLens vs Codex MCP
A side-by-side look at the ContractLens and Codex MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
ContractLensFinance & FintechEVM token risk checks, x402 payability check for sellers, address classifier and live gas.39FairAuth: no auth requiredVerdict: choose ContractLens for finance & fintech work; choose Codex MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose ContractLens when
- You need dedicated capabilities in the Finance & Fintech domain.
- Its auth model fits you: No auth required.
Choose Codex MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CODEX_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C ContractLens | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 39/100 · Fair | 43/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | CODEX_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 25 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View ContractLens | View Codex MCP |
Tools & capabilities
ContractLens tools
No tool names declared yet. Check the project README from the listing page.
Codex MCP 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.
ContractLens
No confirmed install command for ContractLens yet — follow the setup steps linked from its listing page rather than a guessed package name.
Codex MCP
{
"mcpServers": {
"codex-data-codex-mcp": {
"command": "npx",
"args": [
"-y",
"@codex-data/codex-mcp"
],
"env": {
"CODEX_API_KEY": "YOUR_CODEX_API_KEY_HERE"
}
}
}
}
Frequently asked questions
ContractLens is categorized under Finance & Fintech and uses an install path we have not confirmed yet. Codex MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick ContractLens for finance & fintech work and Codex MCP for finance & fintech.
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. ContractLens has no confirmed install command yet — follow its own setup instructions.
ContractLens has no declared pricing — check the project's own site. Auth: no auth required. Codex MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 contractlens and codex-data-codex-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ContractLens has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Codex MCP has 43/100 (Fair) with 4 views, 0 installs and 25 GitHub stars.