retire_and_certify — vealth MCP Tool
retire_and_certify
(retire and certify) is one of 90 tools on the
vealth
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call retire_and_certify from your client
- Claude Code vealth retire_and_certify run in your project directory
- Claude Desktop vealth retire_and_certify ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor vealth retire_and_certify ~/.cursor/mcp.json
- VS Code vealth retire_and_certify .vscode/mcp.json
- Zed vealth retire_and_certify ~/.config/zed/settings.json
- Windsurf vealth retire_and_certify ~/.codeium/windsurf/mcp_config.json
- Cline vealth retire_and_certify ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI vealth retire_and_certify ~/.gemini/settings.json
- Grok vealth retire_and_certify .mcp.json (in your project root)
- ChatGPT vealth retire_and_certify Settings → Connectors → Advanced → Developer mode
- Claude.ai vealth retire_and_certify Settings → Connectors → Add custom connector
- LangChain vealth retire_and_certify pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vealth https://vealth.net/mcp
Other tools on this server
- 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
- prepare_accept_hours
- submit_accept_hours
- 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
- verify_work
- anchor_proof
- verify_anchor
- crypto_tokens
- crypto_wallets
- crypto_route_set
- crypto_lanes
- net_subscription_quote
- net_subscription_status
- regen_provisioning_subscription_quote
- regen_provisioning_subscription_status
- operator_decisions
- crypto_lp_positions
- hydrex_position
- hydrex_votes
- hydrex_claimable
- hydrex_vault
- hydrex_reality
- board_stats
- place_standing
- worker_titles
- compare_titles
- funding_quote
- prepare_funding
- prepare_backing
- submit_backing
- prepare_evidence_surface
- submit_evidence_surface
- prepare_evidence_write
- submit_evidence_write
- payment_options
- account_statement
- payment_preflight
- regen_forum_feed
- regen_governance_status
- regen_address_lookup
- regen_burn_tracker
- regen_token_volume
- labor_unit
- provision_plan
- credential_quote
- gmx_get_positions
- gmx_get_orders
- gmx_get_prices
- prepare_gmx_order
- submit_gmx_order
- prepare_bridge
- bridge_status
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.