Udbud Dk
Server Details
Udbud.dk MCP — Danish government public procurement notices (keyless).
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-udbud-dk
- GitHub Stars
- 0
- Server Listing
- mcp-udbud-dk
TDQS
Scored across 34 tools
Several tools overlap heavily: ask_pipeworx, ask_pipeworx_beta (currently identical), ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all route or discover data, and five polymarket_* tools cover related prediction-market analysis. Descriptions help distinguish most cases, but boundaries are fuzzy enough to risk misselection.
Most tools use snake_case, but the pattern is mixed: verb_noun (compare_entities, resolve_entity), noun_phrase (entity_profile, recent_changes), imperative (remember, subscribe), and prefixed names (ask_pipeworx, dk_tender_*). It remains readable but lacks a single predictable convention.
34 tools is excessive for a server whose name and core identity (Udbud Dk) point to Danish public tenders—only three tools (dk_tender_search/recent/detail) serve that domain. The rest are broad platform meta-tools, making the set feel bloated and unfocused.
The Danish tender surface covers search (free-text, CPV, CVR, type, dates), recent listings, and full notice detail—core lifecycle for procurement data. A notable gap is proactive monitoring: subscribe supports sec_8k, polymarket_edge, and fred_series but not Danish tender alerts, so agents must poll recent.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
Related MCP Connectors
Germany public procurement MCP — official German government tenders (keyless).
Netherlands TenderNed MCP — Dutch government public procurement notices (keyless).
Doffin MCP — Norwegian government public procurement notices (BYOK / platform key).
Moldova Government Procurement (MTender) MCP — keyless.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceAccess official German government public procurement tenders via MCP, with keyless access.4 npmMIT
- AlicenseAqualityAmaintenanceMCP server for amtsblattportal.ch — the Swiss official gazette portal (SHAB + 27 cantonal gazettes). Public procurement and official notices, person-data rubrics excluded by design.645 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for accessing Dutch government public procurement notices from TenderNed without requiring an API key.3 npmMIT
- AlicenseNot gradedqualityBmaintenanceNeutral MCP server for researching public procurement notices from EU (TED) and German (DÖE) sources, offering tools to search, retrieve, and inspect notices without built-in business preferences.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.