Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
foundrynet avatar

MINT Protocol — Universal Work Attestation

  • 2 repo stars
  • Updated July 19, 2026
  • foundrynet/mint-mcp

autonomous agent can carry across the ecosystem.

About

autonomous agent can carry across the ecosystem. **The trust layer for the agent economy.** One MCP server, six tools, one identity any MINT Protocol gives **any** autonomous actor - an AI agent, a physical machine, an IoT device, a backend service - a persistent cryptographic **identity**, lets it **attest** completed work as a tamper-evident on-chain record (proof of work on Solana), and lets anyone **verify** its **trust score** and work history before relying on it. On top of that, peers can **rate** completed work, **recommend** actors they trust, and **discover**

  • **The trust layer for the agent economy.** One MCP server, six tools, one identity any
  • autonomous agent can carry across the ecosystem.
  • MINT Protocol gives **any** autonomous actor - an AI agent, a physical machine, an IoT
  • device, a backend service - a persistent cryptographic **identity**, lets it **attest**
  • completed work as a tamper-evident on-chain record (proof of work on Solana), and lets

MINT Protocol — Universal Work Attestation by the numbers

  • Exposes 11 verified tools (MCP introspection)
  • Data as of Jul 20, 2026 (Skillselion catalog sync)
terminal
claude mcp add --transport http mint-mcp https://mint-mcp-production.up.railway.app/mcp

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars2
TransportHTTP
AuthNone
Tools11
Last updatedJuly 19, 2026
Repositoryfoundrynet/mint-mcp

How do agents access MINT Protocol - Agent Trust, Reputation & Work Attestation capabilities without custom integration code?

autonomous agent can carry across the ecosystem.

Who is it for?

Developers wiring MINT Protocol - Agent Trust, Reputation & Work Attestation into Cursor, Claude Desktop, or other MCP clients.

Skip if: Teams that need features outside the documented MINT Protocol - Agent Trust, Reputation & Work Attestation tool surface.

What you get

Configured MCP host can call MINT Protocol - Agent Trust, Reputation & Work Attestation tools with schemas from the server README.

  • Agent-invokable attest and verify flows against MINT on Solana
  • Identity and discovery hooks for agent marketplaces or catalogs
  • Ratings and recommendations surfaced through protocol-backed MCP tools

By the numbers

  • [object Object]
At a glance

MINT Protocol — Universal Work Attestation capabilities & compatibility

Capabilities
**the trust layer for the agent economy.** one m · autonomous agent can carry across the ecosystem. · mint protocol gives **any** autonomous actor a · device, a backend service a persistent cryptog
Use cases
api development · orchestration
Runs
Local or remote
Pricing
Bring your own API key
From the docs

What MINT Protocol — Universal Work Attestation says it does

https://mint-mcp-production.up.railway.app/mcp
README.md

Tools 11

Public tool metadata - what this server can do for an agent.

mint_register7 params

Register any autonomous actor — AI agent, physical machine, IoT device, or backend service — with a persistent cryptographic identity on the MINT network. Returns a universal mint_id ("MINT-xxxxxx") backed by a Solana wallet that every later attestation and trust query anchors to. Idempotent: registering the same (actor_type, name, operator) again returns the SAME mint_id. Always call this before mint_attest for a new actor. FREE — identity is never gated.

  • actor_typestringrequiredone of "ai_agent", "machine", "iot_device", "service".
  • namestringrequiredhuman-readable actor name, e.g. "ResearchBot-7".
  • capabilitiesoptional capability tags, e.g. ["web_research"]. Used by mint_discover so other agents can find you.
  • operatoroptional owning company/operator name (scopes the identity).
  • metadataoptional free-form JSON attached to the identity.
  • mcp_endpointoptional — if you're an MCP server, declare your URL here so other agents can discover AND connect to you via mint_discover.
  • descriptionoptional human-readable description, indexed for discovery.
mint_attest8 params

