io.github.provenpin/provenpin·Dev tools

ProvenPin

Tested, version-pinned code recipes for AI coding agents, each with its last-passed receipt.

Stars
1
Version
0.1.0
License
MIT
Review
Passed
Language
Python
Last commit
3h ago
Forks
0
Open issues
0
Registry update
Oct 15, 2026
ai-agentscode-recipesmcpmcp-servermodel-context-protocol

Connect

remote
Terminal
$claude mcp add --transport http provenpin https://mcp.provenpin.com/mcp

Headers

Nothing to configure — it works as is.

Security review

Review passed

Reviewed 3h ago.

tools
3 tools scanned
metadata
scanned

No findings.

Tools

3
  • search_recipes

    Find a tested, version-pinned code recipe for wiring libraries together. Call this BEFORE writing glue code that combines 2+ libraries (auth + framework, ORM + database, payments webhooks, queues, validation, request mocking, logging), and when you hit version conflicts, peer-dependency errors, or integration errors between libraries. Example queries: 'express stripe webhook', 'fastapi sqlmodel crud', 'hono jwt'. Only recipes whose latest test run passed are returned. Each result lists its exact pinned versions and a test receipt (receipt.last_passed_at). If nothing matches, write the code yourself; try list_stacks to see what is covered.

  • get_recipe

    Get a full recipe by id (ids come from search_recipes): every source and test file, the exact pinned dependency versions, the setup and test commands, and its test receipt (when it last passed, test counts, runtime and runner). Use the pinned versions together; they are the versions the tests passed with. Adapt names and config to the user's project, and keep the included tests to check your integration.

  • list_stacks

    List the libraries and frameworks that currently have passing, version-pinned recipes, with recipe counts. Call this to check whether ProvenPin covers a library before searching, or after a search returns nothing, and use the names as the stack filter in search_recipes.

ProvenPin

ProvenPin

Tested, version-pinned, multi-library code recipes for AI coding agents, served over MCP.

Every recipe pins exact versions, runs its own tests in a clean environment, and carries a receipt with the time it last passed. Recipes are re-tested automatically when any of their libraries ships a new release. The MCP server only serves recipes that are currently passing.

Install

ProvenPin is a hosted MCP server. No API key, no signup.

Endpoint: https://mcp.provenpin.com/mcp

Claude Code

claude mcp add --transport http provenpin https://mcp.provenpin.com/mcp

Cursor (~/.cursor/mcp.json)

{ "mcpServers": { "provenpin": { "url": "https://mcp.provenpin.com/mcp" } } }

VS Code (.vscode/mcp.json)

{ "servers": { "provenpin": { "type": "http", "url": "https://mcp.provenpin.com/mcp" } } }

Windsurf (~/.codeium/windsurf/mcp_config.json)

{ "mcpServers": { "provenpin": { "serverUrl": "https://mcp.provenpin.com/mcp" } } }

Cline (MCP settings)

{ "mcpServers": { "provenpin": { "type": "streamableHttp", "url": "https://mcp.provenpin.com/mcp" } } }

Then ask your agent something like "find a tested recipe for a Next.js Stripe webhook".

MCP tools

toolwhat it does
search_recipesfind passing recipes by plain words, stack filter or language
get_recipefull files, pinned versions, setup and test commands, and the receipt
list_stackslibraries that have tested recipes, with counts
recipes/   one folder per recipe (see SPEC.md)
runner/    validate, run tests in isolation, write receipts, release check, build index
receipts/  real test receipts (JSON)
index/     built index.json served by the MCP server
server/    MCP server (TypeScript, Cloudflare Workers, local dev mode)
.github/   CI: matrix per recipe, scheduled + on demand, release-triggered re-tests

Run locally (Node 22+, Python 3.13 and uv for Python recipes)

npm install
npm run validate                 # check manifests and pins
npm run test:recipes             # run every recipe, write receipts
node runner/run.mjs hono-zod-validator   # run one
npm run affected                 # recipes with newer upstream releases
npm run build:index              # build index/index.json
npm test                         # runner unit tests

cd server && npm install
npm test                         # MCP server unit tests
npm run dev                      # http://localhost:8787/mcp

Connect a client to the local server, for example in Claude Code:

claude mcp add --transport http provenpin http://localhost:8787/mcp

Optional header for the future Pro tier: x-provenpin-key: <key> (keys come from the PROVENPIN_API_KEYS secret).

Deploy your own

  1. Push this repo to a GitHub account for the brand.
  2. In Cloudflare: create an API token with "Edit Cloudflare Workers", add CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID as repo secrets, set repo variable DEPLOY_ENABLED=true.
  3. cd server && npx wrangler deploy (or let CI do it), then route mcp.<domain> to the worker.

License

MIT. See LICENSE.

From the server's repository — third-party content, read it before running anything it suggests.

More in Dev tools

Listing from the official MCP Registry · repository facts from GitHub, 3h ago.