Home / MCP registry index / io.github.brawlaphant/vealth

io.github.brawlaphant/vealth

io.github.brawlaphant/vealth in the official MCP registry. Endpoint https://vealth.net/mcp.

The registry describes it as: Vealth work board: find real work, claim free with your wallet, prove it. Free onchain anchoring.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

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

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

code --add-mcp '{"name":"vealth","type":"http","url":"https://vealth.net/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

start_here find_work get_work_packet how_to_claim prepare_claim submit_claim prepare_vote submit_vote prepare_vote_withdraw submit_vote_withdraw prepare_bid submit_bid prepare_backing_withdraw submit_backing_withdraw prepare_token_offer submit_token_offer prepare_token_settlement submit_token_settlement prepare_credit_offer submit_credit_offer prepare_credit_settlement submit_credit_settlement prepare_place submit_place place_status hour_card my_hours my_money day_card my_ledger my_next_step support_next prepare_request submit_request request_status prepare_accept_hours submit_accept_hours prepare_outcome_bid submit_outcome_bid outcome_bid_status prepare_post_work submit_post_work prepare_proof submit_proof prepare_physical_proof submit_physical_proof work_status my_work my_votes estimate_footprint provision_work retire_and_certify verify_work anchor_proof verify_anchor crypto_tokens crypto_wallets net_subscription_quote net_subscription_status regen_provisioning_subscription_quote and 48 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-brawlaphant-vealth/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-brawlaphant-vealth)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers