Vealth

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 加密货币与区块链

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://vealth.net/mcp

claude mcp add --transport http vealth https://vealth.net/mcp

{
  "mcpServers": {
    "vealth": {
      "url": "https://vealth.net/mcp"
    }
  }
}

{
  "servers": {
    "vealth": {
      "type": "http",
      "url": "https://vealth.net/mcp"
    }
  }
}

https://vealth.net/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档，检查于 2026年11月10日。

通过互联网连接，适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月10日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• start_here

  The door for an agent arriving with nothing. Leads with the front-door set: the few posted packets of physical work an ordinary person can take today (no licence, no special equipment, no supervisor), checked against the live board. Explains that ecological wealth is provisioned

• find_work

  Search Vealth's public board of real ecological and community work packets. Each result includes the pay, the skill level, the exact proof that gets it approved, and a page URL. Free, no account, no wallet. Use this when someone asks for work, a job, a task, or something to do ne

• get_work_packet

  Full detail for a single packet by its id, including the full description and proof requirement. Cost and signer: free and keyless, nothing to sign.

• how_to_claim

  Explains exactly how to claim work and what happens after. Claiming is free. Returns instructions, never performs the claim, because claiming requires the worker's own wallet signature. Pass the optional workId of the job in hand and the NEXT_CALL is prepare_claim for that job (w

• prepare_claim

  Start claiming a packet for a wallet you control. Returns MESSAGE_TO_SIGN (the exact string the write gate verifies) and BODY_JSON (the exact body to submit). Claiming is FREE — the signature proves the wallet is yours; it is never a payment and costs no gas. Sign MESSAGE_TO_SIGN

• submit_claim

  Complete the claim: pass the BODY_JSON string from prepare_claim UNCHANGED plus the signature your wallet produced over MESSAGE_TO_SIGN. This server relays the signed request to the same public claim gate any HTTP client uses — it holds no keys and no funds, and without your sign

• prepare_vote

  Say a job should matter more or less. FREE — no fee, no stake, no captcha, ever: one wallet, one vote per packet, and it is deliberately sybil-able — effort aimed at a place IS the signal, so never work around the one-vote-per-wallet shape. A vote spends no money, certifies no pr

• submit_vote

  Complete the vote: pass workId, the BODY_JSON from prepare_vote UNCHANGED, and the signature your wallet produced over MESSAGE_TO_SIGN. This server relays the signed request to the same public vote gate any HTTP client uses — it holds no keys and no funds, and without your signat

• prepare_vote_withdraw

  Take back a vote you cast — the position leaves the active tally, but the event stays in the packet's public history (withdrawing is not erasing). Free, same signature-is-the-gate rule as casting. Returns MESSAGE_TO_SIGN and BODY_JSON; sign with the SAME wallet that cast the vote

• submit_vote_withdraw

  Complete the withdrawal: pass workId, the BODY_JSON from prepare_vote_withdraw UNCHANGED, and the signature over MESSAGE_TO_SIGN. Free, always, and relays to the same public gate any HTTP client uses. Cost and signer: free, no gas; signed by the person's own wallet or passkey, an

• prepare_bid

  Name your price instead of claiming at the posted pay. FREE — a signed offer, no fee, no gas. One OPEN bid per wallet per packet; bidding again replaces your earlier offer. The packet's creator decides: accepting your bid mints your claim AT YOUR PRICE, through the same admission

• submit_bid

  Complete the bid: pass workId, the BODY_JSON from prepare_bid UNCHANGED, and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to the same public bid gate any HTTP client uses; this server holds no keys and no funds. Free with a valid signature. Returns your recorde

• prepare_backing_withdraw

  Take back a pledge you made — the row becomes WITHDRAWN in the packet's public pledge ledger (withdrawing is not erasing) and its amount leaves the pledged total. Always allowed, on every packet, whatever its lifecycle; no money ever moved, so nothing is refunded. Free, same sign

• submit_backing_withdraw

  Complete the withdrawal: pass workId, the BODY_JSON from prepare_backing_withdraw UNCHANGED, and the signature over MESSAGE_TO_SIGN. Free, always, and relays to the same public gate any HTTP client uses. Cost and signer: free, no gas; signed by the person's own wallet or passkey,

