contextplus

Semantic Intelligence for Large-Scale Engineering. Context+ is an MCP server designed for developers who demand 99% accuracy. By combining RAG, Tree-sitter AST, Spectral Clustering, and Obsidian-style linking, Context+ turns a massive codebase into a searchable, hierarchical feature graph.

Runssource: GitHubhomepageTypeScriptMITcommit 1b59b37f3130

TypeScript, MIT licensed. The project labels itself: mcp server.

contextplus runs. An Argusic agent installed it in 0.1 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Context+ MCP server builds, all 271 tests pass, MCP server responds to initialize on stdio with correct capabilities.

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.03 (measured)
recorded runs
2
last tested
stars
1,990
forks
169
open issues
2
watchers
10
size
0 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.

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 run test:all exited 0, 271 passed (45 suites, 236 main + 35 demo); node build/index.js responded to MCP initialize with serverInfo name=contextplus version=1.0.0
Model tokens used
34,167
Exact commit tested
1b59b37f3130
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.

**Install & Build**: `npm install` (131 packages) and `npm run build` (tsc) both completed without …
**Tests**: `npm run test:all` — 271 tests pass across 45 suites, 0 failures, 0 skipped. This includ…
**Server Launched**: MCP stdio server starts, responds to `initialize` with proper JSON-RPC, report…
**No errors encountered** — everything worked on the first pass.
tokens used
34,167
All 271 tests pass (236 main + 35 demo). Let me compile the report.
Here's the summary:
**Install & Build**: `npm install` (131 packages) and `npm run build` (tsc) both completed without …
**Tests**: `npm run test:all` — 271 tests pass across 45 suites, 0 failures, 0 skipped. This includ…
**Server Launched**: MCP stdio server starts, responds to `initialize` with proper JSON-RPC, report…
**No errors encountered** — everything worked on the first pass.

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.1 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • 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.

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.1 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.03
Argusic Runner1/3Runs100.000.01

Topics (from GitHub)

mcp-server

Embed the badge

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

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

Questions

Does contextplus run?
Yes. contextplus runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test contextplus?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1b59b37f3130. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test contextplus?
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 contextplus take to install?
0.1 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 contextplus need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing contextplus?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for contextplus?
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