Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pharaoh

NPM · @PHARAOH-SO/MCP · 2 COMPONENTS

Codebase knowledge graph — architectural awareness for AI coding agents via MCP

+16 this week 88 Trust /100

Last scanned (2 hours ago)

Scores higher than 92% of npm servers

Category Code Search and Documentation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Pharaoh-so/pharaoh-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1828 tokens (~203/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability check failed: the tool surface changed between 0.3.27 and 0.3.61: 0 tool removals, 1 breaking changes, 7 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1
    • Package version: 0.3.56 → 0.3.61 functional
  • 4 Nov 26 −1
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 266 → 203 ▲ functional
    • Package version: 0.3.54 → 0.3.56 functional
  • 3 Nov 26 +16
    • Provenance: unverified → pass ▲ security
    • Source repository: fail → pass ▲ security
    • The attested source repository moved: Pharaoh-so/pharaoh-mcp security
    • Security disclosure: unverified → pass ▲ functional
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50.

  • 28 Oct 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 47.

  • 25 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 24 Oct 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: unverified → 0.85 ▲ functional
    • Package version: 0.3.52 → 0.3.54 functional
    • Package version: 0.3.52 → 0.3.53 functional
  • 23 Oct 26 −26
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 0.84 → unverified ▼ functional
    • Package version: 0.3.50 → 0.3.52 functional
    • Package version: 0.3.50 → 0.3.51 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pharaoh-so/mcp@0.3.61

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Pharaoh-so/pharaoh-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Pharaoh-so/pharaoh-mcp/.github/workflows/publish-mcp-proxy.yml@refs/heads/main
Rekor log index 3692601737
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:6f830046c0a8baf8e6139a438afc2c0c381ab2eaa23024462f52612721bf2a580b87402a2c93d140d40dac846fe856c929ff31aa968d320b9de38f202

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,341 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_blast_radius ~161

What a change to a function, file or module reaches. CALL THIS WHEN: • Changing a signature, refactoring or deleting code • Finding the callers or detected endpoints a change reaches RETURNS: Risk, production callers by module/file, endpoints, cron jobs and DB operations, through direct and indirect calls. Hops are the shortest detected path within the requested depth (1–5). Test-file callers are excluded.

NameTypeReqDescription
depthinteger–How many hops to trace (default: 3, range: 1–5)
entitystringyesFunction name, file path, or module name
entity_typestringyesType of entity
repostringyesRepository name — one of your connected repos.

No output schema declared.

No examples provided.

get_codebase_map ~145

A repo's architecture in one call. CALL THIS WHEN: • Getting a repo's overall structure, or which module owns something • The repo's exact name in Pharaoh isn't known RETURNS: Modules with file counts and LOC, module dependencies with two-way ones flagged, the 5 files changed most in 90 days, endpoints with handler files (first 50), convention entry points (first 30), and risk signals (high-risk functions without direct test links, exact clones, cycles).

NameTypeReqDescription
include_metricsboolean–List the 10 most-changed files instead of 5
repostringyesRepository name — one of your connected repos.

No output schema declared.

No examples provided.

get_module_context ~136

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.

NameTypeReqDescription
modulestringyesModule name (e.g., "crons", "slack", "db")
repostringyesRepository name — one of your connected repos.

No output schema declared.

No examples provided.

get_unused_code ~219

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.

NameTypeReqDescription
functionsarray–Function names or Class.method names to check instead of listing everything unused
modulestring–Limit to one module
repostringyesRepository name — one of your connected repos.

No output schema declared.

No examples provided.

pharaoh_account ~122

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.

NameTypeReqDescription
actionstring–Only status; pharaoh_manage_repo re-maps a repo

No output schema declared.

No examples provided.

pharaoh_manage_repo ~149

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.

NameTypeReqDescription
actionstringyesWhich change to make
fullboolean–refresh_repo only: rebuild the whole graph instead of a delta refresh
repostringyesRepo slug (owner/repo) or repo name

No output schema declared.

No examples provided.

pharaoh_recon ~182

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.

NameTypeReqDescription
blast_radiusarray–Blast radius targets
dependenciesarray–Module pairs to trace a dependency path between
functionsarray–Function searches
include_mapboolean–Include the codebase map (default true)
modulesarray–Modules to profile
repostringyesRepository name — one of your connected repos.

No output schema declared.

No examples provided.

search_functions ~227

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.

NameTypeReqDescription
exported_onlyboolean–Exported functions only (default false)
filestring–Only this file (full path matches exactly, a file name as a substring)
limitinteger–Max results (default 20)
modulestring–Only this module
offsetinteger–Results to skip (default 0)
querystringyesFunction name or part of one
repostringyesRepository name — one of your connected repos.

No output schema declared.

No examples provided.

Install

How do I install the Pharaoh MCP server?

Pharaoh runs locally as an npm package, launched with npx -y @pharaoh-so/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pharaoh-so/mcp

# add to Claude Code
claude mcp add so-pharaoh-pharaoh -- npx -y @pharaoh-so/mcp
Common questions

What is the Pharaoh MCP server?

Pharaoh is an MCP server listed in the public MCP registry as so.pharaoh/pharaoh. Codebase knowledge graph, architectural awareness for AI coding agents via MCP. This page covers its npm package (@pharaoh-so/mcp).

Is the Pharaoh MCP server safe to use?

Pharaoh scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Pharaoh MCP server expose?

Pharaoh exposes 8 tools: get_codebase_map, pharaoh_recon, get_module_context, get_blast_radius, search_functions, and 3 more. Their descriptions and schemas cost roughly 1,341 tokens of context every time the server is loaded.

Is the Pharaoh MCP server still maintained?

Pharaoh is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Pharaoh MCP server under?

Pharaoh declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.