GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud
Mcportal
Overview
Description from the maker (original English)
Quota-guarded MCP layer over Korean public data APIs (data.go.kr), compiled from OpenAPI specs
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new↓ 66/wk · ★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- PyPIPython’s uv installed (for the uvx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"mcportal": {
"command": "uvx",
"args": [
"mcportal"
]
}
}
}Run this in your terminal
claude mcp add mcportal -- uvx mcportalOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mcportal": {
"command": "uvx",
"args": [
"mcportal"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"mcportal": {
"type": "stdio",
"command": "uvx",
"args": [
"mcportal"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account yonghwan1106, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 5571 servers in this category
- Published to the registry more recently than 30% of the other 5571 servers in this category
- Basic checks equal to or better than 100% of the other 5571 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Mcportal safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.2.2) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
MCP server for terminal commands, file operations, and process management
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCPortal
The missing bridge between data.go.kr and the global MCP ecosystem. MCPortal normalizes Korean public-API specifications into standard OpenAPI 3.1, compiles them into MCP servers, and puts every outbound call behind a hard daily budget with backoff and caching. Fully open source, fully self-hosted.
한국어 문서: README.ko.md — this English README is the canonical document and the Korean file is a translation of it.
Accuracy disclaimer
data.go.kr publishes no "remaining quota" endpoint. MCPortal's usage ledger
therefore counts only the calls that went through MCPortal, which makes it
a best-effort estimate. Calls that the same
serviceKeyspends outside
MCPortal — another script, the portal console, a different tool — never reach
the ledger, so the ledger value is always a lower-bound approximation of real
consumption. The axis of trust is not that estimate but the **hard budget cap
(
CALL_BUDGET)**. Even when the ledger is wrong, the hard guard physically
blocks calls beyond the daily cap, so the safety line against quota-related
account sanctions always comes from
CALL_BUDGET.
The no-key boundary
| Works without any API key | Needs a data.go.kr service key |
|---|---|
| Replaying record/replay cassettes | Live API calls |
The full test suite (pytest), including the record-mode tests, which run on synthetic transports | Live response sampling |
Standing up an MCP server from a committed spec plus its cassette (mcportal serve --replay) — from a repo checkout, or from a PyPI install pointed at one (note 1) | Ad-hoc conversion of an API that has no cassette yet |
Regenerating the compile demo (examples/compile_demo.py) | Recording new cassettes |
Regenerating and listing the preset bundles (mcportal compile / mcportal presets) — bundled in the wheel since 0.2.0 (note 1) | Sampling a response schema that is still unresolved (mcportal sample) |
Reading quota status (mcportal quota status) | The key-dependent benchmark items K1–K3 |
Running the benchmark harness (the five key-free items in benchmarks/PROTOCOL.md) | — |
Every demo, development and CI path in MCPortal runs without a key. The record/replay layer replays cassettes that were recorded earlier, so the same response flow can be reproduced and the whole test suite can go green with no serviceKey present. Spec-to-MCP conversion has already happened at build time — the compiled artifacts are committed under specs/ — so clone the repository and even standing up an MCP server and answering tool calls needs no key: mcportal serve 15000115 --replay serves eight tools over stdio with no serviceKey anywhere in the environment.
That sentence says *clone* on purpose. Replay needs a cassette, and cassettes are recorded upstream responses that stay in the repository instead of going out in the wheel (note 1), so a bare pip install mcportal has nothing to replay until it is pointed at a checkout with --presets-root or MCPORTAL_PRESETS= . Cassettes exist for three of the four bundles — 15081808 has none in the repository either, because it was deliberately left out of sampling (see *Presets* below), so that one bundle is live-only.
What does need a key is narrow: live traffic to data.go.kr, and sampling or converting an API that has no cassette yet.
Note 1 — what the wheel carries, and what it does not.
Since 0.2.0, the published wheel carries the four preset bundles (16 bundle
files plus the two
presets/documents, measured on the built artifact), so a
plain
pip install mcportalcan runmcportal presetswith no checkout.
Since 0.2.2 the wheel also carries the three
sampled_schemas.jsonfiles
—
15000115,15101612and15102108;15081808has none, because it was
deliberately left out of sampling. They ship because `mcportal compile
--check
needs them:--check` does not diff files, it re-synthesizes
openapi.jsonfrom its source + curation + sampled layers, so without the
sampled layer an installed copy cannot reproduce the very
openapi.jsonit
shipped. On 0.2.1 as published,
compile --checkfrom a plain install reports
3 of 4 drifted and exits 3 (measured 2026-08-15); on that version pass
--presets-root /presets. 0.2.2 restores it to 4 of 4 matched,
exit 0, from the install alone.
Those three files carry only the **field names and types inferred from the
responses** — zero response values — and that structure already ships inside
openapi.json, so nothing is exposed that the wheel did not already carry.
What the wheel still leaves out is the recorded upstream traffic itself:
`cassettes/` and `samples/` stay in the repository only, which is why
mcportal serve --replayis a checkout path. To use a different bundle set —
or to give a PyPI install the cassettes — point MCPortal at a checkout with
--presets-rootor the environment variableMCPORTAL_PRESETS=.
When
mcportal presetsfinds no bundle it prints the paths it searched.
Key-free reproduction walkthrough
# 1) Compile a spec from synthetic fixtures (zero network, zero credentials).python examples/compile_demo.py
-> specs/demo/openapi.json + specs/demo/samples/*.json
Re-running produces byte-identical output; the determinism check is
built into the script.
2) Stand up an MCP server over stdio from a committed bundle (no key).
Needs the [mcp] extra. --replay reads presets/ /cassettes/ .json,
which exists for 15000115, 15101612 and 15102108; 15081808 has none.
mcportal serve 15000115 --replay
-> 8 tools over stdio, zero credentials. On a PyPI install add
--presets-root /presets (note 1).
#
The same thing without the CLI, against any spec plus any cassette:
python -c "from mcportal.mcp import build_server; \ build_server('specs/demo/openapi.json', mode='replay', \ cassette_path=' ')"
specs/demo/ commits the spec and the samples, not a cassette, so
must point at one you recorded yourself. That a server
really stands up and answers a tool call without a key is proven by the
last case in tests/test_mcp_wiring.py, which builds a synthetic cassette
in tmp_path. presets/ /openapi.json fits the same slot.
3) Regenerate the preset bundles from real published specs (no key).
Works from a checkout, and — since 0.2.2 started carrying the sampled
layer — from a plain pip install too (note 1). On 0.2.1 as published from
PyPI, or to point at a different bundle set, pass --presets-root
or set MCPORTAL_PRESETS= .
mcportal presets # list mcportal compile --check # byte-compare committed vs regenerated (exit 3 on drift)
4) The whole test suite (no live network, no key, no real data).
pytest -q
Install
pip install mcportal # core runtime (single dependency: httpx)pip install "mcportal[mcp]" # + the MCP conversion layer (fastmcp)
Dependency policy: the core runtime depends on httpx and nothing else. The spec-normalizing compiler (mcportal.compiler) uses only the standard library and httpx. fastmcp is required solely by mcportal.mcp and ships as the optional [mcp] extra — without it, import mcportal and the entire test suite still work, and calling into the MCP layer raises a Korean ImportError that explains how to install it. The [mcp] extra also declares anyio, because the sync-to-async bridge imports anyio.to_thread directly; httpx pulls anyio in transitively, but a direct import deserves a direct declaration so that pins and lockfiles constrain it.
import mcportal does not import mcportal.mcp — that is what keeps the import working without fastmcp installed. The MCP symbols are resolved lazily on first attribute access through a module __getattr__ (PEP 562), so from mcportal.mcp import build_server and mcportal.build_server refer to the same object. Either spelling is fine.
Single-key principle (no multi-key rotation)
MCPortal's data.go.kr profile does not support multi-key rotation. data.go.kr issues one key per development account and meters a daily call limit against it; cycling several keys to escape that limit risks violating the service's operating policy and inviting account sanctions. MCPortal respects the structure as it is and accepts a single key. When the limit is too low, the supported answer is data.go.kr's own path — registering a use case and applying for the operational tier — not more keys.
CLI
The CLI uses the standard library argparse only. Zero new runtime dependencies is a binding rule for this project, so even the terminal tables are laid out by hand (Hangul counted as double width, ASCII rules, safe on a Windows cp949 console).
mcportal quota status [--ledger PATH] [--budget N] [--day YYYY-MM-DD][--key-fp FP | --key-env VAR] [--json] mcportal compile [PRESET_ID ...] [--presets-root PATH] [--check] [--json] mcportal presets [--presets-root PATH] [--json] [--verbose] mcportal sample PRESET_ID ... --key-env VAR [--budget N] [--count N] [--ledger PATH] [--presets-root PATH] [--json] mcportal serve PRESET_ID [--replay | --key-env VAR] [--presets-root PATH] [--name TEXT]
| Subcommand | What it does |
|---|---|
quota status | Shows today's (KST) usage, budget, remainder and state per key fingerprint. The ledger is opened read-only (`mode=ro`) and never created. Budget resolution order is --budget > CALL_BUDGET > profile default, and the output states which path was taken |
compile | Regenerates preset bundles. Files whose content is unchanged are not rewritten. --check writes nothing and only byte-compares |
presets | Lists the bundles as a table; --verbose expands the curation notes |
sample | Live sampling that fills in response schemas still marked unresolved, writing the inferred schema, the response bodies and a replayable cassette. It is the one subcommand that needs a key, and the key is taken only from the environment variable named by --key-env VAR, never as a literal argument |
serve | Stands one bundle up as an MCP server over stdio. The default --replay needs no key; --key-env VAR goes live through the same quota guard. Requires the [mcp] extra. Documented against a repo checkout: --replay reads presets/ /cassettes/ .json, which the wheel does not carry (note 1), so from a PyPI install pass --presets-root /presets or set MCPORTAL_PRESETS= /presets. Three of the four bundles have a cassette — 15081808 has none in the repository either, so it serves live only. stdout is protocol-only; every human-readable line, banner included, goes to stderr |
Exit codes: 0 success (including "no ledger", "no presets" and "nothing changed" — an empty state is not a failure) / 1 execution failure / 2 usage error / 3 drift found by compile --check / 130 user interrupt.
--json prints JSON alone on stdout (no human prose mixed in, so it is pipe-safe) and sends every error to stderr. A raw service key is never printed on any path — even --key-env reads the environment variable and computes the fingerprint locally. The ledger stores no raw key, so a fingerprint is the only thing the CLI ever had available to show.
Presets — three services, four datasets
presets/ holds bundles built from real published specifications on data.go.kr. Their purpose is to demonstrate, in data rather than in code, the fix for the failure mode of naive spec conversion, where every generated tool ends up described as "list query".
| ID | Service | Domain | Sour
Only the beginning is shown; read the rest in the repo