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.MadeByFYI/madeby

NPM · MADEBY

Disclose AI authorship of code per the ACO standard — tools for AI coding agents.

Available components

59 Trust /100

Last scanned (4 hours ago)

Scores higher than 36% 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 Security50
  • Malware scan not yet available for this package.Unverified
  • 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 & Transparency45
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1588 tokens (~144/item across 11 items; 6 tools + 5 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.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 7 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
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.

  • 22 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.3.11 → 0.3.12 functional
  • 21 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 20 Oct 26 0
    • Known CVEs: pass → unverified ▼ security
    • Schema quality: 130 → 144 ▼ functional
    • Dependency health: pass → unverified ▼ functional
    • Package version: 0.3.7 → 0.3.11 functional
    • Package version: 0.3.7 → 0.3.10 functional
    • Package version: 0.3.7 → 0.3.9 functional
    • Package version: 0.3.7 → 0.3.8 functional
  • 19 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.3.6 → 0.3.7 functional
  • 18 Oct 26 +1

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

  • 17 Oct 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 16 Oct 26 61

    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 22 Oct 2026 · Analysed npm/madeby@0.3.12

Provenance No attestation

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

Result No attestation
Ecosystem npm

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 · 6 exposed · ~1,433 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
ai ~171

Made by AI (WRITE): record witnessed AI-authorship spans from YOUR OWN session log into the repo's .madeby/spans (asserted tier, self-reported) — how an agent DISCLOSES its own contribution. Honest by construction: it records only spans whose AI-authored content is STRUCTURALLY PRESENT in the checkout (survives reformatting); anything not present is discarded. Writes only derived attribution, locally — the log/content never leave the machine. It cannot claim a higher tier or attribute work to anyone else.

NameTypeReqDescription
logstring–session transcript path (default: auto-discover the Claude Code transcript)
pathstring–path to the repo (default: the server's working directory)
refstring–commit the spans anchor to (default: HEAD)

No output schema declared.

No examples provided.

check ~114

Evaluate a repo's commits against its .madeby/policy.json disclosure policy (the maintainer gate). Returns pass/fail, the policy mode, and the undisclosed commits. The policy file is optional — with no file (or an invalid one) it degrades to advisory (report-only, never a false gate).

NameTypeReqDescription
pathstring–path to the repo (default: the server's working directory)
rangestring–git commit range, e.g. origin/main..HEAD (default: recent history)

No output schema declared.

No examples provided.

coverage ~184

Authorship coverage scoreboard for a repo — the honest estimate of how much of the code's authorship is ON THE RECORD (known) vs undisclosed (unknown — origin unknown, NEVER guessed), the human/with_ai/ai mix OF THE KNOWN (never of the whole repo), the asserted-vs-verified trust split, and byAgent: the agents and model versions named in the AI commits, exactly as disclosed (a commit naming a tool and its model counts under both). Disclosure, not detection; the report is a labeled estimate (counts only — derive percents at the edge). Use it to show a maintainer their provenance picture and motivate requiring disclosure.

NameTypeReqDescription
pathstring–path to the repo (default: the server's working directory)
rangestring–git commit range, e.g. origin/main..HEAD (default: recent history)

No output schema declared.

No examples provided.

disclose ~360

Disclose authorship on HEAD per ACO — the agent-native disclosure of work you just did. Pick the honest category: 'ai' (an AI authored it; you, the committer, are accountable) adds Authored-by-ai; 'with_ai' (a human authored it WITH AI assistance) adds Authored-by-human + Assisted-by; 'human' adds Authored-by-human. IMPORTANT: if the AI wrote the code and a human is merely committing it, that is 'ai' — do NOT claim 'with_ai'/human authorship the human didn't do. Amends HEAD's MESSAGE only (a testimony, never a content change) and refuses if there are staged changes. Evidence upgrade for the ai category (witnessed spans from a session log) is the CLI `madeby ai --witness`. Read the standard: madeby://guide/aco.

NameTypeReqDescription
category––the honest authorship category (see the description). Defaults from with_ai if omitted.
modelstring–the model version you are running as, e.g. claude-sonnet-5 — written as tool:model. Give it when the repo's AGENTS.md asks; omit it rather than guess.
pathstring–path to the repo (default: the server's working directory)
printboolean–return the disclosure trailer lines instead of amending HEAD — for platforms that make the commit themselves; put them in the commit message's last paragraph
toolstring–the AI tool to name (Assisted-by for with_ai, Authored-by-ai for ai). Default: AI.
with_aiboolean–legacy shorthand: true ⇒ category with_ai, false ⇒ human. Prefer `category`.

No output schema declared.

No examples provided.

init ~325

Align a repository with MadeBy in one call: create .madeby/policy.json (advisory by default — reports, never fails) and the CI disclosure check for the host (github default; azure-devops guided). Idempotent — never clobbers an existing policy or workflow; the one change it makes is mode: "required" raising an existing advisory policy to required (it never lowers one). Returns the files created/skipped and the recommended next steps. Read the resources: madeby://guide/align (full workflow), madeby://guide/enforce (make the check required — the host's control plane, exact commands), madeby://guide/backfill (account for existing history honestly — never fabricate). The ACO convention block is versioned: the result flags an `outdated` AGENTS.md/CLAUDE.md (drift); call again with update:true to refresh just that block in place — how an agent keeps the convention current.

NameTypeReqDescription
hoststring–CI host to wire: github (default) or azure-devops
mode––policy mode to seed (default: advisory)
pathstring–path to the repo (default: the server's working directory)
record_modelboolean–opt in: ask AI disclosures to also name the model version (tool:model) — policy recordModel + an AGENTS.md line. Never turned off by init; default false.
updateboolean–refresh an outdated ACO convention block in place (drift update); default false (report only)

No output schema declared.

No examples provided.

who ~279

Made by whom? Read what's ON THE RECORD about who made this. With `path`: one file's origin — witnessed AI spans (model/tool, precise) where captured, last-touch commit disclosure from git blame elsewhere (approximate, labeled), unknown otherwise. With no `path`: a repo-wide map (the orientation to read BEFORE you work) — the witnessed AI surface plus commit-level disclosure coverage, cheap (no per-file blame). The universal contract is the line range: for a symbol, turn it into a line range with your own tooling (tree-sitter/LSP/ctags) and pass it — MadeBy never parses code. Disclosure, not detection: it reports what's disclosed and never asserts 'human'.

NameTypeReqDescription
commitLimitnumber–map only: recent commits to include in the coverage figure (default 500)
endLinenumber–with `path`: optional 1-based end of a line range
pathstring–repo-relative file to read one file's origin (omit for a repo-wide map)
prefixstring–map only: limit to a path prefix, e.g. src/
repostring–path to the repo (default: the server's working directory)
startLinenumber–with `path`: optional 1-based start of a line range

No output schema declared.

No examples provided.

Install

How do I install the io.github.MadeByFYI/madeby MCP server?

io.github.MadeByFYI/madeby runs locally as an npm package, launched with npx -y madeby. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · madeby

# add to Claude Code
claude mcp add madebyfyi-madeby -- npx -y madeby
Common questions

What is the io.github.MadeByFYI/madeby MCP server?

io.github.MadeByFYI/madeby is an MCP server listed in the public MCP registry as io.github.MadeByFYI/madeby. Disclose AI authorship of code per the ACO standard, tools for AI coding agents. This page covers its npm package (madeby).

Is the io.github.MadeByFYI/madeby MCP server safe to use?

io.github.MadeByFYI/madeby scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. It declares no install or post-install scripts. 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.MadeByFYI/madeby MCP server expose?

io.github.MadeByFYI/madeby exposes 6 tools: init, check, coverage, who, disclose, ai. Their descriptions and schemas cost roughly 1,433 tokens of context every time the server is loaded.

Is the io.github.MadeByFYI/madeby MCP server still maintained?

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

io.github.MadeByFYI/madeby declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.