• prepare_token_offer

  Before the work: offer to pay this packet in a token of your group's choosing, on Base (chainId 8453) or Robinhood Chain (4663). FREE — a signed offer, no fee, no gas, NO money moves and none is held. The board reads balanceOf for the record (verified or intent-only), the token's

• submit_token_offer

  Complete the offer: pass workId, the BODY_JSON from prepare_token_offer UNCHANGED, and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to the same public door any HTTP client uses (POST /labor/work/:workId/back/token); this server holds no keys, no funds and no to

• prepare_token_settlement

  After your proof is approved and someone paid you in a token on chain: name the chain (8453 Base or 4663 Robinhood Chain) and the transaction hash, and the board reads the transfer to YOUR wallet and writes the same settlement record a dollar payout writes — your work record, the

• submit_token_settlement

  Complete the record: pass workId, the BODY_JSON from prepare_token_settlement UNCHANGED, and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to POST /labor/work/:workId/settle/token; this server holds no keys, no funds and no tokens, and reads the chain only. Free

• prepare_direct_offer

  Before the work: offer to pay this packet yourself, OFF the board, in US dollars, through your own card processor (your own Stripe, for example), your bank, or any way you and the worker agree. FREE: a signed statement, no fee, no gas, NO money moves through Vealth and none is he

• submit_direct_offer

  Complete the offer: pass workId, the BODY_JSON from prepare_direct_offer UNCHANGED, and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to the same public door any HTTP client uses (POST /labor/work/:workId/back/direct); this server holds no keys and no funds. Fre

• prepare_direct_settlement

  After your proof is approved and the payer paid you directly (card, bank, or any way you agreed): name the payer's wallet, the dollars you received and how, plus an optional short receipt id. The board accepts it only from a payer with standing (an active direct offer your amount

• submit_direct_settlement

  Complete the record: pass workId, the BODY_JSON from prepare_direct_settlement UNCHANGED, and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to POST /labor/work/:workId/settle/direct; this server holds no keys and no funds. Free with a valid signature. Returns th

• prepare_credit_offer

  Before the work: offer to pay this packet in verified stewardship hour (VSH) ecocredits from a named batch on Regen Ledger (chain regen-1). FREE, a signed offer, no fee, no gas, NO credit moves and none is held. You give NO Regen address: the board derives the regen1 account your

• submit_credit_offer

  Complete the offer: pass workId, the BODY_JSON from prepare_credit_offer UNCHANGED, and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to the same public door any HTTP client uses (POST /labor/work/:workId/back/credit); this server holds no keys, no funds and no

• prepare_credit_settlement

  After your proof is approved and someone sent you VSH ecocredits on Regen Ledger: name the batch denom and the regen-1 transaction hash, and the board reads the transfer that reached the regen1 account YOUR signing key controls, then writes the same settlement record a dollar pay

• submit_credit_settlement

  Complete the record: pass workId, the BODY_JSON from prepare_credit_settlement UNCHANGED, and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to POST /labor/work/:workId/settle/credit; this server holds no keys, no funds and no credits, and reads regen-1 only. Fre

• prepare_place

  Your place is not on the board yet: this is how it gets there. FREE, a signed statement, no fee, no gas, no money moves and nothing is held. You give the pin where you are standing, the radius of the place, plain words for its name, the name of the local person who will acknowled

• submit_place

  Complete the handover: pass the BODY_JSON from prepare_place UNCHANGED and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to the same public door any HTTP client uses (POST /labor/place/intake); this server holds no keys and no funds. Free with a valid signature.

• place_status

  Read an intake you handed over: pending, posted, or rejected with the reason. Free, keyless, no wallet needed. Pass intakeId for one, or wallet to list every place that wallet handed over. While it says pending there is nothing to claim yet and no packet exists; when it says post

• hour_card

  The ONE document to read to a person before they start: what the place is and the circle every GPS fix must land inside, what to bring and what the safety notes say, the method steps in order, the proof to hand in as a checklist, what the land gets, what the worker gets and wheth

