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.

MCP AST Explorer

PYPI · MCP-AST-EXPLORER

Python symbol exploration for codebase onboarding agents.

Available components

+11 this week 66 Trust /100

Last scanned (15 hours ago)

Scores higher than 63% of PyPI servers

Category Developer Tools

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability34
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 145 tokens (~24/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage14
  • 0% of tools have a non-trivial description (not blank, and not just the tool's name).Fail
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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 +15
    • Malware scan: unverified → pass ▲ security
  • 4 Nov 26 −4
    • Stability: pass → 0.67 functional
  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 2 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 1 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 28 Oct 26 0
    • Stability: pass → 0.97 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 pypi/mcp-ast-explorer@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 18 packages
Packages resolved 18
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~145 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
call_chain ~34

No description provided.

NameTypeReqDescription
depthinteger––
from_symbolstringyes–
languagestring––
pathstringyes–
NameTypeReqDescription
callersarray––
error–––
foundbooleanyes–
symbolstringyes–

No examples provided.

class_hierarchy ~28

No description provided.

NameTypeReqDescription
class_namestringyes–
languagestring––
pathstringyes–
NameTypeReqDescription
class_namestringyes–
error–––
foundbooleanyes–
subclassesarray––

No examples provided.

find_definition ~26

No description provided.

NameTypeReqDescription
languagestring––
pathstringyes–
symbolstringyes–
NameTypeReqDescription
error–––
foundbooleanyes–
kind–––
location–––
name–––
qualified_name–––
signature–––
source_code–––
symbolstringyes–

No examples provided.

find_references ~27

No description provided.

NameTypeReqDescription
languagestring––
pathstringyes–
symbolstringyes–
NameTypeReqDescription
error–––
foundbooleanyes–
referencesarray––
symbolstringyes–

No examples provided.

function_signature ~26

No description provided.

NameTypeReqDescription
languagestring––
pathstringyes–
symbolstringyes–
NameTypeReqDescription
error–––
foundbooleanyes–
kind–––
name–––
qualified_name–––
signature–––
symbolstringyes–

No examples provided.

health ~4

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the MCP AST Explorer server?

MCP AST Explorer runs locally as a PyPI package, launched with uvx mcp-ast-explorer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-ast-explorer

# add to Claude Code
claude mcp add lovranran-mcp-ast-explorer -- uvx mcp-ast-explorer
Common questions

What is the MCP AST Explorer server?

MCP AST Explorer is listed in the public MCP registry as io.github.LovRanRan/mcp-ast-explorer. Python symbol exploration for codebase onboarding agents. This page covers its PyPI package (mcp-ast-explorer).

Is the MCP AST Explorer server safe to use?

MCP AST Explorer scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 MCP AST Explorer server expose?

MCP AST Explorer exposes 6 tools: health, find_definition, find_references, function_signature, call_chain, class_hierarchy. Their descriptions and schemas cost roughly 145 tokens of context every time the server is loaded.

Is the MCP AST Explorer server still maintained?

MCP AST Explorer 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 MCP AST Explorer server under?

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

What did VerifyMCP test on the MCP AST Explorer server?

VerifyMCP ran 16 checks on MCP AST Explorer, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.