mcp-moldova-tenders

Moldova Government Procurement (MTender) MCP — keyless.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool	Description
`moldova_recent_tenders`	Most recent government procurement tenders from Moldova's national e-procurement platform (MTender), published as Open Contracting (OCDS) data. Returns each tender with ocid, title, buyer (procuring entity), value + currency (MDL), status, CPV classification, and publication/period dates. Titles and descriptions are in Romanian. Use moldova_get_tender for the full detail of one tender.
`moldova_get_tender`	Full detail for a single Moldova (MTender) government procurement tender by its OCDS contracting id (ocid, e.g. "ocds-b3wdp1-MD-1539840280133"). Returns title, description, buyer/procuring entity, value + currency, status, procurement method and category, CPV classification, tender period dates, budget, and parties. Get an ocid from moldova_recent_tenders or moldova_search_tenders.
`moldova_search_tenders`	Keyword search over recent Moldova (MTender) government procurement tenders. Scans the most recent tenders and returns those whose title, buyer, or CPV description contains the query (case-insensitive; Romanian text). Note: this is a client-side filter over recent tenders (MTender has no native full-text search), so it matches recent listings only. Returns shaped tenders like moldova_recent_tenders.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "moldova-tenders": {
      "url": "https://gateway.pipeworx.io/moldova-tenders/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/moldova-tenders/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Moldova Tenders data" })

The gateway picks the right tool and fills the arguments automatically.

License

MIT

Moldova Tenders