io.github.fieldcure/publicdata-kr
NUGET · FIELDCURE.MCP.PUBLICDATA.KR · SCANNED AUG 3
Korean public data API gateway for discovering and calling data.go.kr APIs from MCP clients.
Available components
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 →
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 & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 69 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
nuget · FieldCure.Mcp.PublicData.Kr
claude mcp add fieldcure-publicdata-kr -- dnx [email protected] --yes
codex mcp add fieldcure-publicdata-kr -- dnx [email protected] --yes
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fieldcure-publicdata-kr": {
"type": "local",
"command": [
"dnx",
"[email protected]",
"--yes"
],
"enabled": true
}
}
} mcp_servers:
fieldcure-publicdata-kr:
command: "dnx"
args: ["[email protected]", "--yes"] {
"mcpServers": {
"fieldcure-publicdata-kr": {
"command": "dnx",
"args": [
"[email protected]",
"--yes"
]
}
}
} 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.
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 0
- Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
- 26 Jul 26 47
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed nuget/[email protected]
Provenance none
Ecosystem: nuget · Outcome: none
Reason: nuget_signature_unverified
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
call_api ~285
Call a Korean public data API with automatic serviceKey injection. WORKFLOW: always discover_api → describe_api → call_api. Do NOT call this tool with a serviceId from discover_api; call_api takes a full 'url' string returned by describe_api under operations[].url, NOT a serviceId. The 'params' argument is a JSON STRING (not an object), e.g. params="{\"pageNo\":\"1\",\"numOfRows\":\"5\"}". If the call fails with ACCESS_DENIED, the user needs to apply for access to this specific API at data.go.kr.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | integer | — | Max items to return (default: 20, prevents context overflow) |
| params | string|null | — | Query parameters as a JSON STRING (serialized object, not a raw object), with string values only. Example: '{"pageNo":"1","numOfRows":"5","type":"json"}'. Parameter names come from describe_api's req… |
| url | string | yes | Full endpoint URL from describe_api's operations[].url. Do NOT pass a serviceId / service_id from discover_api — that is for describe_api, not for this tool. A valid url looks like 'http://apis.data.… |
No output schema declared.
No examples provided.
describe_api ~89
Get the request parameters and response schema of a specific data.go.kr API. Input is the serviceId from discover_api results. Returns operations[].url and request_parameters[] — these are the required inputs for call_api. Always call this between discover_api and call_api; never pass a serviceId directly to call_api.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | Service ID (list_id) from discover_api results |
No output schema declared.
No examples provided.
discover_api ~147
Search Korean public data APIs on data.go.kr by keyword. Returns API names, descriptions, providers, and serviceIds. Use this when the user asks about Korean government data. WORKFLOW: the returned serviceId is the input for describe_api (not call_api). Always follow up with describe_api to get the actual endpoint url and parameter schema before calling call_api.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | — | Page number (default: 1) |
| pageSize | integer | — | Results per page (default: 10, max: 50) |
| query | string | yes | Search keyword in Korean or English (e.g., '미세먼지', '부동산', '사업자') |
No output schema declared.
No examples provided.