modelcontextprotocol
The official MCP server implementation for the Perplexity API Platform
Runs with mockssource: GitHubhomepageTypeScriptMITcommit c58e4ad25460
TypeScript, MIT licensed.
modelcontextprotocol runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
npm install builds successfully, all 90 tests pass, HTTP server starts and serves the /health endpoint and MCP tools/list endpoint correctly
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 92 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.
- Install time
- under a minute
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- npm test passed 90/90 tests (4 files), curl to /health returned 200 OK, curl to /mcp returned valid JSON-RPC tools/list with 4 tools
- Model tokens used
- 28,373
- Exact commit tested
- c58e4ad25460
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Here's the final report based on everything I observed:
**Install**: `npm install` ran successfully including the build step (`tsc` + `shx chmod`). 245 pac…
**Tests**: `npm test` passed all 90 tests across 4 test files with zero failures.
**HTTP Server**: Launched on `127.0.0.1:8080`, health endpoint returned `{"status":"ok","service":"…
No errors were encountered at any stage.
tokens used
28,373
Here's the final report based on everything I observed:
**Install**: `npm install` ran successfully including the build step (`tsc` + `shx chmod`). 245 pac…
**Tests**: `npm test` passed all 90 tests across 4 test files with zero failures.
**HTTP Server**: Launched on `127.0.0.1:8080`, health endpoint returned `{"status":"ok","service":"…
No errors were encountered at any stage.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
- Installed in 0.5 minutes, faster than the median of the 23 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 24 TypeScript projects Argusic has installed and timed, modelcontextprotocol was the 2nd fastest to reach a running state, and 18 of 24 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.01 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/modelcontextprotocol)Questions
- Does modelcontextprotocol run?
- modelcontextprotocol runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test modelcontextprotocol?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c58e4ad25460. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test modelcontextprotocol?
- 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 modelcontextprotocol 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 modelcontextprotocol need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing modelcontextprotocol?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does modelcontextprotocol compare with the alternatives?
- Of the 24 TypeScript projects Argusic has installed and timed, modelcontextprotocol was the 2nd fastest to reach a running state, and 18 of 24 reached one at all.
- Where is the evidence for modelcontextprotocol?
- 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.