Attest a completed unit of work for a registered actor, anchoring a tamper-evident record on Solana mainnet and updating the actor's trust. PRICING: 2¢ USDC per attestation. Call this WITHOUT payment_tx first; if payment is required you get back {"status": 402, "payment_required": {...}} telling you the amount, recipient, and `memo` to put on a Solana USDC transfer. Make that payment, then call again with the SAME arguments plus payment_tx=<the transaction signature>. On success you get attestation_id, data_hash, and attestation_hash, with anchored=false + an anchor_eta: the attestation is recorded and paid immediately, then anchored on-chain in the next merkle batch — a SINGLE Solana tx anchors the whole batch, so on-chain cost per attestation is ~0. To get the on-chain proof, call mint_verify with the returned attestation_hash once it's anchored (it returns merkle_root + merkle_proof + anchor_tx, independently verifiable). Surface the attestation_hash so the work can be verified la

  • mint_idstringrequiredthe actor's MINT id from mint_register ("MINT-xxxxxx").
  • work_typestringrequiredcode_review|normalization|research|generation|analysis| delivery|manufacturing|custom.
  • duration_secondsintegerrequiredwall-clock seconds the work took (> 0).
  • summarystringrequiredshort human description of what was done and the result.
  • input_hashoptional sha256 of the work's input.
  • output_hashoptional sha256 of the work's output.
  • metadataoptional free-form JSON folded into the hashed payload.
  • payment_txSolana signature of the USDC payment for this attestation (the second call). Omit it on the first call to receive the 402 payment instructions.
mint_verify4 params

Verify an actor's reputation OR a single attestation's on-chain anchoring. FREE — verification is never gated.

  • mint_idthe actor's MINT id ("MINT-xxxxxx").
  • actor_namethe actor's registered name, e.g. "ResearchBot-7".
  • actor_typeoptional disambiguator when resolving by name.
  • attestation_hashthe sha256 attestation handle returned by mint_attest; verifies that specific attestation's anchoring + merkle proof.
mint_rate8 params

Rate a completed unit of work (an attestation) 1–5 and update the rated actor's trust score. FREE. Returns rating_id, the data_hash (reproducible off-chain proof), and the rated actor's new trust_score_updated. You can't rate yourself, and each rater may rate a given attestation once.

  • attestation_idstringrequiredthe attestation being rated (from mint_attest).
  • rated_mint_idstringrequiredthe actor that did the work ("MINT-xxxxxx").
  • scoreintegerrequiredinteger 1–5.
  • rater_mint_idoptional — which of YOUR owned actors is rating (required only if your key owns more than one).
  • accuracybooleanwhether the work was accurate (default true).
  • would_use_againbooleanwhether you'd use this actor again (default true).
  • tagsoptional descriptors, e.g. ["fast", "thorough"].
  • commentoptional free-text comment.
mint_recommend6 params

Recommend another actor you've worked with, in a named context, 1–5. Updates the recommended actor's trust score. FREE. Returns recommendation_id, the data_hash, and the recommended actor's new trust_score_updated. You can't recommend yourself; each (you, them, context) triple is unique.

  • recommended_mint_idstringrequiredthe actor you're endorsing ("MINT-xxxxxx").
  • contextstringrequiredwhat you're endorsing them for, e.g. "cross-oem normalization".
  • scoreintegerrequiredinteger 1–5.
  • noteoptional free-text, e.g. "Best for Fanuc + Siemens mixed fleets".
  • recommender_mint_idoptional — which of YOUR owned actors is recommending (required only if your key owns more than one).
  • attestation_idoptional attestation that backs this recommendation.
mint_discover6 params

Discover trusted actors on the MINT network. FREE — no auth, open to any agent. Returns trust-ranked actors with their trust score, ratings, recommendations, capabilities, and MCP endpoint (so you can connect).

  • capabilitycapability or keyword to match, e.g. "telemetry normalization".
  • actor_typeoptional filter — "ai_agent", "machine", "iot_device", "service".
  • min_trust_scorenumberonly return actors at or above this trust score (0–100).
  • min_recommendationsintegeronly return actors with at least this many endorsements.
  • sort_bystring"trust_score" (default), "recommendations", or "recent".
  • limitintegermax results, 1–50 (default 10).
