Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Idb

NPM · @PIPEWORX/MCP-IDB · 2 COMPONENTS

IDB (Inter-American Development Bank) Procurement MCP.

+3 this week 82 Trust /100

Last scanned (11 hours ago)

Scores higher than 72% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-idb). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1063 tokens (~265/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 2 Nov 26 −26
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
    • Dependency health: pass → unverified ▼ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 1 Nov 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 30 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 79

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-idb@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-idb
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-idb/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637404921
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:77a02c76c02c4f088c2cffdb64b76d3c7333607e01d2c8f015868b3515917965dae36b43a46854ad6ff69cd89ac30ab0fba984016b3d6acb5733a689d

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~1,011 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
idb_check_mdb_debarment ~304

Check whether a person or firm name appears on the multilateral development bank cross-debarment list — IDB's own debarment/sanctions list PLUS the cross-debarred lists of the World Bank Group, Asian Development Bank, African Development Bank, and EBRD, which the five banks mutually enforce. Answers "is this vendor debarred" for procurement due-diligence. Matching is accent- and case-insensitive (handles Spanish/Portuguese diacritics like "González" vs "Gonzalez") and requires every word of the query name to appear in a record — so a full name narrows results, a bare surname broadens them. Returns each match's entity type, nationality, sanction dates, prohibited practice, and which bank's list it came from. Keyless, ~1,300 records, queried live.

NameTypeReqDescription
entity_typestring–Optional filter: "Individual" or "Firm".
limitnumber|string–Max matches to return (1-50). Default 10.
namestringyesPerson or firm name to check, e.g. "Ricardo Reynoso Gonzalez" or "Consultora Tecnodinamica". Accents optional.
sourcestring–Optional filter to one issuing bank, e.g. "IDB", "WBG", "ADB", "AfDB", "EBRD" (partial match against the source label).

No output schema declared.

No examples provided.

idb_get_notice ~110

Fetch one IDB procurement notice by its notice id (from idb_search_notices results). Returns the full record: project, loan number, sector, procurement method, publication date, deadline, and the document URL on idbdocs.iadb.org. If the id has multiple entries (amendments/re-publications), all are returned newest-first.

NameTypeReqDescription
notice_idstringyesIDB notice id, e.g. "38846" — find ids via idb_search_notices.

No output schema declared.

No examples provided.

idb_search_awards ~258

Search Inter-American Development Bank (IDB) contract award data — which firms and individual consultants were awarded contracts under IDB-financed projects, with contract amount, sector, borrower country, and dates. ~159,000 awards. Filter by country, awarded firm name, sector, and contract year. Note: many individual-consultant contracts record the firm as "Not Available" by design (the consultant is not a named firm). Keyless, queried live against the same data as IDB's 70MB awards CSV — no download needed.

NameTypeReqDescription
countrystring–Borrowing country, e.g. "Colombia", "Bolivia", "Ecuador". Partial/case-insensitive match.
firmstring–Awarded firm name (partial/case-insensitive), e.g. "Deloitte", "Odebrecht".
keywordstring–Keyword against the project name.
limitnumber|string–Max awards to return (1-50). Default 15.
sectorstring–Sector keyword, e.g. "Rural Electrification", "Health Services", "Water Supply".
yearnumber|string–Contract signature year, e.g. 2025.

No output schema declared.

No examples provided.

idb_search_notices ~339

Search Inter-American Development Bank (IDB) project procurement notices — live bidding notices, expressions of interest, general/specific procurement notices, and contract-award notifications for IDB-financed projects across 26 Latin American and Caribbean countries. Filter by country, sector, and keyword; defaults to open notices only (deadline not yet passed) sorted soonest-first. Each result carries the notice id, project, deadline, and a document URL. Keyless, ~37,000 notices, queried live.

NameTypeReqDescription
countrystring–Country name, e.g. "Peru", "Ecuador", "Jamaica". Partial/case-insensitive match. Omit for all LAC countries.
keywordstring–Full-text keyword against the notice title and project name, e.g. "road rehabilitation", "software licenses".
limitnumber|string–Max notices to return (1-50). Default 15.
open_onlyboolean–Restrict to notices whose deadline has not passed (default true). Set false to include closed/expired notices too, or when type is "award" (awards have no future deadline).
sectorstring–Sector keyword, e.g. "Energy", "Health", "Transport", "Water". Partial/case-insensitive match against the English sector name.
typestring–Notice type filter: "specific" (specific procurement notice), "general" (general procurement notice), "eoi" (expression of interest), "award" (contract award notification), or "rfi" (request for info…

No output schema declared.

No examples provided.

Install

How do I install the Idb MCP server?

Idb runs locally as an npm package, launched with npx -y @pipeworx/mcp-idb. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-idb

# add to Claude Code
claude mcp add pipeworx-io-idb -- npx -y @pipeworx/mcp-idb
Common questions

What is the Idb MCP server?

Idb is an MCP server listed in the public MCP registry as io.github.pipeworx-io/idb. IDB (Inter-American Development Bank) Procurement MCP. This page covers its npm package (@pipeworx/mcp-idb).

Is the Idb MCP server safe to use?

Idb scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Idb MCP server expose?

Idb exposes 4 tools: idb_search_notices, idb_get_notice, idb_search_awards, idb_check_mdb_debarment. Their descriptions and schemas cost roughly 1,011 tokens of context every time the server is loaded.

Is the Idb MCP server still maintained?

Idb is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Idb MCP server under?

Idb declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.