@pharaoh-so/mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
Its tool definitions changed since version 0.3.82. If you approved the earlier ones, read them again.
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @pharaoh-so/mcp@0.3.85
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
get_codebase_map repo, include_metrics, include_health
A repo's architecture in one call. CALL THIS WHEN: • Orienting in a repo or locating a module • The mapped repo name is unknown RETURNS: Modules and LOC, dependencies and cycles, hot files (5), endpoints (50), entry points (30), exact clones and high-risk functions without direct test links.
pharaoh_recon repo, include_map, modules, functions, blast_radius, dependencies
Several Pharaoh queries in one call, run in parallel: codebase map, module profiles, function searches, blast radius and module dependency paths. CALL THIS WHEN: • Planning a change, reviewing a PR or assessing architecture, when the modules and functions to check are known RETURNS: Each requested section in one response, as the single-purpose tools return it. Per call: up to 5 modules, 3 searches, 3 blast radius targets, 3 dependency pairs.
get_module_context repo, module
One module's profile: what it contains, depends on and is called by. CALL THIS WHEN: • Changing code in a module, or planning a change to it • Finding what a module exports, depends on, or which code calls into it RETURNS: Files, LOC, exported signatures with complexity, imports in and out, DB tables, endpoints, cron jobs, env vars, and callers in other modules, grouped by module.
get_blast_radius repo, entity, entity_type, scope, local_context, depth
What a change to a function, file or module reaches. CALL THIS WHEN: • Changing a signature, refactoring or deleting code • Finding a change's callers or entry points RETURNS: Detected production callers (depth 1 is direct only). Hosted adds risk, endpoints, cron jobs and DB operations. Verified worktrees report saved-file callers and coverage.
search_functions repo, query, module, file, exported_only, offset, limit
Find functions by name or concept across the whole codebase. CALL THIS WHEN: • Checking whether a function, helper or utility already exists • Finding where something is implemented (e.g. "retry", "validate", "notify") RETURNS: Matching functions with file path, line range, module, signature, export status and complexity. Matches name parts (camelCase, snake_case) and file paths, not comments; test code ranks last. SCREAMING_SNAKE queries, and queries no function matches, return matching constants with up to 80 characters of each value.
5 more tools
get_unused_code repo, module, functions
Find code nothing runs: functions no production entry point (endpoint, CLI command, cron job, event handler, worker, entry file) reaches. CALL THIS WHEN: • Cleaning up a module or deleting a function • Confirming new code is reached from an entry point RETURNS: Reachability through the call graph, not text references. • Dead: unreached, named in no other file, and no import of its file could reach it. • Possibly unused: unreached, but named in other files (string dispatch, dynamic loading) or an import of its file could reach it. Listed with the files that name it. • Used only by tests: exported functions and class methods only test files reference. With `functions`: each one's status, and the call path from an entry point when it's reachable.
pharaoh_setup repo
Pharaoh's connection and setup status for the repo you're working in. Writes no files. CALL THIS WHEN: • The user asks to set up Pharaoh, or to check its setup • Pharaoh was just connected and the user asks what to try first RETURNS: Connection, mapped-repo and access status, a Codebase Health link, optional first-use choices, and the Pharaoh-first instructions line only when needed.
pharaoh_account action
Your Pharaoh plan and mapped repos in each workspace. Changes nothing. CALL THIS WHEN: • Checking which plan a workspace is on • A tool says the plan doesn't include it, or a repo isn't mapped • Finding the setup page or the billing page RETURNS: Each workspace you can access with its plan and tracked-repo count, whether its repos are mapped on every push, the setup page, and the billing page when a workspace has a billing account.
pharaoh_manage_repo action, repo, full
Re-map a repo now. Every repo is mapped during the trial and on Pro, and re-maps on every push.
• refresh_repo { repo, full? }: queue a re-map of one repo.
• set_free_repo { repo }: retired; it changes nothing, since there is no live repo to choose.
CALL THIS WHEN:
• A repo's graph looks out of date, or needs a full rebuild
RETURNS: The queued job.pharaoh_update
Update the npx proxy to the newest Pharaoh release, with the user's consent. CALL THIS WHEN: • The user asks to update Pharaoh, or accepts a notice that a new Pharaoh version is available RETURNS: On the npx proxy, whether the newest release passed verification (npm's registry signature and its build provenance) and is staged; it becomes active at the next session start. On a hosted connection, that it is already current.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18 |
| Source | github.com/Pharaoh-so/pharaoh-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-9Nm84fD2oOgKHiSBjq8ixrKEirtPY58vp0mDkIksK8s0jbVOPCdCccuuBgmNe/5Q7oxxf4RdWZRNMiIr2Qs9Rw== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 0.3.85 | 2026-11-16 | Starts with no setup | 10 |
| 0.3.82 | 2026-11-12 | Starts with no setup | 9 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40pharaoh-so/mcp)
New version out? Ask for a fresh report.