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.

io.github.CloudCorpRecords/procureport

NPM · @RENETURCIOS/PROCUREPORT · 2 COMPONENTS

Korean public procurement: bids, awards, contracts, statistics, products and mall search.

64 Trust /100

Last scanned (8 hours ago)

Scores higher than 31% 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 811 tokens (~54/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 49

    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/@reneturcios/procureport@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~811 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
call_api_with_pagination_support ~118

Call any service operation repeatedly with paging and aggregate the items across pages for bulk exploration.

NameTypeReqDescription
max_pagesnumber–Maximum number of pages to fetch, defaults to 5.
operationstringyesOperation name to call.
page_sizenumber–Number of items per page, defaults to 100.
paramsobject–Additional parameters to pass to the operation.
servicestringyesAPI service ID, such as public_data_standard, procurement_statistics, product_list, or shopping_mall.

No output schema declared.

No examples provided.

call_procurement_statistics_api ~56

Call the procurement statistics API (14 operations) with an operation and parameters.

NameTypeReqDescription
operationstringyesOperation name to call on the procurement statistics API.
paramsobject–Additional parameters to pass to the operation.

No output schema declared.

No examples provided.

call_product_list_api ~59

Call the product list API (12 operations) for the product catalogue with an operation and parameters.

NameTypeReqDescription
operationstringyesOperation name to call on the product list API.
paramsobject–Additional parameters to pass to the operation.

No output schema declared.

No examples provided.

call_public_data_standard_api ~62

Call the public data standard API for bid notices, awards, and contracts with an operation and parameters.

NameTypeReqDescription
operationstringyesOperation name to call on the public data standard API.
paramsobject–Additional parameters to pass to the operation.

No output schema declared.

No examples provided.

call_shopping_mall_api ~57

Call the shopping mall API (9 operations) with an operation and parameters.

NameTypeReqDescription
operationstringyesOperation name to call on the shopping mall API.
paramsobject–Additional parameters to pass to the operation.

No output schema declared.

No examples provided.

crawl_list ~62

Query the product list, optionally filtered by a search query, with paging.

NameTypeReqDescription
pagenumber–Page number to return.
page_sizenumber–Number of items per page.
querystring–Search query text to filter the product list.

No output schema declared.

No examples provided.

get_all_api_services_info ~30

List all API services and their operations from the built-in catalogue, without calling the upstream API.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_api_operations ~50

List the operations available for one API service from the built-in catalogue.

NameTypeReqDescription
servicestringyesAPI service ID, such as public_data_standard, procurement_statistics, product_list, or shopping_mall.

No output schema declared.

No examples provided.

get_data_exploration_guide ~33

Return a guide to exploring the procurement data: which services and tools to use, in what order.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_detailed_attributes ~33

Fetch the detailed attributes for a single product by its product identifier.

NameTypeReqDescription
product_idstringyesProduct identifier.

No output schema declared.

No examples provided.

get_procurement_statistics_by_year ~44

Get procurement statistics for a single year.

NameTypeReqDescription
yearnumberyesYear to get statistics for, as an integer between 1900 and 2100.

No output schema declared.

No examples provided.

get_recent_bid_announcements ~70

Get recent bid announcements over an automatically computed recent period, optionally for one business type.

NameTypeReqDescription
business_typestring–Business type name or code, such as goods, services, construction, or foreign.
daysnumber–Number of recent days to include, defaults to 7.

No output schema declared.

No examples provided.

get_successful_bids_by_business_type ~62

Get successful bids (awards) for a business type; a Korean business-type name is converted to its code automatically.

NameTypeReqDescription
business_typestringyesBusiness type name or code, such as goods, services, construction, or foreign.

No output schema declared.

No examples provided.

search_shopping_mall_products ~50

Search shopping mall products by name, optionally narrowed to one company.

NameTypeReqDescription
companystring–Company name to narrow results to.
querystringyesProduct name to search for.

No output schema declared.

No examples provided.

server_info ~25

Return information about this server and the tools it offers, without calling the upstream API.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/procureport MCP server?

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

npm · @reneturcios/procureport

# add to Claude Code
claude mcp add cloudcorprecords-procureport -- npx -y @reneturcios/procureport
Common questions

What is the io.github.CloudCorpRecords/procureport MCP server?

io.github.CloudCorpRecords/procureport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/procureport. Korean public procurement: bids, awards, contracts, statistics, products and mall search. This page covers its npm package (@reneturcios/procureport).

Is the io.github.CloudCorpRecords/procureport MCP server safe to use?

io.github.CloudCorpRecords/procureport scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/procureport MCP server expose?

io.github.CloudCorpRecords/procureport exposes 15 tools: crawl_list, get_detailed_attributes, server_info, call_public_data_standard_api, call_procurement_statistics_api, and 10 more. Their descriptions and schemas cost roughly 811 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/procureport MCP server still maintained?

io.github.CloudCorpRecords/procureport 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 io.github.CloudCorpRecords/procureport MCP server under?

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