Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Tracepulse 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.
What it does
Runtime feedback MCP server for AI coding agents. ViewGraph sees the UI - TracePulse feels the backend.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user tracepulse-mcp '--' npx -y tracepulse
# 2 — ask your agent for something these tools do
# get_errors, get_server_logs, get_runtime_status and 41 more
Tracepulse costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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 Tracepulse 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.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx 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 tracepulse-mcp '--' npx -y tracepulseReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
44 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.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under AGPL-3.0
- 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 Tracepulse or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tools were statically extracted from the published source (44 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>".
44 of the 44 recovered tools are registered only when parsed.command === "version" is false (dist/cli.js:8439) — 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 · 44 only when parsed.command === "version" is false (dist/cli.js:8439) — typically when a key or option is configured. All 44 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_errors conditional | no tags | |
| get_server_logs conditional | no tags | |
| get_runtime_status conditional | no tags | |
| clear_errors conditional | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| acknowledge_error conditional | state-write | state-write: declares readOnlyHint: false |
| watch_for_errors conditional | no tags | |
| get_build_errors conditional | no tags | |
| get_error_clusters conditional | no tags | |
| get_migration_status conditional | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_audit_trail conditional | no tags | |
| get_session_insights conditional | no tags | |
| check_drift conditional | no tags | |
| get_session_impact conditional | no tags | |
| get_session_summary conditional | no tags | |
| get_perf_baseline conditional | no tags | |
| get_error_context conditional | no tags | |
| get_timeline conditional | no tags | |
| list_services conditional | no tags | |
| get_correlated_errors conditional | no tags | |
| get_new_errors conditional | no tags | |
| get_error_trends conditional | no tags | |
| correlate_with_diff conditional | no tags | |
| get_cross_layer_diagnosis conditional | no tags | |
| get_health_summary conditional | no tags | |
| verify_fix conditional | no tags | |
| verify_loop conditional | no tags | |
| get_prompt_context conditional | no tags | |
| verify_build conditional | code-execuntrusted-input | code-exec: parameter "command"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| wait_for_build conditional | no tags | |
| wait_for_event conditional | no tags | |
| run_and_watch conditional | code-execuntrusted-input | code-exec: parameter "command"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_requests conditional | no tags | |
| restart_server conditional | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_infra_status conditional | no tags | |
| get_infra_detail conditional | no tags | |
| check_port conditional | no tags | |
| free_port conditional | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_project_health conditional | no tags | |
| verify_mcp conditional | code-execuntrusted-input | code-exec: parameter "command"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| register_probe conditional | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| list_probes conditional | no tags | |
| get_bug_patterns conditional | no tags | |
| start_server conditional | code-execexternal-sink | code-exec: parameter "command"; external-sink: declares readOnlyHint: false, openWorldHint: true |
| stop_server conditional | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
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.
Supply chain and provenance
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 0.9.31. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
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.
Any signed-in account that does not publish Tracepulse can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.