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.

Portugal Tenders

NPM · @PIPEWORX/MCP-PORTUGAL-TENDERS · 2 COMPONENTS

Portugal public procurement MCP -- IMPIC (Instituto dos Mercados Públicos, do Imobiliário e da…

+3 this week 82 Trust /100

Last scanned (10 hours ago)

Scores higher than 72% of npm servers

Category E-commerce

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-portugal-tenders). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1064 tokens (~266/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
    • Stability: 0.17 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 3 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 2 Nov 26 +1

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

  • 1 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 31 Oct 26 +1

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

  • 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-portugal-tenders@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-portugal-tenders
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-portugal-tenders/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3691854154
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:7ac90beb4d57a1e7d0344ef2fef08a6922477227b30c9560bc117c772b01e60a07f94ef5ed7b7636539dd9f90fc0decdc6f6888866b8aa74ca6f9ad45

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,009 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
pt_announcement_detail ~105

Fetch one PORTUGUESE tender announcement by the internal "id" returned from pt_announcement_search. Returns the full record: IMPIC notice id, buyer (with NIF tax number), notice type, contract type(s), procedure model, base amount, CPV codes, lot descriptions, publish date, proposal deadline and window, and a link to the official notice document.

NameTypeReqDescription
idnumber|stringyesThe announcement's internal id, from pt_announcement_search.

No output schema declared.

No examples provided.

pt_announcement_search ~429

Search PORTUGUESE public-procurement tender ANNOUNCEMENTS (contract notices) published through Portal BASE (base.gov.pt), run by IMPIC (Instituto dos Mercados Públicos, do Imobiliário e da Construção). IMPIC's own live API needs registration and a token Pipeworx does not hold yet, so this answers from a refreshed recent-window dataset (see data_as_of and the window fields in the response). Filter by free-text keyword (matched against the Portuguese notice title), CPV classification code or prefix (e.g. "45" for construction, "72000000" for IT services), contracting-authority (buyer) name substring (Portuguese spelling, e.g. "Câmara Municipal", "Instituto"), and a publish-date range. Returns compact shaped notices: id, IMPIC notice id, buyer, title, notice type, contract type(s), base amount (EUR), CPV, publish date, and proposal deadline. Call pt_announcement_detail with the returned id for the full record.

NameTypeReqDescription
buyerstring–Contracting-authority (buyer) name, partial match, Portuguese spelling, e.g. "Câmara Municipal de Lisboa", "Instituto", "Universidade".
cpvstring–CPV classification code or numeric prefix, e.g. "45" (construction works), "72000000" (IT services).
date_fromstring–Earliest PUBLISH date, YYYY-MM-DD. Defaults to 90 days before date_to.
date_tostring–Latest PUBLISH date, YYYY-MM-DD. Defaults to the newest date in the loaded window (see ann_window_to in any response), which can trail today because IMPIC publishes per-year bulk files.
limitnumber|string–Max notices to return (default 20, max 100). Newest-first.
querystring–Keyword(s), case-insensitive, matched against the Portuguese notice title, e.g. "limpeza", "software", "obras", "manutenção".

No output schema declared.

No examples provided.

pt_contract_detail ~111

Fetch one PORTUGUESE awarded contract by its "idcontrato" (returned from pt_contract_search). Returns the full record: buyer and supplier (with NIF tax numbers), full title and description, amount, base procurement price, CPV codes, execution deadline, execution location(s), procedure type, publish/signing/decision dates, and the legal regime cited.

NameTypeReqDescription
idcontratostringyesThe contract's id, e.g. "12026866". Returned by pt_contract_search.

No output schema declared.

No examples provided.

pt_contract_search ~364

Search PORTUGUESE public-procurement AWARDED CONTRACTS published through Portal BASE (base.gov.pt), run by IMPIC. Filter by free-text keyword (matched against the Portuguese contract title), buyer (adjudicante/contracting-authority) name substring, supplier (adjudicatário/awarded contractor) name substring, contract-amount range (EUR), and a publish-date range. Returns compact shaped contracts: contract id, title, buyer, supplier, amount (EUR), contract type(s), CPV, publish date, and the contract-signing date. Call pt_contract_detail with the returned idcontrato for the full record.

NameTypeReqDescription
amount_maxnumber|string–Maximum contract amount in EUR.
amount_minnumber|string–Minimum contract amount in EUR.
buyerstring–Contracting-authority (buyer/adjudicante) name, partial match, Portuguese spelling, e.g. "Câmara Municipal do Porto", "Ministério".
date_fromstring–Earliest PUBLISH date, YYYY-MM-DD. Defaults to 90 days before date_to.
date_tostring–Latest PUBLISH date, YYYY-MM-DD. Defaults to the newest date in the loaded window (see contract_window_to in any response).
limitnumber|string–Max contracts to return (default 20, max 100). Newest-first.
querystring–Keyword(s), case-insensitive, matched against the Portuguese contract title, e.g. "pavimentação", "formação", "software".
supplierstring–Awarded supplier (adjudicatário) name, partial match, e.g. "Mota-Engil", "Altice".

No output schema declared.

No examples provided.

Install

How do I install the Portugal Tenders MCP server?

Portugal Tenders runs locally as an npm package, launched with npx -y @pipeworx/mcp-portugal-tenders. 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-portugal-tenders

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

What is the Portugal Tenders MCP server?

Portugal Tenders is an MCP server listed in the public MCP registry as io.github.pipeworx-io/portugal-tenders. Portugal public procurement MCP -- IMPIC (Instituto dos Mercados Públicos, do Imobiliário e da… This page covers its npm package (@pipeworx/mcp-portugal-tenders).

Is the Portugal Tenders MCP server safe to use?

Portugal Tenders 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 Portugal Tenders MCP server expose?

Portugal Tenders exposes 4 tools: pt_announcement_search, pt_announcement_detail, pt_contract_search, pt_contract_detail. Their descriptions and schemas cost roughly 1,009 tokens of context every time the server is loaded.

Is the Portugal Tenders MCP server still maintained?

Portugal Tenders 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 Portugal Tenders MCP server under?

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