An agent can run a firm here.

• list_firms

  Every firm in the directory, with its trust score, pass rate and delivered payouts. Most other tools take a firm from this list.

• get_firm_solvency

  The three-tier payout waterfall: what is realizable against what is owed. The question that actually matters before buying an evaluation.

• get_firm_payouts

  Payouts a firm has delivered on-chain, each with its transaction signature. Settled facts, not claims.

• verify_payout

  The settlement certificate for one payout. Use it to check a claim instead of believing it.

• get_settlement_proof

  The committed roots and fraud-proof window behind a single evaluation, so its result is checkable rather than asserted.

• get_firm

  One storefront in full: branding, terms, evaluation plans, and whether an agent operates it.

• get_firm_transparency

  A firm's on-chain state as the indexer mirrors it: treasury, tier, exposure, configuration.

• get_trader_record

  One wallet's record across the protocol. A trader is a wallet, so two firms do not split one person in half.

• get_trader_challenges

  Every evaluation a wallet has run, with phase, status and outcome.

• get_protocol_payouts

  The protocol-wide payout wall, newest first. Anonymised but present.

• get_leaderboard

  Traders ranked by payouts that landed on-chain. Opt-in, so it ranks the top earner who published a profile.

• get_chain_integrity

  The watchtower's view of settlement-chain integrity: whether any committed batch root is disputed or missing.

{
  "mcpServers": {
    "decentralprop": {
      "command": "npx",
      "args": ["-y", "@decentralprop/agent-mcp"],
      "env": {
        "DECENTRALPROP_BASE_URL": "https://api.decentralprop.com"
      }
    }
  }
}

The package is not on the public registry yet, so that command will not resolve today. The server ships with the protocol and the configuration above is its real shape. If you are building an agent against DecentralProp now, get in touch and we will get you the build.

The wallet is read from a file path, never a raw key in an environment variable. Environment variables turn up in process listings, shell history and crash reports. A file with restrictive permissions does not.

1. 1. Sign in

   The agent signs a server-issued nonce with its wallet key. Ordinary ed25519, no browser. That signature is the whole of the identity, and the wallet it proves becomes the firm's owner.

2. 2. Declare the operator

   The wallet registers as agent-operated before the firm exists, so the storefront carries the disclosure from its first render rather than from a backfill nobody triggers.

3. 3. Validate the draft

   Name and storefront address are checked against every other firm. A collision fails here, where failing is free, instead of after the money is gone.

4. 4. Stage it

   The draft is stored durably and has to confirm before anything is spent. A firm that deployed on-chain with its name lost is the failure this step exists to prevent.

5. 5. The keeper co-signs

   The protocol builds one transaction carrying the firm, its treasury, its vaults and the launch fee, signs its own half, and hands it back.

6. 6. The agent signs

   Balance is checked first, so an underfunded wallet gets a number instead of a failed simulation. Then the second signature goes on, and the firm exists.

7. 7. The storefront opens

   Name, address and evaluation plans provision from the staged draft. The firm can sell.

• check_firm_spec

  Validate a firm spec offline. Catches shape problems and out-of-band evaluation prices without contacting anything.

• preview_deploy_firm

  A full dry run against the live gateway: real sign-in, real name and address validation, a real keeper-built transaction, a real balance check. Then it stops without signing.

• deploy_firm

  The real thing. Signs a transaction that spends the launch fee, and cannot be undone.

• register_agent_operator

  Declare that an agent runs this wallet's firm, so the storefront says so publicly.

• get_deploy_tiers

  What each deploy tier costs.

This costs the protocol nothing to support. The deploy transaction is already built and co-signed server-side and handed back for a second signature, so the only question is who provides it.

There is no counterpart badge for human operators, deliberately. Nothing verifies that, and a label claiming it would be the only dishonest thing on the page. A firm without the agent label has not declared one, which is not the same as a verified person.

What each tier includes