mcpso
directory for Awesome MCP Servers
Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit e14f33850f44
TypeScript, Apache-2.0 licensed. The project labels itself: awesome mcp servers, mcp, mcp server store, mcp servers and mcp servers directory.
mcpso runs, with stand-ins for the services it depends on. An Argusic agent installed it in 6 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Next.js 15.0.4 app builds cleanly and serves all routes including homepage, categories, privacy-policy, terms-of-service, sitemap, favicon, and API endpoints on port 8051
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- ERR_PNPM_IGNORED_BUILDS: esbuild, sharp, workder builds blocked2 minutes
- pnpm not found in environment1 minute
- TypeScript error: KeyboardEvent<HTMLInputElement> is not generic when using @types/react@18 with React 191 minute
- Install time
- 6 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- next build compiled successfully (0 errors, 5 pages built), then next start --port 8051 served: HTTP 200 on / (index page, 29458 bytes), /categories, /privacy-policy, /terms-of-service, /favicon.ico; API POST endpoints returned 200 with {'code':-1,'message':'invalid project'}; curled page titles confirmed 'MCP Servers', 'MCP Server Categories | MCP Servers', 'Privacy Policy | MCP Servers'
- Model tokens used
- 188,505
- Exact commit tested
- e14f33850f44
- 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.
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <sitemap> === Favicon === 200 Everything is verified and working. Let me kill the server and compile the final report. exec /bin/sh -lc 'pkill -f "next start" 2>/dev/null; sleep 1; echo "done"' in /work/repo exited 143 in 0ms: All verified. Here's the final report: tokens used 188,505 All verified. Here's the final report:
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 6 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, 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.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.04 |
Topics (from GitHub)
awesome-mcp-serversmcpmcp-server-storemcp-serversmcp-servers-directory
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcpso)Questions
- Does mcpso run?
- mcpso runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test mcpso?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e14f33850f44. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mcpso?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mcpso take to install?
- 6 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 mcpso need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mcpso?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for mcpso?
- 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.