Repowise
PYPI · REPOWISE · 2 COMPONENTS
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
Available components
Last scanned (8 hours ago)
Scores higher than 58% of PyPI servers
Category Code Search and Documentation
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 Security49
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 15 of 145 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 repowise-dev/repowise). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1341 tokens (~268/item across 5 items; 5 tools + 0 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 Management40
- Stability check failed: the tool surface changed between 0.59.0 and 0.61.0: 5 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
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 6 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
Checks we ran (15)
- 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
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
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 →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40.
- 20 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33.
- 18 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27.
- 15 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 13 Nov 26 −21
- Malware scan: pass → unverified ▼ security
- Stability: 0.60 → fail ▼ security
- Schema quality: 2755 → 1341 ▲ functional
- Package version: 0.60.1 → 0.61.0 functional
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 21 Nov 2026 · Analysed pypi/repowise@0.61.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 | repowise-dev/repowise |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/repowise-dev/repowise/.github/workflows/publish.yml@refs/tags/v0.61.0 |
| Rekor log index | 3857558470 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:a2f19fe7c4354c68cfb8740b338baf18b9a3a50f4a7a6875c3a0156384e75c8b |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 145 packages
| Packages resolved | 145 |
|---|---|
| Stale | 14 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_answer ~160
Answer a how, where, or why question in one evidence-grounded call. High confidence may be used directly; medium and low lead with the evidence to verify. ``candidate_files`` ranks files worth opening that the citations do not name. Args: question: One question about one subject. Split "where is X and when does Y run" into two calls; do not paste a whole multi-part task. scope: repository-relative path prefix. repo: usually omitted. include: ``["evidence"]`` expanded evidence; ``["diagnostics"]`` adds ``retrieval_quality``.
| Name | Type | Req | Description |
|---|---|---|---|
| include | – | – | – |
| question | string | yes | – |
| repo | – | – | – |
| scope | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_context ~283
Triage card for files / modules / symbols — relationships, not source bytes. Returns summary, signatures with lines, hotspot, fix_history and decision titles; either risk cue means get_risk. Batch targets in one call. Whole file, body-elided and line-verified: include=["skeleton"] in ONE call, or Read it; do not call get_symbol per signature. Rename: include=["references"] is the whole edit set when ``complete``. Which files in a directory lack tests: include=["files"] on it. Args: targets: paths, "path::Symbol", "component:<name>", "change:<id>" (pr-123 or a sha), "package:<name>". include: callers | callees | references (+ adds comments) | skeleton | skeleton+ | files | symbols (all, not top 15) | decisions | full_doc | ownership | last_change | metrics | community | health | doc_drift | changes | provenance | suspects | facts. compact: False adds structure, imports, docstrings. symptom: issue text or stack trace to rank ``suspects`` on. repo: usually omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | – |
| include | – | – | – |
| repo | – | – | – |
| symptom | – | – | – |
| targets | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_symbol ~259
Follow-up read of one symbol whose id another response already gave you. **Not an entry point.** ``get_answer`` ships ``symbol_bodies``; for a whole file ``get_context(include=["skeleton"])`` or a Read is one call. Never walk a file symbol by symbol. Returns verified, line-numbered source; a truncated result carries the ``continuation`` to pass back. Args: symbol_id: "path/to/file.py::Name", "path/to/file.py:140-180" for a live range, or an omission ref. A bare file path is not an id. depth: 1 (default) is this symbol alone; 2-3 also returns the bodies it calls, transitively, in ``callee_bodies``. context_lines: extra lines before/after (0-50). query: regex/substring filter on an omission ref's lines. id, reference: aliases for ``symbol_id``. repo: usually omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| context_lines | integer | – | – |
| depth | integer | – | – |
| id | – | – | – |
| query | – | – | – |
| reference | – | – | – |
| repo | – | – | – |
| symbol_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_why ~205
Why this code is shaped this way — decision records + evidence commits. Call before a refactor or pattern divergence. Query: a question, a file path, a question with ``targets``, or nothing (decision dashboard). A path gets the rules in force first, then labelled background records. ``authority: accepted`` means somebody signed the decision; ``answer_basis`` names the strongest evidence lane, and only ``decision`` is a ruling. Args: query: question, file/module path, or omit for the dashboard. targets: file paths to anchor the search. id: decision or ``ev_...`` evidence id from any tool. reference: structured evidence reference. repo: usually omitted. include: ``["history"]``: a path's origin story, commits, episodes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | – | – |
| include | – | – | – |
| query | – | – | – |
| reference | – | – | – |
| repo | – | – | – |
| targets | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_codebase ~284
Find code by concept, symbol, or path — hybrid codebase search. For a how/where/why question call get_answer. Use this to enumerate matches, resolve an identifier to a symbol_id, or find files for get_context. Identifier, literal, `a|b|c` or regex queries return `lines` (path, line, kind, text; definitions first, one group per alternative) read from live files; when `complete` is true they are every match, so no grep is needed. `candidates` lists distinct files to Read, best first. Args: query: identifier, `a|b` alternation, regex, path, or natural language. limit: max results (default 5). mode: auto (by query shape) | symbol | path | concept | hybrid. kind: implementation | test | config | doc. symbol_kind: function | class | method | ... page_type: file_page | module_page. repo: alias, or "all" for workspace-wide. pattern: alias for query.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | – | – | – |
| limit | integer | – | – |
| mode | string | – | – |
| page_type | – | – | – |
| pattern | – | – | – |
| query | string | – | – |
| repo | – | – | – |
| symbol_kind | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
How do I install the Repowise MCP server?
Repowise runs locally as a PyPI package, launched with uvx repowise mcp --transport stdio. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
pypi · repowise
claude mcp add dev-repowise-repowise -- uvx repowise mcp --transport stdio
What is the Repowise MCP server?
Repowise is an MCP server listed in the public MCP registry as dev.repowise/repowise. Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health. This page covers its PyPI package (repowise).
Is the Repowise MCP server safe to use?
Repowise scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 Repowise MCP server expose?
Repowise exposes 5 tools: get_answer, get_context, get_symbol, get_why, search_codebase. Their descriptions and schemas cost roughly 1,191 tokens of context every time the server is loaded.
Is the Repowise MCP server still maintained?
Repowise is still listed as active in the MCP registry. We last reached this channel on 21 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 Repowise MCP server under?
Repowise declares the AGPL-3.0-or-later 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 Repowise MCP server?
VerifyMCP ran 15 checks on Repowise, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Repowise: Malware scan. 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.