• my_hours

  The time-bank statement for one wallet: hours claimed, hours a human accepted, hours that reached a settlement, VSH credit that reached them as payment for their own work, VSH credit they spent through the credit door to pay somebody else's work, and what this board's record says

• my_money

  Everything one wallet was paid, is owed as a receipt, is only offered, and can do next, in a single free keyless read: dollars that settled, every OTHER token that settled and in what amount, open work receipts, token offers still standing on packets they took (each with the toke

• prepare_credential_record

  Some jobs, like the credentialed construction-safety jobs in Los Angeles, are open only to a person whose credential a human has checked. This is how a CHST or STS (BCSP) gets on record. FREE, a signed statement, no fee, no gas, no money moves. You give the issuer (BCSP), the cre

• submit_credential_record

  Complete the record: pass the BODY_JSON from prepare_credential_record UNCHANGED and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to the same public door any HTTP client uses (POST /labor/credential-record); this server holds no keys and no funds. Free with a v

• credential_record_status

  Read the credential records for one wallet: for each, the credential, the issuer, and whether it is pending (waiting for a person to check it), verified (a person read the issuer's public lookup, with the date and the page), not found, or run out. Only a verified record inside it

• prepare_site_authorization

  Some jobs, like the credentialed construction-safety jobs in Los Angeles, are open only to a worker whose credential a person has checked AND whom the site itself has authorized. This is how the site says so. You are the contractor that posted the job, or a wallet that contractor

• submit_site_authorization

  Complete the authorization: pass workId, the BODY_JSON from prepare_site_authorization UNCHANGED and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to the same public door any HTTP client uses (POST /labor/work/:workId/site-authorization); this server holds no ke

• site_authorization_status

  Read whether the site's authorization of one worker wallet on one job stands right now: authorized, withdrawn, no longer standing because its signer stopped speaking for the job's site, or none. A worker asks it to see whether the contractor's signature has landed; a contractor a

• day_card

  Answers "what do I do here today": for one place and one wallet (or a named crew), today's list of work in order, in blocks of 30 minutes, within the hours the person says they have. It is compiled from what already exists: the place's Standing and which of its conditions are due

• my_ledger

  Answers "what is the whole record behind this person": for one wallet, every event the board holds in time order, each with a plain label, the job it belongs to and the receipt that proves it. It lists jobs claimed, proofs handed in and whether each was accepted or not, settlemen

• my_next_step

  Answers "what should this person do next, and what trains them for the job after": for one wallet, it reads the person's own record (the work the board holds as done and accepted, proof decided as a reviewer, titles declared) and maps it onto the library's own ladders to name ONE

• support_next

  Answers "where should the next dollar go" (view backer) or "what should I do next near me" (view worker): one ranked list of open claimable jobs, place conditions that are not yet covered, and open outcome bids, each row explained in plain words by named score parts that add up t

• prepare_request

  Prepare an attributable request for an existing work packet, a canonical definition, or a specific objective. Unlike posting a new packet, this asks the existing /labor/request bridge to resolve the need to one governed packet or an explicit blocker. Your own wallet signs the exa

• submit_request

  Relay BODY_JSON from prepare_request, unchanged, with the caller's personal_sign signature over MESSAGE_TO_SIGN to the existing /labor/request gate. Never hold or sign a key or send payment. The gate validates wallet ownership and either records a demand request, resolves it to a

• request_status

  Read one public signed request by its id from the existing /labor/requests door, including the request's current resolution and existing next-action projection. This is a read, not a new request, a funding event or proof of completion. If a work packet has been linked, use fundin

• prepare_accept_hours

  You were named on a work packet as the person who accepts its hours: this is how you do that. FREE and KEYLESS, a signed judgment, no fee, no gas. NOBODY PAYS ANYBODY HERE: accepting hours releases no wage, records no settlement and mints no token, it writes onto the record that

• submit_accept_hours

  Complete the acceptance: pass the BODY_JSON from prepare_accept_hours UNCHANGED and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to the same public door any HTTP client uses (POST /labor/work/:workId/accept-hours); this server holds no keys and no funds. FREE a

• prepare_outcome_bid

  Offer ONE price to move ONE condition of ONE place up ONE rung of the Vealth Standard (Unread, Read, Tended, Kept, Whole), over open packets at that place that serve that condition (find_work near the place; place_standing gives each condition's rung). Name every packet with its

• submit_outcome_bid

  Complete the outcome bid: pass the BODY_JSON from prepare_outcome_bid UNCHANGED and the signature your wallet produced over MESSAGE_TO_SIGN. Relays to POST /labor/outcome-bids, the same public door any HTTP client uses; this server holds no keys and no funds. Free with a valid si

• outcome_bid_status

  Where an outcome bid stands, recomputed this moment: offered, accepted, working, hold lapsed, settled, or rung reached; every named packet's real state (open, claimed, proved, accepted by a person, settled, or claimed outside the bid); and the condition's rung at the place when t

• prepare_post_work

  Put work YOU define on the public board — your place, your problem, your terms. Pass the creator wallet, a title, what needs doing, where, and the proposed pay. Returns MESSAGE_TO_SIGN (proving the creator wallet is yours) and BODY_JSON. Posting is FREE when the creator wallet si

• submit_post_work

  Complete the posting: pass BODY_JSON from prepare_post_work UNCHANGED and the creator wallet's signature over MESSAGE_TO_SIGN. A valid creator signature posts for free (the signature is the gate, not a fee); xPayment is only for a post with no signature, the $0.05 x402 door. A fa

• prepare_proof

  You did the work — start handing in proof. Pass the packet's workId, your claimId (from submit_claim), your wallet, and proof items matching the packet's own proof line (photos with GPS for field work; documents/text for digital work). On an hours-eligible job, state the hours yo

• submit_proof

  Relay the signed proof to the public completion gate: pass workId, the BODY_JSON from prepare_proof UNCHANGED, and the signature over MESSAGE_TO_SIGN. Approval follows (the creator, or self-verification where the packet supports it); on a funded packet, approval releases the wage

• prepare_physical_proof

  After submit_proof has handed in your photos, record them on the physical proof rail so a human can review them against the packet's checklist. Pass workId, claimId, your wallet and the on-site gps you captured (the board never reads a stored location back to a caller, because th

• submit_physical_proof

  Relay the signed physical proof to the same public door any HTTP client uses (POST /labor/work/:workId/physical-proof): pass workId, the BODY_JSON from prepare_physical_proof UNCHANGED, and the signature over MESSAGE_TO_SIGN. FREE with a valid signature from the claiming wallet.

• work_status

  Live lifecycle state of one packet — OPEN, CLAIMED, PROOF_SUBMITTED, APPROVED, PROOF_REJECTED, SETTLED or EXPIRED — plus its honest pay status (funded vs proposed). Free, keyless, read-only. Cost and signer: free and keyless, nothing to sign.

• my_work

  One question, the whole picture for ONE wallet: every packet it claimed and where each one stands, what is waiting on the person (proof not handed in, proof rejected and the reason given), what settled and its public receipt, and what is newly open nearby that fits the kind of wo

• my_votes

  One wallet's whole demand history: every packet it voted for or against, and every packet it pledged to back — both free, signed acts that move no money. Use this when someone asks what they voted for, whether their vote is still active, or what they have pledged. A pledge here i

• estimate_footprint

  The anchor tool. Give a rough token or call count for your AI session and get an order-of-magnitude CO2e estimate PLUS the real, verifiable ecological work you can provision to answer it on Vealth. Vealth does NOT sell paper offsets — it provisions maintenance of the commons: you

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月10日

• ! 注意

  作者与仓库一致

  发布者（brawlaphant）不是仓库所有者（brawlaphant）；可能是其他人代为上架的

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 98 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 60 个工具描述，未发现针对 AI 的隐藏指令

与“加密货币与区块链”中的其他服务器比较i

• 星标数多于此分类中其他 1635 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1635 个服务器的 34% 更新
• 基础检查结果等于或优于此分类中其他 1635 个服务器的 49%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README