python-utcp

Official python implementation of UTCP. UTCP is an open standard that lets AI agents call any API directly, without extra middleware.

Runssource: GitHubhomepagePythonMPL-2.0commit 3730c4663333

Python, MPL-2.0 licensed. The project labels itself: ai, ai agent, ai agent tools, developer tools, llm, mcp, model context protocol and python.

python-utcp runs. An Argusic agent installed it in 3 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

UTCP core library and all 10 plugin packages install in a Python 3.12 venv and pass their test suites with 569 passed, 5 skipped, 0 failures. The UtcpClient creates and closes without errors, all communication protocol types (http, sse, streamable_http, cli, mcp, text, file, websocket, tcp, udp, gql) register successfully.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
673
forks
58
open issues
15
watchers
10
size
1 MB
created
last push

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.

Time lost to each failure while testing python-utcp, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Externally-managed Python environment prevents system-wide pip install1 minute
  • Missing numpy dependency blocks in_mem_embeddings plugin test collection1 minute
Install time
3 minutes
Cold machine to finish
21 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
pytest --no-header -q on all packages: 59 core + 255 http + 66 cli (5 skipped) + 48 mcp + 119 text/file/websocket/socket/gql + 22 in_mem_embeddings = 569 passed, 5 skipped, 0 failed
Model tokens used
95,598
Exact commit tested
3730c4663333
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

For launch_succeeded: this should be about whether the app ran. The test suite executed = the app r…
For errors: I recorded the main ones — externally managed env, missing numpy, and MCP test timeout …
Let me reconsider the errors list:
1. Externally managed environment -> fixed with venv
2. Missing numpy -> fixed with pip install
That's it. The MCP test "hang" was just a timeout issue — the tests actually pass when given enough…
Actually, looking more carefully, the `test_plugin_registrations_survive_the_isolated_tests_above` …
Errors with 0-minute fixes:
1. Externally managed env -> venv (1 min)
2. Missing numpy -> pip install (1 min)
Hmm, actually looking again at the test_plugin_registrations_survive_the_isolated_tests_above failu…
Let me just note the major issues.

Replay 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.
  • Installed in 3 minutes, faster than the median of the 236 comparable projects Argusic has measured.
  • 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 MPL-2.0, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 237 ai projects Argusic has installed and timed, python-utcp was the 85th fastest to reach a running state, and 168 of 237 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 3 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

aiai-agentai-agent-toolsdeveloper-toolsllmmcpmodel-context-protocolpythonutcp

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/python-utcp.svg)](https://argusic.com/subject/python-utcp)

Questions

Does python-utcp run?
Yes. python-utcp runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test python-utcp?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3730c4663333. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test python-utcp?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does python-utcp take to install?
3 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 python-utcp need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing python-utcp?
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 python-utcp compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, python-utcp was the 85th fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for python-utcp?
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.

Discussion