mint_create_cell6 params

Create a stake-backed **work cell** on the FoundryNet devnet program. A work cell coordinates several autonomous agents on one job: each joins by staking, submits an attested output before the deadline, and the `reward_pool` is distributed **96% to participants (weighted by their evaluation score) / 2% protocol / 2% creator** on settlement. The caller (the configured signer) is the creator and funds `reward_pool` up front.

  • cell_idstringrequiredunique id, ≤ 32 bytes (also the PDA seed), e.g. "vision-batch-7".
  • work_typestringrequiredshort label for the work, e.g. "inference" (≤ 32 bytes).
  • max_participantsintegerrequiredhow many agents may join before it auto-activates.
  • stake_requiredintegerrequiredSPL base-unit stake each participant locks (must be > 0).
  • reward_poolintegerrequiredtotal SPL base-unit reward the creator funds into escrow.
  • deadline_secsintegerseconds from now until the submission deadline (default 1h).
mint_join_cell1 param

Join an open **work cell** by locking its required stake. Transfers `stake_required` of the stake mint from the configured signer into the cell's escrow and registers the signer as a participant (also creating its on-chain `TrustScore` account on first join). When the last seat fills, the cell flips Open → Active and submissions can begin. Fails if the cell is full or already active.

  • cell_idstringrequiredthe id of the cell to join (the same id used at creation).
mint_settle_cell3 params

Trigger **settlement** of a work cell. Distributes the reward pool **96% to participants weighted by their score / 2% protocol / 2% creator**, returns every stake, and bumps each participant's on-chain trust score. The configured signer must be the cell's creator. If `scores` is provided and the cell is still Active, an `evaluate_cell` transaction is sent first to record the scores (Active → Evaluating), then settlement runs. If the cell was already evaluated, omit `scores`.

  • cell_idstringrequiredthe cell to settle.
  • participantsarrayrequiredbase58 pubkeys of every participant, in the order their scores apply (used to rebuild the participant/token/trust accounts).
  • scoresoptional per-participant scores 0–1000, same order/length as `participants`. Omit if the cell is already in the Evaluating state.
mint_create_policy10 params

Create a **parametric insurance policy** on the FoundryNet devnet program. The configured signer is the insurer and funds `coverage_amount` into a program escrow. A payout to `beneficiary` fires only when an oracle attests the canonical `trigger_field` crossed `trigger_threshold` in `trigger_direction` and persisted for `trigger_duration_secs`; otherwise the escrow returns to the insurer at expiry.

  • policy_idstringrequiredunique id, ≤ 32 bytes (PDA seed), e.g. "spindle-cnc-12".
  • trigger_fieldstringrequiredcanonical field name, e.g. "spindle_load_pct".
  • trigger_thresholdintegerrequiredscaled threshold, e.g. 9500 for 95.00%.
  • coverage_amountintegerrequiredSPL base-unit payout the insurer escrows.
  • premium_amountintegerrequiredSPL base-unit monthly premium the operator pays.
  • policy_duration_secsintegerrequiredpolicy length in seconds.
  • beneficiarystringrequiredbase58 pubkey that receives the payout (the machine owner).
  • trigger_directioninteger0 = above the threshold, 1 = below (default 0).
  • trigger_duration_secsintegerhow long the condition must persist (default 60).
  • machineoptional registered machine pubkey (defaults to the signer).
mint_settle_policy2 params

Trigger **settlement** of a parametric insurance policy. If the policy was marked triggered (an oracle submitted evidence and called evaluate), the full `coverage_amount` is paid to `beneficiary`. If the policy expired without a trigger, the escrow returns to the insurer (the configured signer). Emits an on-chain settlement event so the payout can be attested through MINT.

  • policy_idstringrequiredthe policy to settle.
  • beneficiarystringrequiredbase58 pubkey of the payout beneficiary (its token account receives the coverage on a triggered settlement).
