mcpo
A simple, secure MCP-to-OpenAPI proxy server
Runssource: GitHubhomepagePythonMITcommit 788ff92e5288
Python, MIT licensed. The project labels itself: mcp, mcp server, mcp to openapi, open webui and openapi.
mcpo runs. An Argusic agent installed it in 2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
mcpo installs and runs correctly, proxying a real stdio MCP server (FastMCP) over REST with auto-generated OpenAPI schemas; all 27 unit tests pass, both tool endpoints return correct results via HTTP.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- mcp v2.2.0 installed despite pyproject.toml requiring >=1.17.0; mcp v2 renamed McpError->MCPError and streamablehttp_client->streamable_http_client, breaking imports1 minute
- pip install -e .[dev] did not include pytest and pytest-asyncio0.5 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- curl -X POST localhost:8001/hello -d '{"name":"World"}' returned HTTP 200 with 'Hello, World!'; curl -X POST localhost:8001/add -d '{"a":3,"b":5}' returned HTTP 200 with '8'; GET /openapi.json and /docs both returned 200; pytest ran 27/27 passed
- Model tokens used
- 74,028
- Exact commit tested
- 788ff92e5288
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
src/mcpo/tests/test_main.py::test_model_caching PASSED [ 88%]
src/mcpo/tests/test_main.py::test_multi_type_property_with_list PASSED [ 92%]
src/mcpo/tests/test_main.py::test_multi_type_property_with_any_of PASSED [ 96%]
src/mcpo/tests/test_main.py::test_ref_to_parent_node PASSED [100%]
=============================== warnings summary ===============================
.venv/lib/python3.12/site-packages/passlib/utils/__init__.py:854
/work/repo/.venv/lib/python3.12/site-packages/passlib/utils/__init__.py:854: DeprecationWarning: …
from crypt import crypt as _crypt
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
======================== 27 passed, 1 warning in 0.69s =========================
tokens used
74,028Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 2 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 6 mcp projects Argusic has installed and timed, mcpo was the 4th fastest to reach a running state, and 5 of 6 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 2 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcpo)Questions
- Does mcpo run?
- Yes. mcpo runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test mcpo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 788ff92e5288. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mcpo?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mcpo take to install?
- 2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does mcpo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mcpo?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does mcpo compare with the alternatives?
- Of the 6 mcp projects Argusic has installed and timed, mcpo was the 4th fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for mcpo?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.