Mervext vs Contract Parser
A side-by-side look at the Mervext and Contract Parser MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mervext for legal work over a hosted endpoint; choose Contract Parser for legal over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mervext when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
MERVEKT_API_KEY, MERVEKT_API_URL.
Choose Contract Parser when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 36/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | MERVEKT_API_KEYMERVEKT_API_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 8 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Mervext | View Contract Parser |
Tools & capabilities
Mervext tools
No tool names declared yet. Check the project README from the listing page.
Contract Parser 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.
Mervext
{
"mcpServers": {
"mervext": {
"url": "https://api.vstudiodigital.com"
}
}
}
Contract Parser
{
"mcpServers": {
"document-to-json-pdf-invoice-statement-contract-parser": {
"url": "https://mcp.apify.com/?actors=opportunity-biz/document-to-json-mcp"
}
}
}
Frequently asked questions
Mervext is categorized under Legal and uses a remote HTTP/SSE transport. Contract Parser belongs to Legal and uses a remote HTTP/SSE transport. Pick Mervext for legal work and Contract Parser 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.
Mervext has no declared pricing — check the project's own site. Contract Parser has no declared pricing — check the project's own site. 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 mervext and document-to-json-pdf-invoice-statement-contract-parser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mervext has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Contract Parser has 39/100 (Fair) with 1 views, 0 installs and 8 GitHub stars.