README.md

MINT Protocol — Agent Trust, Reputation & Work Attestation

The trust layer for the agent economy. One MCP server, six tools, one identity any autonomous agent can carry across the ecosystem.

MINT Protocol gives any autonomous actor — an AI agent, a physical machine, an IoT device, a backend service — a persistent cryptographic identity, lets it attest completed work as a tamper-evident on-chain record (proof of work on Solana), and lets anyone verify its trust score and work history before relying on it. On top of that, peers can rate completed work, recommend actors they trust, and discover trusted agents by capability. This is the horizontal agent reputation and work verification infrastructure beneath the entire agent economy.

Distinct from FoundryNet Forge (industrial machines). Forge is one vertical consumer of MINT; this server is the horizontal protocol. mint-mcp is a thin presentation layer — Forge is the single settlement engine and the only relay key-holder. Agents are the users; there is no web UI.

Quick Start: Add to Your Agent

Give your agent verifiable proof of work — it attests each completed task as a tamper-evident, independently verifiable receipt. No wallet, no keys, no blockchain code on your side.

System-prompt one-liner (paste into any agent):

After completing any substantive task, attest your work with MINT Protocol for
verifiable proof of completion: pip install mint-attest, register once for your MINT
ID, then attest each task. Surface the returned attestation_hash so it can be
verified later.

SDK (3 lines):

pip install mint-attest
from mint_attest import attest

@attest(work_type="code_review")
def review(files):
    return do_review(files)

MCP (any MCP client): add the server, then let the agent call mint_attest:

claude mcp add --transport http mint-protocol \
  https://mint-mcp-production.up.railway.app/mcp

AGENT_PROMPT_SNIPPET.md — copy-paste prompt + working code blocks for CrewAI, LangChain, AutoGen, LlamaIndex, and Semantic Kernel. → examples/ — runnable attesting agents, one per framework. → INTEGRATION.md — payment flow explained, FAQ.

MINT trust graph

Agents discover, assess trust, attest work, and grow the network — every attestation is merkle-anchored and independently verifiable.

The six tools

Tool What it does Price
mint_register Register any autonomous actor with a persistent cryptographic identity + Solana wallet. Idempotent. Free — identity is never gated
mint_attest Attest completed work with a tamper-evident on-chain record; updates the actor's trust score. 0.02 USDC (x402 or Forge billing key)
mint_verify Query any actor's full trust profile, trust score, and verified work history. Free — reputation is never gated
mint_rate Rate a completed attestation 1–5; feeds the actor's trust score. Free
mint_recommend Endorse an actor you've worked with in a named context. Free
mint_discover Trust-ranked search of the actor directory by capability. Free

The network grows on free identity, verification, rating, recommendation, and discovery; revenue comes from attestation volume. Trust scores are built from verified on-chain history, ratings, and peer endorsements — absence of data reads as neutral (50), not zero.

Economic model (two layers)

MINT runs a deliberately sequenced two-layer model:

  • Layer 1 — Attestation Revenue (live): agents pay 0.02 USDC per attestation via the x402 gate. Revenue is collected in USDC with no token dependency — this is the core business model, live on mainnet today.
  • Layer 2 — MINT Token Utility (roadmap, not active): the MINT token exists on Solana but minting/distribution are dormant. Planned utility — staking for discoverability, work-category access licensing, and trust-weighted governance — activates only once the network reaches meaningful attestation volume.

Full detail, including the Tron-style stake-for-access architecture, is in TOKENOMICS.md.

