The official Svelte MCP server providing docs and autofixing tools for Svelte development
Nothing to run from here
Nexus is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
6
downloads a day
local
runs on your machine
107
downloads in 30d
What it does
Local code-intelligence server: hybrid code search, call graph and project memory.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user jaggernaut007-nexus-mcp '--' uvx nexus-mcp-ci
# 2 — ask your agent for something these tools do
# status, index, search and 5 more
Nexus costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
JAAll 1 server
jaggernaut0071 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Nexus as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user jaggernaut007-nexus-mcp '--' uvx nexus-mcp-ciReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take NEXUS_STORAGE_DIR (Folder for the index, memories and graph (default: .nexus in the project)), NEXUS_OFFLINE (Set to 1 to block the embedding model download after the first run) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Check whether this project is indexed and whether the index is fresh. You do not need it before other nexus tools: an index saved in an earlier session is attached when the server starts. Use it when a tool says "No codebase indexed" or to see index size. Returns indexed (true/false), file and…
Takes no parameters.
Build or refresh the code index for a project. Call it once per project when status says indexed is false; search, find_symbol, graph, map and analyze all need it. Pass an absolute path, or several comma-separated paths for a monorepo. It is incremental when an index exists, and a file watcher…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Absolute path to the codebase directory (or comma-separated paths) |
| paths | string | no | Additional comma-separated paths to index |
Find code by meaning or by keyword: "where is...", "how does... work", "find the code that...", "what handles...". Returns ranked results with file path and line range. The first three carry the whole function or class, so you can answer without opening the file. A query can hold exact names…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to find, in plain words or code terms. Exact names (parse_config) first |
| limit | integer | no | Max results (default 10) |
Look up functions, classes, methods or constants by name and get the whole code of each, with file, line range and direct callers and callees. Use it when you know the name ("show me create_order", "where is TokenBudget defined"), and in place of a file read or a grep for a definition. Pass…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol_name | string | yes | One name, or several with commas (e.g. 'create_server, TokenBudget, MAX_RETRIES') |
| exact | boolean | no | True for exact match, False for fuzzy substring |
Trace the call graph: who calls a function (direction='callers') or what it calls (direction='callees'). With transitive=true it lists everything that depends on the symbol, directly or indirectly; use that before you change a signature or rename, move or delete a shared function ("what breaks if…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol_name | string | yes | Name of the function/symbol to trace |
| direction | string | no | 'callers' (who calls this) or 'callees' (what this calls) |
| transitive | boolean | no | — |
Review the quality of the indexed project, or of one path: the most complex functions, long functions, large classes, dead code (functions with no static caller), module dependencies and an overall quality score. Use it for "what is the most complex code", "review this directory", "is there dead…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | Optional relative path to filter analysis (subdirectory or file) |
Keep and recall project knowledge across sessions: decisions, preferences, conventions, status. Use action='store' when the user says "remember that..."
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | 'store' saves a note, 'search' finds notes by meaning, 'delete' removes notes |
| content | string | no | The note to store (action='store') |
| query | string | no | What to look for (action='search') |
| tags | string | no | Comma-separated tags (all actions) |
| memory_id | string | no | ID of the note to delete (action='delete') |
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Nexus or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 2.3.0 · scanned 6 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings11 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digesta3dd48ec78201996022d10569d5d92efeda29781cb5f6261b05cad6d3213b614
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
7 of the 7 recovered tools are registered only when _settings.rate_limit_enabled is false (src/nexus_mcp/server.py:98) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
No tool is registered unconditionally · 7 only when _settings.rate_limit_enabled is false (src/nexus_mcp/server.py:98) — typically when a key or option is configured. All 7 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| status conditional | no tags | |
| index conditional | no tags | |
| search conditional | no tags | |
| find_symbol conditional | no tags | |
| graph conditional | no tags | |
| analyze conditional | no tags | |
| memory conditional | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta3dd48ec78201996
Scanned2026-11-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 2.3.0. Pin a release below and the command asks for exactly that one.
2.3.0
6 Nov 2026
latestNo release note was published with this version.
2.2.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Nexus can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.