GovContract Radar vs Krasoft Russian Public Procurement
A side-by-side look at the GovContract Radar and Krasoft Russian Public Procurement MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
K
Krasoft Russian Public ProcurementLegal · Remote HTTP/SSESearch and analytics for Russian public procurement (44-FZ/223-FZ): tenders, contracts, market data42FairAuth: not declaredVerdict: choose GovContract Radar for legal work; choose Krasoft Russian Public Procurement 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 GovContract Radar when
- You need dedicated capabilities in the Legal domain.
KChoose Krasoft Russian Public Procurement 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 | K Krasoft Russian Public Procurement | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 29/100 · Emerging | 42/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| 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 | 0 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View GovContract Radar | View Krasoft Russian Public Procurement |
Tools & capabilities
GovContract Radar tools
No tool names declared yet. Check the project README from the listing page.
Krasoft Russian Public Procurement 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.
GovContract Radar
No confirmed install command for GovContract Radar yet — follow the setup steps linked from its listing page rather than a guessed package name.
Krasoft Russian Public Procurement
{
"mcpServers": {
"krasoft-russian-public-procurement": {
"url": "https://zakupki.krasoft.ru/mcp"
}
}
}
Frequently asked questions
GovContract Radar is categorized under Legal and uses an install path we have not confirmed yet. Krasoft Russian Public Procurement belongs to Legal and uses a remote HTTP/SSE transport. Pick GovContract Radar for legal work and Krasoft Russian Public Procurement 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. GovContract Radar has no confirmed install command yet — follow its own setup instructions.
GovContract Radar has no declared pricing — check the project's own site. Krasoft Russian Public Procurement 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 govcontract-radar and krasoft-russian-public-procurement as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GovContract Radar has a quality signal of 29/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Krasoft Russian Public Procurement has 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.