mcptools

A command-line interface for interacting with MCP (Model Context Protocol) servers using both stdio and HTTP transport.

Runssource: GitHubGoMITcommit e7bd72461183

Go, MIT licensed. The project labels itself: mcp, mcp server and modelcontextprotocol.

mcptools runs. An Argusic agent installed it in 0.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

MCP Tools builds and runs: the mcp binary at /work/repo/bin/mcp prints help/version, starts a mock MCP server, and all test suites pass

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.01 (measured)
recorded runs
2
last tested
stars
1,631
forks
133
open issues
40
watchers
15
size
25 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 mcptools, 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.

  • Go not installed in container (no root to apt-get)0.5 minutes
Install time
under a minute
Cold machine to finish
1 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
go test ./... exited 0 with 3 packages passing; bin/mcp version printed 'MCP Tools version dev'; bin/mcp mock tool hello 'test' started server successfully
Model tokens used
39,724
Exact commit tested
e7bd72461183
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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.

**Version**: `bin/mcp version` → "MCP Tools version dev".
**Mock server**: Starts successfully, logs to `~/.mcpt/logs/mock.log`.
**Tests**: `go test ./...` — all 3 test packages pass (zero failures, zero errors).
The only issue was Go not being installed — I downloaded Go 1.24.1 manually (no root/sudo available…
tokens used
39,724
Everything passes cleanly. Here's the summary:
**Build**: `go build` succeeded — binary at `bin/mcp` (13 MB).
**Version**: `bin/mcp version` → "MCP Tools version dev".
**Mock server**: Starts successfully, logs to `~/.mcpt/logs/mock.log`.
**Tests**: `go test ./...` — all 3 test packages pass (zero failures, zero errors).
The only issue was Go not being installed — I downloaded Go 1.24.1 manually (no root/sudo available…

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 0.5 minutes, faster than the median of the 15 comparable projects Argusic has measured.
  • Recovered from all 1 error 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.
  • Measured 2 times, so the result is not a one-off.

Of the 16 mcp projects Argusic has installed and timed, mcptools was the 5th fastest to reach a running state, and 14 of 16 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 0.5 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 Runner2/3Runs100.000.01
Argusic Runner1/3Runs100.000.06

Topics (from GitHub)

mcpmcp-servermodelcontextprotocol

Embed the badge

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

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

Questions

Does mcptools run?
Yes. mcptools runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test mcptools?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit e7bd72461183. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test mcptools?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does mcptools take to install?
0.5 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 mcptools need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing mcptools?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does mcptools compare with the alternatives?
Of the 16 mcp projects Argusic has installed and timed, mcptools was the 5th fastest to reach a running state, and 14 of 16 reached one at all.
Where is the evidence for mcptools?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion