Paraguay Dncp

Name: Paraguay Dncp
Author: pipeworx-io

Server Details

Paraguay DNCP MCP — Paraguay government procurement / public contracts (keyless).

The last two health checks of this connector failed. 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
Uptime: 18.6% over 63 days
Last Tested: 2026-10-19 09:28
Transport: Streamable HTTP
URL
Repository: pipeworx-io/mcp-paraguay-dncp
GitHub Stars: 0
Server Listing: mcp-paraguay-dncp

TDQS

A3.9/5.0

Scored 2026-10-07 00:11 across 38 tools

Disambiguation3/5

Descriptions work hard to delineate usage, but the set contains genuine overlap: ask_pipeworx, ask_pipeworx_beta (explicitly the 'identical' router), ask_pipeworx_grounded, and deep_research all answer questions by routing to the same catalog, and discover_tools/suggest_questions are also meta-entry points. Company tools (entity_profile, company_facts, compare_entities, recent_changes) and the prediction-market cluster (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, polymarket_kalshi_spread) overlap enough that misselection is plausible despite the verbose guidance.

Naming Consistency4/5

Everything is snake_case, which is consistent, and provider-namespaced tools (polymarket_*, kalshi_*, paraguay_*, pipeworx_*) are predictable. Minor deviations exist in style — bare verbs (remember, recall, forget, subscribe, unsubscribe) versus noun phrases (entity_profile, company_facts) versus verb_noun — but the pattern stays readable.

Tool Count2/5

38 tools is well past the heavy threshold and, more importantly, is mismatched to the server's stated scope: 'Paraguay Dncp' has only two Paraguay-specific tools while the other 36 are a generic cross-domain Pipeworx catalog. For a single-country procurement API, this is an extreme surface-to-purpose mismatch.

Completeness3/5

The actual DNCP domain is covered by just search_tenders + get_record, a read-only surface that is arguably complete for public procurement data but thin (no supplier/buyer entity lookup, and search relies on a client-side filter since the API has no free-text parameter). Assessed as the whole toolset, coverage of unrelated domains is broad but shallow relative to the server's name.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

29 tool updatesOct 7, 2026

Changedai_visibility_check1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "entity": "Tesla"
+  }
+]
```

Changedask_pipeworx3 fields changed

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Changedask_pipeworx_beta4 fields changed

addedInput schema / examples

Added value: +[
+  {
+    "question": "What is the current US unemployment rate?"
+  }
+]

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Changedask_pipeworx_grounded4 fields changed

addedInput schema / examples

Added value: +[
+  {
+    "question": "What was Apple's fiscal 2023 revenue?"
+  }
+]

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Your question in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Addedcompany_facts

Changedcompare_entities1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "type": "company",
+    "values": [
+      "AAPL",
+      "MSFT"
+    ]
+  }
+]

Changeddeep_research9 fields changed

addedInput schema / examples

Added value: +[
+  {
+    "depth": "quick",
+    "question": "What is the current US unemployment rate and how has it changed over the past year?"
+  }
+]

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / input

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / prompt

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / q

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"The research question, in natural language. Broad/multi-part is fine — decomposition is the point."New value: +"The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases."

addedInput schema / properties / text

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Changedentity_profile1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Changedforget4 fields changed

addedInput schema / properties / k

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

changedInput schema / properties / key / description

Previous value: -"Memory key to delete"New value: +"Memory key to delete. Accepts name, k, label as aliases."

addedInput schema / properties / label

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Changedgenerate_llms_txt1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "url": "https://pipeworx.io"
+  }
+]

Addedkalshi_weather_edge

Changedpipeworx_feedback1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "message": "Fleet #2184 smoke test: verifying pipeworx_feedback example call returns non-empty.",
+    "type": "other"
+  }
+]

Changedpipeworx_trending1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "window": "7d"
+  }
+]
```
Changedpolymarket_arbitrage1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "topic": "Fed rate decision"
+  }
+]
```
Changedpolymarket_edge_tracker1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "days": 14,
+    "window": "1wk"
+  }
+]
```

Changedpolymarket_edges3 fields changed

addedInput schema / examples

Added value: +[
+  {
+    "limit": 5,
+    "window": "1wk"
+  }
+]

changedInput schema / properties / min_edge_pp / description

Previous value: -"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage."New value: +"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage and Polymarket's own taker fee."

changedInput schema / properties / slippage_pp / description

Previous value: -"Assumed execution slippage in percentage points per leg (default 0.3). Subtracted from raw |edge| before ranking and Kelly sizing. Polymarket has zero trading fees as of 2024 but bid/ask + thin depth typically eats 20-50bp per trade. Bump for very thin partitions; drop to 0 if you have a smarter fill model."New value: +"Assumed execution slippage in percentage points per leg (default 0.3), for bid/ask + thin depth cost that a last-trade price does not show. Subtracted from raw |edge| before ranking and Kelly sizing, ON TOP OF Polymarket's own taker fee — which is NOT zero (rate 0.04-0.07 depending on category, read off each market's own published fee schedule; see fees_pp_applied on every row and fees.ts for the full schedule). Bump slippage for very thin partitions; drop to 0 if you have a smarter fill model — the fee still applies regardless."

