io.github.fieldcure/publicdata-kr
NUGET · FIELDCURE.MCP.PUBLICDATA.KR
Korean public data API gateway for discovering and calling data.go.kr APIs from MCP clients.
Available components
Last scanned (22 hours ago)
Scores higher than 88% of NuGet servers
Category Search and Retrieval
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 & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 162 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 521 tokens (~173/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 −1
- Stability: pass → 0.93 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 −3
- Stability: pass → 0.80 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 4 Nov 2026 · Analysed nuget/FieldCure.Mcp.PublicData.Kr@1.0.3
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | nuget |
| Reason | Signature present, unverified |
Signer
| Signed as | Author signature |
|---|---|
| Subject | CN=Fieldcure Co.\, Ltd.,O=Fieldcure Co.\, Ltd.,L=Seongbuk-gu,ST=Seoul,C=KR |
| Issuer | CN=GlobalSign GCC R45 CodeSigning CA 2020,O=GlobalSign nv-sa,C=BE |
| Valid from | 17 Jan 2024 |
| Valid until | 17 Jan 2027 |
Countersigner
| Signed as | Repository signature, names nuget.org |
|---|---|
| Subject | CN=NuGet.org Repository by Microsoft,O=NuGet.org Repository by Microsoft,L=Redmond,ST=Washington,C=US |
| Issuer | CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1,O=DigiCert\, Inc.,C=US |
| Valid from | 23 Feb 2024 |
| Valid until | 18 May 2027 |
| Service index | https://api.nuget.org/v3/index.json |
| Owners | FieldCure |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
Registry declarations For information only
What the registry and the package's own manifest say about this version. The publisher or the registry writes these, nothing here is verified, and none of it affects the score.
| Repository | https://github.com/fieldcure/fieldcure-mcp-publicdata |
|---|---|
| Repository type | git |
| Commit | 33b5448a590d910a7fab908dec26912ef3a654d3 |
| Project URL | https://github.com/fieldcure/fieldcure-mcp-publicdata |
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 →
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.
How do I install the io.github.fieldcure/publicdata-kr MCP server?
io.github.fieldcure/publicdata-kr runs locally as a NuGet package, launched with dnx FieldCure.Mcp.PublicData.Kr@1.0.3 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · FieldCure.Mcp.PublicData.Kr
claude mcp add fieldcure-publicdata-kr -- dnx FieldCure.Mcp.PublicData.Kr@1.0.3 --yes
What is the io.github.fieldcure/publicdata-kr MCP server?
io.github.fieldcure/publicdata-kr is an MCP server listed in the public MCP registry as io.github.fieldcure/publicdata-kr. Korean public data API gateway for discovering and calling data.go.kr APIs from MCP clients. This page covers its NuGet package (FieldCure.Mcp.PublicData.Kr).
Is the io.github.fieldcure/publicdata-kr MCP server safe to use?
io.github.fieldcure/publicdata-kr scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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.fieldcure/publicdata-kr MCP server expose?
io.github.fieldcure/publicdata-kr exposes 3 tools: discover_api, describe_api, call_api. Their descriptions and schemas cost roughly 521 tokens of context every time the server is loaded.
Is the io.github.fieldcure/publicdata-kr MCP server still maintained?
io.github.fieldcure/publicdata-kr is still listed as active in the MCP registry. We last reached this channel on 4 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.fieldcure/publicdata-kr MCP server under?
io.github.fieldcure/publicdata-kr declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.