io.github.MadeByFYI/madeby
Disclose AI authorship of code per the ACO standard — tools for AI coding agents.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
madebyclaude mcp add madeby -- npx -y madeby@0.3.12 mcp
{
"mcpServers": {
"madeby": {
"command": "npx",
"args": [
"-y",
"madeby@0.3.12",
"mcp"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
MadeBy
Who made this thing? — a verifiable content-provenance layer, starting with code.
This is the v2 build. The design lives in the spec docs at the repo root:
ARCHITECTURE.md— asker-pull spine, hash-as-join-key, attestation standard, invariantsTESTING.md— the trust/QA doctrine (publishable conformance; verify without open source)
The first attempt is archived under archive/v1/ — reference only.
The CLI — madeby
The product ships as a zero-infra CLI that runs against your local git history. Disclosure, not detection: it reports what contributors put on the record and never guesses whether code is AI.
npx madeby coverage # the scoreboard: how much of your repo's authorship is disclosed
npx madeby init # drop the ACO AGENTS.md convention + a CI disclosure check into your repo
npx madeby check # the gate: do commits meet .madeby/policy.json? (advisory by default)
npx madeby who # made by whom? what's on the record for a file or the whole repo
npx madeby ai # an AI agent discloses it authored HEAD (Authored-by-ai:)
npx madeby me # affirm you authored HEAD yourself (--with-ai [tool] for assisted)
madeby coverage is the maintainer's scoreboard — known (disclosed) vs unknown authorship, the
human/with_ai/ai mix of the known, and the asserted-vs-verified trust split, as a labeled estimate.
Built on ACO, the open Authorship Certificate of Origin standard. Full docs:
packages/cli · on npm: madeby.
Repo layout
apps/web/ Next.js web app (Vercel)
packages/core/ Shared deterministic trust logic — canonicalization,
fingerprinting, tier resolution + conformance vectors.
This is the publishable / open boundary (TESTING.md §4).
workers/badge/ Cloudflare Worker — live-served badge SVGs (stub)
services/ingestion/ Python (Modal) — public-git ingestion + compute (stub)
Develop
pnpm install
pnpm dev # runs apps/web at http://localhost:3000
pnpm typecheck # tsc across packages
pnpm build # build all packages
pnpm test # trust-gate suite (conformance vectors land in #17)
Requires Node ≥ 22 and pnpm 10.
Provisioning (handoff)
The skeleton builds with no external services. To run against real infrastructure, copy
.env.example → .env and fill in the values listed there.
Provenance (we dogfood)
This repo records its own provenance from commit zero — signed commits, Co-Authored-By: trailers,
and a .madeby/ span manifest. See PROVENANCE.md; verify with
pnpm provenance:verify-trailers.
Tickets
Work is tracked as GitHub issues, organized under epics (#1 dogfood, #4 foundations, #5 read-side, #6 producer-push, #16 trust-QA).
Frequently asked questions
What is io.github.MadeByFYI/madeby?
Disclose AI authorship of code per the ACO standard — tools for AI coding agents.
How do I install io.github.MadeByFYI/madeby?
It runs on your machine. In Claude Code: claude mcp add madeby -- npx -y madeby@0.3.12 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.MadeByFYI/madeby need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.MadeByFYI/madeby open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.MadeByFYI/madeby?
It is published by MadeByFYI. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.