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.

io.github.Apheironn/pasr

PYPI · PASR-MCP

Local, token-budgeted code context with file:line provenance and selection receipts.

Available components

+6 this week 84 Trust /100

Last scanned (23 hours ago)

Scores higher than 88% of PyPI 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 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 39 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 Apheironn/pasr). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 407 tokens (~81/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +33
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.33 ▲ functional
  • 13 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Oct 26 −43
    • Malware scan: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.3.0 → 0.4.0 functional
  • 4 Oct 26 78

    First indexed and scored.

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 16 Oct 2026 · Analysed pypi/pasr-mcp@0.4.0

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo Apheironn/pasr
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Apheironn/pasr/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3084944666
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:97518dc0a732855a668e0a0be8c771e4f76f94a79e210fed81e038f3a838c12d

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

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

Dependencies 39 packages
Packages resolved 39
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~407 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
find_evidence ~76

Locate query terms in workspace source, with ranked file:line hits and read ranges. include uses workspace-relative paths/globs: *.py is root-only; **/*.py is recursive.

NameTypeReqDescription
includearray––
per_fileinteger––
querystring––
top_kinteger––

Structured output declared, but exposes no named fields.

No examples provided.

find_files ~58

Rank workspace paths by query-term matches in their names. Does not search file contents. Optional include scopes paths; an empty query lists candidates.

NameTypeReqDescription
includearray––
querystring––
top_kinteger––

Structured output declared, but exposes no named fields.

No examples provided.

find_symbols ~77

Find exact or partial symbol definitions with file:line ranges (Python, JS/TS, Rust). include uses workspace-relative paths/globs: *.py is root-only; **/*.py is recursive.

NameTypeReqDescription
includearray––
kindsarray––
querystring––
top_kinteger––

Structured output declared, but exposes no named fields.

No examples provided.

find_usages ~61

Find lexical references to a symbol, with source lines and enclosing definitions when available. Returns at most top_k hits; read_lines suggests bounded source ranges.

NameTypeReqDescription
includearray––
symbolstringyes–
top_kinteger––

Structured output declared, but exposes no named fields.

No examples provided.

select_context ~135

Select source spans from explicit files and/or include globs for a query. Context is capped at 1,500 tokens including file:line labels; metadata costs extra. Files accept path:start-end ranges. Range-only reads return ordered whole-line prefixes and continuation.files; whole-file or mixed scopes are ranked. outline returns a definition index. Each call is independent: retain prior context and compare source_fingerprint across continuations.

NameTypeReqDescription
advancedobject––
budget_tokensinteger––
filesarray––
includearray––
outlineboolean––
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.Apheironn/pasr MCP server?

io.github.Apheironn/pasr runs locally as a PyPI package, launched with uvx pasr-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · pasr-mcp

# add to Claude Code
claude mcp add apheironn-pasr -- uvx pasr-mcp
Common questions

What is the io.github.Apheironn/pasr MCP server?

io.github.Apheironn/pasr is an MCP server listed in the public MCP registry as io.github.Apheironn/pasr. Local, token-budgeted code context with file:line provenance and selection receipts. This page covers its PyPI package (pasr-mcp).

Is the io.github.Apheironn/pasr MCP server safe to use?

io.github.Apheironn/pasr scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. 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 io.github.Apheironn/pasr MCP server expose?

io.github.Apheironn/pasr exposes 5 tools: find_files, find_symbols, find_evidence, find_usages, select_context. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.

Is the io.github.Apheironn/pasr MCP server still maintained?

io.github.Apheironn/pasr is still listed as active in the MCP registry. We last reached this channel on 16 October 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 io.github.Apheironn/pasr MCP server under?

io.github.Apheironn/pasr declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.