Borrowing it
Nothing to install: this file belongs to getmasv/masv-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/getmasv/masv-mcp-server/main/.kiro/steering/distribution.mdgit clone --depth 1 https://github.com/getmasv/masv-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/getmasv/masv-mcp-server/distribution)<a href="https://agentmods.dev/instructions/getmasv/masv-mcp-server/distribution"><img src="https://agentmods.dev/badge/instructions/getmasv/masv-mcp-server/distribution/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/getmasv/masv-mcp-server/distribution"><img src="https://agentmods.dev/badge/instructions/getmasv/masv-mcp-server/distribution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01080 | $0.01080 |
| Opus 5.5 | $0.00432 | $0.00432 |
| Sonnet 5.5 | $0.00216 | $0.00216 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
masv-mcp-server distribution.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 22d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Distribution
Model
npm is the installable artifact; the directories and registries are metadata pointing back to it. Users
run it with npx @getmasv/masv-mcp-server over stdio.
A remote HTTP server is the goal, because stdio does not run in remote agent sessions and is not listable
on assistant platforms that require a hosted endpoint. See architecture.md.
Releases are automated in CI on tag push. Publishing by hand is the exception, not the process.
Identity
The same server is registered under different names per channel. Keeping this list accurate matters — some listings are hard to find again without the exact identifier.
| Where | Identifier |
|---|---|
| npm | @getmasv/masv-mcp-server (public) |
| Official MCP Registry | io.github.getmasv/masv (mcpName in package.json, name in server.json) |
| Smithery | masv/masv → smithery.ai/server/masv/masv |
| GitHub | github.com/getmasv/masv-mcp-server |
The Smithery listing is not discoverable by search. A registry query for masv returns unrelated
fuzzy matches and not masv/masv; only direct lookup by qualified name resolves. Worth investigating —
Smithery's publish pipeline has deploy/scan/metadata/publish stages, and an incomplete stage is the likely
cause. Until it's fixed, the listing effectively does not exist for anyone browsing.
Channels
Only the first three need an action per release. The rest were registered once and pick up changes from npm, the MCP registry, or the GitHub repo — do not resubmit them on every version.
| Channel | Per release? | How |
|---|---|---|
| npm | yes | npm publish |
| Official MCP Registry | yes | mcp-publisher publish from server.json; version must match npm |
| Smithery | yes | scripts/smithery-publish.sh; payload generated from live tools/list |
| Glama | no — indexes GitHub | One-time; glama.json claims the listing |
| PulseMCP | no — indexes registry | One-time |
| mcp.so | no — submitted once | Web form, already done |
| mcpservers.org | no — submitted once | Web form, already done |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 22d ago Changed · +6 lines · +131 tokens per session faf98b4e91cf
- 26d ago First seen · 74 lines · 949 tokens per session scan A 09ee967b8caf
masv-mcp-server distribution.md is an instructions file published in the GitHub repository getmasv/masv-mcp-server (5 stars, last pushed 21d ago), licensed MIT. It adds 1,080 tokens to every session, about $0.0043 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-25.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.