Nordic Data vs Vexa
A side-by-side look at the Nordic Data and Vexa MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Nordic Data for communication work over a hosted endpoint; choose Vexa for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Nordic Data when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_tenders, get_tender, search_awards.
Choose Vexa when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
API_KEY, API_BASE, TRANSCRIBE_ENABLED, RUNTIME_BACKEND.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 48/100 · Fair | 48/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 | None listed | API_KEYAPI_BASETRANSCRIBE_ENABLEDRUNTIME_BACKEND |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2,906 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 28 | Not listed |
| Full listing | View Nordic Data | View Vexa |
Tools & capabilities
Nordic Data tools 28
search_tendersNordic procurement notices by country, keyword, CPV, date. Filter by `source` (EU-wide vs Norway-with-below-threshold) or `buyer_orgnr`.get_tenderFull tender details by IDsearch_awardsSearch contract awards (who won what)get_tender_leaderboardTop public-sector buyers in a Nordic countryget_company_contract_winsPublic-sector contracts won by a Norwegian companysearch_companiesSearch by name, industry, locationget_companyFull registry recordget_company_contactPublic email + phone (with MX-verified email candidates)get_company_narrativeAI-generated executive summaryget_company_peersPeer-cohort benchmarksget_company_snapshotOne-call snapshot across every data layerget_company_changesRegistry change history- +16 more on the listing page
Vexa 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.
Nordic Data
{
"mcpServers": {
"nordic-data": {
"url": "https://api.nordicdata.cloud/mcp"
}
}
}
Vexa
{
"mcpServers": {
"vexa": {
"url": "https://api.cloud.vexa.ai/bots"
}
}
}
Frequently asked questions
Nordic Data is categorized under Communication and uses a remote HTTP/SSE transport. Vexa belongs to Communication and uses a remote HTTP/SSE transport. Pick Nordic Data for communication work and Vexa for communication.
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.
Nordic Data has no declared pricing — check the project's own site. Vexa 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 nordic-data and vexa as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Nordic Data has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Vexa has 48/100 (Fair) with 2 views, 0 installs and 2,906 GitHub stars.