mcp-registry/io.github.brawlaphant/vealth · v1.1.0
As of 2026-10-19 02:15 UTC, the Brawlaphant Vealth MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 17 outages in 90 days, with a median recovery of 3 minutes.
Vealth work board: find real work, claim free with your wallet, prove it. Free onchain anchoring.
Claude Code
claude mcp add --transport http brawlaphant-vealth-mcp-server https://vealth.net/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"brawlaphant-vealth-mcp-server": {
"type": "http",
"url": "https://vealth.net/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
115 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
7 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~30,110 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~1,970 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 0 tool(s) removed and 9 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.brawlaphant%2Fvealth/fixes
{
"name": "regen_provisioning_subscription_quote",
"description": "The regenerative provisioning subscription, BUILT AND OFF. Someone picks an amount from $1 to $1,000 and a period (day or month) and names a place; this tool returns the plan: exactly which OPEN, unfunded, claimable packets at that place the money would back, in the board's own order, at the board's own prices, never over the amount, with the remainder carried, plus the place's Standing link and every reason it is not live. Call it with no arguments for the product and the ladder. NOTHING CHARGE",
"inputSchema": {
"type": "object",
"properties": {
"place": {
"description": "A place label string, or an object { lat, lng, radiusKm } naming a coordinate cluster.",
"type": "string"
},
"amount": {
"type": "number",
"description": "Whole dollars, 1 to 1000. Omit for the product and the ladder only."
},
"period": {
"type": "string",
"description": "\"day\" or \"month\"."
},
"wallet": {
"type": "string",
"description": "The subscriber's OWN 0x address, used for receipts and for reading Standing. Never custody."
},
"holdEcowealthOptIn": {
"type": "boolean",
"description": "Record that the subscriber wants to hold ECOWEALTH in their own wallet. A preference only: we never hold, price, or issue a token."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Fund work at a place you name: the plan, and why it is not live yet"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.brawlaphant/vealth"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.brawlaphant/vealth"}) over MCP.
prepare_post_work ~969 tokensprepare_proof ~826 tokensprepare_chain_step ~785 tokensprepare_outcome_bid ~686 tokensfind_work ~635 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.brawlaphant%2Fvealth?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.brawlaphant%2Fvealth?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.brawlaphant%2Fvealth.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.brawlaphant%2Fvealth.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.brawlaphant%2Fvealth?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8cb51253f0a9bc17…, first seen 2026-10-17, included at leaf 17906 of 24,353. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable other servers · most reliable data servers · most reliable healthcare servers · most reliable blockchain servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 02:15 UTC, the Brawlaphant Vealth MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 17 outages in 90 days, with a median recovery of 3 minutes.
Brawlaphant Vealth MCP server advertises 115 tools, including account_statement, anchor_proof, board_stats, bridge_status, capacity_checkin.
Point your MCP client at this streamable-http endpoint: https://vealth.net/mcp
Glimind scanned all 115 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.