Get paid per install
Set a price in $PLINTH — flat, per-call, or free. Revenue settles to your wallet on Solana, no middleman.
Ship a tool. Get installed.
Wrap any capability as an MCP server, describe it in a manifest, and publish to Plinth. Your tool gets a version history, an on-chain integrity record, and a cut of every paid install.
plinth.toml
[tool]
name = "summarizer"
version = "1.0.0"
category = "data"
license = "MIT"
[mcp]
entry = "./server.js"
scopes = ["net:read"]
[pricing]
model = "per_call"
price = "0.002 PLINTH"publish
# build + hash + sign + anchor
plinth publish
// → integrity: sha256:9f2a…c1
// → anchored: tx 4Kp…uZ on solana
// → live: @plinth/summarizer@1.0.0
# cut a new version anytime
plinth publish --bump minorVersions are immutable once anchored. Bumping publishes a new record; old installs keep resolving to the exact build they pinned.
Why publish here
The registry works for builders.
Keep your namespace
Claim a publisher identity and your scope is yours. No one else can publish under your name.
Verifiable by default
Every release anchors a hash. Users — and their agents — can prove the build they ran is the build you shipped.
Get a verified badge
Stake to get verified
Publishers can stake $PLINTH behind a tool to earn the verified badge and rank higher. Ship malware, lose the stake.