Changedpolymarket_fill_risk1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "market": "will-the-fed-increase-interest-rates-by-25-bps-after-the-december-2026-meeting-20260729232808636",
+    "side": "buy_yes",
+    "size_usd": 1000
+  }
+]

Changedrecall4 fields changed

addedInput schema / properties / k

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

changedInput schema / properties / key / description

Previous value: -"Memory key to retrieve (omit to list all keys)"New value: +"Memory key to retrieve (omit to list all keys). Accepts name, k, label as aliases."

addedInput schema / properties / label

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Changedrecent_changes1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "since": "30d",
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Addedrelease_calendar_markets

Changedremember10 fields changed

addedInput schema / examples

Added value: +[
+  {
+    "key": "target_ticker",
+    "value": "AAPL"
+  }
+]

addedInput schema / properties / content

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

addedInput schema / properties / data

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

addedInput schema / properties / k

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

changedInput schema / properties / key / description

Previous value: -"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\")"New value: +"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\"). Accepts name, k, label as aliases."

addedInput schema / properties / label

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

addedInput schema / properties / text

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

addedInput schema / properties / v

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

changedInput schema / properties / value / description

Previous value: -"Value to store (any text — findings, addresses, preferences, notes)"New value: +"Value to store (any text — findings, addresses, preferences, notes). Accepts content, text, data, v as aliases; a non-string value is stored as JSON."

Addedresolution_audit
Addedresolution_diff

Changedresolve_entity1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Changedscan_competitor_ai_presence1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "entities": [
+      "Pipeworx",
+      "Zapier"
+    ]
+  }
+]

Changedscan_dependency1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "package": "left-pad"
+  }
+]
```

Changedsearch_within1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "query": "supply-chain risk",
+    "text": "Apple Inc. reported fiscal 2023 revenue of $383.285 billion, driven by strong iPhone and Services growth. Net income was $96.995 billion. The company faced supply-chain risk in China during the quarter."
+  }
+]

Changedsuggest_questions1 field changed
- addedInput schema / examples
```
Added value: +[
+  {
+    "topic": "finance"
+  }
+]
```

Changedvalidate_claim1 field changed

addedInput schema / examples

Added value: +[
+  {
+    "claim": "Apple's fiscal 2023 revenue was $383 billion"
+  }
+]

1 tool updateSep 12, 2026

Changedbet_research2 fields changed

changedInput schema / examples

Previous 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"
+  }
+]

changedInput schema / properties / market / description

Previous 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 updatesSep 11, 2026

Changedbet_research2 fields changed

changedInput schema / examples

Previous 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"
+  }
+]

changedInput schema / properties / market / description

Previous 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."

Changedpolymarket_kalshi_spread2 fields changed

changedInput schema / examples

Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]

changedInput schema / properties / topic / description

Previous 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."

1 tool updateSep 3, 2026

Changedentity_profile3 fields changed

changedInput schema / properties / type / description

Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."

changedInput schema / properties / type / enum

Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]

changedInput schema / properties / value / description

Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."

1 tool updateSep 1, 2026

Changedresolve_entity1 field changed

changedInput schema / properties / value / description

Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."

Related MCP Connectors

Brazil Pncp A
io.github.pipeworx-io
Brazil PNCP MCP — Brazilian government procurement (keyless).
Government Data Open Data
2
Chile Procurement A
io.github.pipeworx-io
Chile Government Procurement MCP — Mercado Público / ChileCompra (keyless-ish).
Government Data Open Data
2
Ecuador Procurement A
io.github.pipeworx-io
Ecuador Government Procurement MCP — SERCOP / Compras Públicas (keyless).
Government Data Open Data
432
Taiwan Procurement A
io.github.pipeworx-io
Taiwan Government Procurement MCP — 政府電子採購網 (PCC) tenders (keyless).
Government Data Open Data
452

Related MCP Servers

mcp-contrataciones-py
App Automation Government Data Open Data
ricarcya
A
license
B
quality
B
maintenance
Enables AI agents to query Paraguay's public procurement data via the official DNCP API v3 (OCDS), including tender processes, awards, contracts, suppliers, contracting entities, product catalog, and visualizations.
Updated 2 months ago (2026-08-29 19:25 UTC)
17
MIT
seace-mcp
Government Data Open Data
pipaacebedo
A
license
A
quality
B
maintenance
Enables local, credential-free searching and reading of Peru's public procurement system—including selection processes, contracts, documents, and annual procurement plans—through MCP tools, returning clean data and direct download URLs without storing files.
Updated 13 days ago (2026-10-06 23:15 UTC)
25
1
Apache 2.0
secop-mcp-server
Government Data Open Data
juandavidsernav
A
license
A
quality
D
maintenance
An MCP server to query Colombian public procurement data from SECOP I and II in real time, enabling contract research, transparency oversight, and data journalism.
Updated 7 months ago (2026-03-15 17:12 UTC)
10
2
MIT
MCP Compras Públicas Brasil
Government Data Open Data
LeonardoDiasRR
F
license
C
quality
B
maintenance
Enables read-only access to official Brazilian government procurement data from Compras.gov.br and the PNCP, covering all cataloged public GET endpoints through MCP tools.
Updated a month ago (2026-09-09 00:35 UTC)
175
1
-