rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Local gVisor sandbox for coding agents that records what they actually ran.
Skills that teach the AI this kind of work; they work alongside this one
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 32/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 44/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 29 (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install RayTrace. Follow https://mcp.popnx.com/i/godcreatebugs-raytrace.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 19, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server RayTrace for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "raytrace": { "command": "npx", "args": [ "-y", "@raytrace-cli/cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the RayTrace tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"raytrace": {
"command": "npx",
"args": [
"-y",
"@raytrace-cli/cli",
"mcp"
]
}
}
}Use RayTrace and tell me what you can do for me, then show me one thing✓ If Claude says it is using RayTrace or shows a RayTrace tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect RayTrace yet
RayTrace runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect RayTrace
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server RayTrace for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user raytrace -- npx -y @raytrace-cli/cli mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the RayTrace tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user raytrace -- npx -y @raytrace-cli/cli mcpYou should see RayTrace listed as connected
Use RayTrace and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using RayTrace or shows a RayTrace tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server RayTrace for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "raytrace": { "command": "npx", "args": [ "-y", "@raytrace-cli/cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the RayTrace tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use RayTrace and tell me what you can do for me, then show me one thing✓ If Cursor says it is using RayTrace or shows a RayTrace tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server RayTrace for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "raytrace": { "type": "stdio", "command": "npx", "args": [ "-y", "@raytrace-cli/cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the RayTrace tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use RayTrace and tell me what you can do for me, then show me one thing✓ If VS Code says it is using RayTrace or shows a RayTrace tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user raytrace -- npx -y @raytrace-cli/cli mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"raytrace": {
"command": "npx",
"args": [
"-y",
"@raytrace-cli/cli",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"raytrace": {
"command": "npx",
"args": [
"-y",
"@raytrace-cli/cli",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"raytrace": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@raytrace-cli/cli",
"mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @raytrace-cli/clipypi: raytrace-cliBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account Godcreatebugs, which owns the repo
Code last changed today
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for @raytrace-cli/cli@0.17.7
Checks only this package version, not every dependency · checked Nov 19, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/godcreatebugs-raytrace)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed today, and the latest version (0.17.7) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Python (uv) on your computer.
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one RayTrace | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Eye of Sauron
See what your coding agents did, rather than what they said they did.
Try the interactive demo — no install needed
Website · npm · PyPI · MCP · Contributing · Report an issue
A coding agent doesn't just suggest edits. It runs commands, installs packages, reads and writes files, and opens network connections — often with permission to do all of that on your machine.
What it tells you afterwards is a claim. "Tests passed" is what the agent reported. That report can miss a command that phoned home, a package you didn't ask for, a file outside the task, or a test whose real exit code was not zero. And if the agent is running on your laptop, it can reach everything else there: secrets, private networks, and files that were never part of the work.
Sandboxing is how you change both of those problems. The agent works in an isolated copy of the project, where it cannot see your machine. And the record of what happened is taken from outside that sandbox, so the agent cannot turn it off or edit it.
Why we built RayTrace (1 min 47 sec)
*Why we built RayTrace — the gap between what an agent reports and what actually ran.*
RayTrace runs Claude Code or Codex in that isolated copy, records what actually happened, and shows it in a dashboard.
Each local sandbox is a Docker container under gVisor, inside a Linux VM made with Lima. It can't see your machine's files or private networks. A collector outside the sandbox — which the agent can't turn off — records every command, its real exit code, the files it read or changed, and where it connected. Your own files are never changed. Nothing is uploaded.
The dashboard has two layers. Tool calls are what the agent reported. Sandbox evidence is what the machine saw. If those disagree, you can see it, and take the file diffs home as a patch.
Local sandboxes are free, MIT licensed, and need no RayTrace account. Cloud sandboxes are optional, for teams that want a shared dashboard at app.raytracer.si.
Install the CLI from npm or PyPI, then create a sandbox in any Git repository. Nothing is uploaded.
npm install -g @raytrace-cli/cli
cd your-project # any Git repository raytrace sandbox create --local # first time: sets up the VM, a few minutes raytrace connect your-project --claude # a terminal in it, with Claude Code running
--name my-box to choose the name.--codex instead of --claude to start Codex, or leave both off for a plain shell where you run claude or codex yourself.connect prints a link to the dashboard showing only this sandbox's prompts. The full local dashboard is at http://127.0.0.1:8797 — open that in your browser. If you set RAYTACE_PORT in ~/.raytrace/config.env, the dashboard is on that port instead.The npm package needs Node.js 22.13 or newer (node --version) on macOS or Linux. The PyPI package installs the same CLI with its own Node.js, so you don't need Node on the machine. Windows is experimental. Where this page says npx -y @raytrace-cli/cli@latest, use uvx --from raytrace-cli raytrace instead.
Or skip the commands and ask your editor's agent: set up MCP, then say "create a local sandbox and connect this repo".
| Requirement | |
|---|---|
| macOS 13.5 or later | Nothing to install. RayTrace uses your Lima 2.0+ if you have it, or offers to download Lima into ~/.raytrace/lima (no admin rights; checked against a pinned checksum) |
| Older macOS | QEMU too: brew install qemu |
| Linux | Lima, QEMU, and access to /dev/kvm (sudo usermod -aG kvm $USER, then log out and in) |
| Windows | experimental; RayTrace doesn't download Lima there, so local sandboxes need WSL2 — see docs/windows.md for what works and the WSL2 and cloud paths |
| Disk and memory | the first setup downloads about 1 GB; the VM uses 4 GiB of memory while it runs |
raytrace doctor checks all of this and says how to fix anything missing.
raytrace sandbox list --local # your local sandboxes
raytrace connect my-box --claude # back in; the sandbox keeps running when you leave raytrace sandbox stop my-box # stop it; its files are kept raytrace sandbox start my-box raytrace sandbox destroy my-box # asks whether to delete its captured logs too limactl stop raytrace # stop the whole VM to free its 4 GiB of memory
When you destroy a sandbox, you're asked what to do with its logs:
~/.raytrace/archive/ - /: the agent transcripts, the recorded commands, files and connections as JSON lines, and any forks. Its sessions stay in your dashboard.--delete-logs or --keep-logs answers without asking. To keep the logs in the cloud, raytrace upload logs --sandbox my-box sends them to app.raytracer.si (needs a sign-in).
/tmp. All sandboxes share the VM's 30 GiB disk.npm test. Each rerun is a fork, a sandbox of its own started from the snapshot just before that step.Claude Code and Codex are preinstalled. --claude starts Claude Code with --dangerously-skip-permissions, and --codex starts Codex with --dangerously-bypass-approvals-and-sandbox. The sandbox's own settings, which the agent can't change, make this the default too, so typing claude or codex yourself works the same way. The sandbox is what keeps the agent contained, and every command is recorded.
Files a project's owner restricts in the dashboard (Initial scan) can't be changed by the agent, whatever it tries. Sign in to Claude Code or Codex inside the sandbox, as you would on your machine; the sign-in stays until you destroy it. Exiting the agent drops you into the sandbox's shell, and exiting that leaves the sandbox running. raytrace connect takes you back.
In local sandboxes, Codex's prompts don't reach the dashboard's Prompts page yet. Its commands, file changes and network connections are recorded.
Cloud sessions are at app.raytracer.si. The local dashboard is at http://127.0.0.1:8797 — open that in your browser. Every page is about one prompt, and they link to each other.
The dashboard has two layers. Tool calls are what the agent reported: the path from your prompt to the answer, with the command, what the agent says came back, and tokens, time and cost at each step. Sandbox evidence is what the machine saw, recorded from outside the agent where it can't be turned off or edited: every process, its real exit code, the files it read or changed, and where it connected.
| Feature | What it does |
|---|---|
| Prompts | Every prompt you gave the agent, newest first, with where it ran (your machine, a local sandbox or a cloud sandbox), the model, how many tool calls it took and what it cost. Open one to read the answer and a short recap of the run. |
| Tool calls | The path from your prompt to the answer: one divider for each round trip to the model, one row for each tool call it proposed, with the command and what the agent says came back, plus tokens, time and cost at each step. |
| Sandbox evidence | What the sandbox itself saw, recorded from outside the agent. Every process in time order, with its real exit code, the files it read or changed, and where it connected — including anything no tool call accounts for. Use it to check "tests pass" against the real exit code, and to catch a script that phoned home or a package you didn't ask for. |
| Changes | Every file the prompt changed, with its diff, first for the whole prompt and then step by step. Download it all as one patch and apply it to your own checkout. The sandbox works on a copy; the patch is how you take the work home. |
| Context | What was in the model's context when it answered: what you said earlier, what the model brought in itself (earlier answers, and the files it read, with how much of each actually fit), and what the agent's harness adds to every request. Use it to see whether a wrong answer came from a file that was never read, or was cut off. |
| Playground | Pick any step and rerun from there with something changed: a tool result, a file, the model, the message, or a time limit. Each rerun is a fork, a sandbox of its own started from the snapshot just before that step. Add a check such as npm test and every fork is graded pass or fail, so you can compare models or outcomes side by side. |
| Story | The short version of a long run: a timeline of only the steps that mattered, the single most consequential command pulled out at the top, and for each step what the agent could see, what it proposed, what really happened and what that led to. Worked