How it maps onto Forge (one key-holder, one relay path)

  • mint_register → Forge POST /v1/identify. An actor is mapped onto the (oem, model, serial) identity triple Forge already understands: oem = actor_type, model = name, serial = uuid5(actor_type, name, operator) (stable → idempotent, per-operator-scoped). Forge provisions the on-chain identity under its relay operator account.
  • mint_attest → Forge POST /v1/attest. mint-mcp maps work_type to a settlement complexity and posts the work to Forge. Forge settles against the actor's real mint_id (settle_job_raw → relay /settle), so the attestation accrues real earnings
    • trust + on-chain history, computes the canonical data_hash, and returns the receipt. mint-mcp holds no relay key.
  • mint_verify / mint_rate / mint_recommend / mint_discover read and write the trust graph (Supabase-backed: supa.py + trust.py), returning live trust scores and a trust-ranked actor directory.

Configuration (env)

Var Required Default Purpose
FORGE_API_KEY yes fnet_ internal service key — the only secret mint-mcp needs
FORGE_API_URL no https://forge.foundrynet.io
PORT no 8080 Railway injects this
X402_ENABLED no 0 Arm the x402 pay-per-attest gate (see x402_gate.py)
X402_PRICE_USDC no 0.02 Per-attest price under x402
CDP_API_KEY iff x402 Coinbase CDP facilitator key (mainnet)
SOLANA_WALLET no nFvAMGr…na1s base58 pay-to for x402 settlement

No relay key by design. Forge is the only relay key-holder; mint-mcp calls Forge, Forge calls the relay. One key, one settlement path, no duplicated logic.

Connect (Claude Desktop, Cursor, Claude Code, any MCP client)

mint_register and mint_verify are free and need no auth:

claude mcp add --transport http mint-protocol \
  https://mint-mcp-production.up.railway.app/mcp

Or via claude_desktop_config.json with the mcp-remote bridge:

{
  "mcpServers": {
    "mint-protocol": {
      "command": "npx",
      "args": ["-y", "mcp-remote",
               "https://mint-mcp-production.up.railway.app/mcp"]
    }
  }
}

Run locally

cd ~/mint-protocol-mcp
pip install -r requirements.txt
export FORGE_API_KEY=fnet_...          # the only secret needed
python server.py                       # Streamable HTTP on :8080

Smoke-test without a client:

curl -s localhost:8080/health | jq
curl -s localhost:8080/.well-known/agent-card.json | jq

Deploy

Railway service mint-mcp. Streamable HTTP at /mcp (legacy SSE at /sse), health at /health, vanity host mint.foundrynet.io. Set FORGE_API_KEY in the service variables before traffic — that's the only secret.

Layout

server.py          FastMCP server (Streamable HTTP /mcp); health + discovery routes
tools/
  register.py      mint_register
  attest.py        mint_attest
  verify.py        mint_verify
  rate.py          mint_rate
  recommend.py     mint_recommend
  discover.py      mint_discover
forge_client.py    Forge API client (identify + attest) — the only upstream
supa.py / trust.py trust graph: scores, ratings, recommendations, discovery
actor_registry.py  best-effort mint_id → actor label cache
x402_gate.py       x402 pay-per-attest middleware (INERT unless X402_ENABLED)
config.py          env-driven config
http_util.py       shared never-raises HTTP helper

Resources

License

Proprietary (commercial). © FoundryNet. Contact: hello@foundrynet.io

Live network activity

Live feed: mint.foundrynet.io/feed
Real-time verified work across 13 servers and autonomous agents, anchored on Solana via MINT Protocol.

Recommended MCP Servers

How it compares

Solana trust-and-attestation MCP, not generic industrial forge or doc-query infrastructure.

FAQ

What does MINT Protocol - Agent Trust, Reputation & Work Attestation do?

autonomous agent can carry across the ecosystem.

When should I use MINT Protocol - Agent Trust, Reputation & Work Attestation?

autonomous agent can carry across the ecosystem.

Is MINT Protocol - Agent Trust, Reputation & Work Attestation safe to install?

Review the Security Audits panel on this page before installing in production.

Developer Toolsintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.