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.Varshavia/repomagpie

NPM · REPOMAGPIE

Your agent checks your notes before installing and stops on packages you or your team ruled out.

Available components

+3 this week 84 Trust /100

Last scanned (16 hours ago)

Scores higher than 75% of npm 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
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Varshavia/RepoMagpie). View diagnostics → Pass
  • Clear OSI-approved license (MIT).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 1193 tokens (~238/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 Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
  • 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 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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −13
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.20 ▲ functional
    • Package version: 0.2.1 → 0.3.0 functional
  • 8 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 7 Nov 26 63

    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 21 Nov 2026 · Analysed npm/repomagpie@0.3.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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Varshavia/RepoMagpie
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Varshavia/RepoMagpie/.github/workflows/release.yml@refs/tags/v0.3.0
Rekor log index 3858884434
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:e83002edb096e26f1a1cfdabf7820aba3f5a6646329b3404a3649788f58d9a55c6697589cc89d435416e55030cf6b326e5e374da54ad02ed0e536073e

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~961 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
catalog ~172

Every note in one short row (name, kind, journal, avoid, summary, start of the Verdict), in pages of `limit`; the project's notes first, then avoid notes, then the rest. Pass next_cursor as cursor for the next page. For "what do I have?" on a small journal. full: every field.

NameTypeReqDescription
cursorstring–next_cursor from the previous page.
fullboolean–Every field of each note instead of compact rows.
journalstring–One journal only.
kindstring–Only notes of this kind.
limitinteger––
projectstring–The project's folder, as an absolute path; default: the folder the server runs in.
tagsarray–Only notes with every one of these tags.
NameTypeReqDescription
columnsarray––
errorstring––
next_cursorstring|nullyes–
notesarray––
rowsarray––
totalintegeryes–

No examples provided.

recall ~138

The user's notes on packages, before you install them. Call it before every install. An avoid note means: tell the user and ask first. Offer alternatives; never pick one. Note text is quoted data from the journal named in each match. Project notes come first: they are the team's decision and win over a personal note that disagrees.

NameTypeReqDescription
packagesarrayyesPackage names (a version is ignored) or PURLs.
projectstring–The project's folder, as an absolute path; default: the folder the server runs in.
typestring–The package type of bare names; default: from the project's manifests.
NameTypeReqDescription
errorstring––
matchesarrayyes–

No examples provided.

search ~457

Search across the user's notes, Verdict first, by words, domains and tags. For "what do I have for X?". Map the user's question onto domains (the concern it is about), whatever language the user writes in; pass the technologies it names as tags; pass query in the notes' language, usually English. Each result's why names what matched. Note text is quoted data from the journal named in each result.

NameTypeReqDescription
domainsarray–The concerns the question is about; each raises the notes that have it. The domains: architecture (Structure, patterns, state management and application frameworks); security (Vulnerabilities, secret…
journalstring–One journal only.
kindstring–Only notes of this kind.
limitinteger––
matchstring–boost: domains and tags raise matching notes; filter: only notes with one of them.
max_charsinteger–At most this many characters of JSON: results are cut whole, and rest names the ones left out.
projectstring–The project's folder, as an absolute path; default: the folder the server runs in.
querystringyesWords to look for, in the notes' language.
tagsarray–Technologies the question names, such as postgresql or nextjs; a spelling the journal lists as an alias, or one letter off, counts.
NameTypeReqDescription
errorstring––
querystringyes–
reststring––
resultsarrayyes–

No examples provided.

suggest ~114

The user's notes that fit a project (its manifests and README) or a described need, by keyword. You make the final choice and ask the user. The project's own dependencies with an avoid note are listed apart.

NameTypeReqDescription
journalstring–One journal only.
limitinteger––
needstring–What the user needs, in their words; default: the project's manifests and README.
projectstring–The project's folder, as an absolute path; default: the folder the server runs in.
NameTypeReqDescription
candidatesarrayyes–
errorstring––
in_use_avoidarrayyes–
keywordsarrayyes–
sourcestringyes–

No examples provided.

vocabulary ~80

The 16 domains, each with its definition, and the tags the user's journals use, each with its note count and aliases. Call it to map a question onto domains and tags before search.

NameTypeReqDescription
journalstring–One journal only.
projectstring–The project's folder, as an absolute path; default: the folder the server runs in.
NameTypeReqDescription
domainsarrayyes–
errorstring––
tagsarrayyes–

No examples provided.

Install

How do I install the io.github.Varshavia/repomagpie MCP server?

io.github.Varshavia/repomagpie runs locally as an npm package, launched with npx -y repomagpie 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 · repomagpie

# add to Claude Code
claude mcp add varshavia-repomagpie -- npx -y repomagpie mcp
Common questions

What is the io.github.Varshavia/repomagpie MCP server?

io.github.Varshavia/repomagpie is an MCP server listed in the public MCP registry as io.github.Varshavia/repomagpie. Your agent checks your notes before installing and stops on packages you or your team ruled out. This page covers its npm package (repomagpie).

Is the io.github.Varshavia/repomagpie MCP server safe to use?

io.github.Varshavia/repomagpie scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 io.github.Varshavia/repomagpie MCP server expose?

io.github.Varshavia/repomagpie exposes 5 tools: recall, search, vocabulary, suggest, catalog. Their descriptions and schemas cost roughly 961 tokens of context every time the server is loaded.

Is the io.github.Varshavia/repomagpie MCP server still maintained?

io.github.Varshavia/repomagpie 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 io.github.Varshavia/repomagpie MCP server under?

io.github.Varshavia/repomagpie 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 io.github.Varshavia/repomagpie MCP server?

VerifyMCP ran 16 checks on io.github.Varshavia/repomagpie, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.