Skip to content

now in public beta

The edit is easy. Knowing what breaks is hard.

Before a refactor, your agent should know every caller, importer, and dependent. Maguyva answers that from the real call graph, not a grep.

free plan: 3 repos, 50K indexed lines, no card.

// blast radius

Every caller, every package

Graph search finds dependents across the whole monorepo, including cross-language call sites.

// before you ship

Grounded in real lines

File paths and line numbers, so the migration list is right before CI goes red.

// any client

24 documented MCP clients

One remote MCP integration. No local indexer, no IDE to switch.

Check blast radius before you refactor.

Index one repo you already know and ask what calls the function you are about to change.

  1. // step 01

    Index a repo you know

    Pick the codebase where a refactor scares you. Free tier: 3 repos, 50K indexed lines.

  2. // step 02

    Connect over MCP

    Claude, Codex, Cursor, or any MCP client. One remote server, no local setup.

  3. // step 03

    Ask what breaks if you change it

    Get every caller and importer from the real graph, not a grep, before you touch a line.