io.github.brawlaphant/vealth
REMOTE · VEALTH.NET · SCANNED OCT 4
Vealth work board: find real work, claim free with your wallet, prove it. Free onchain anchoring.
Available components
Recent critical change
Authorization (1 Sept 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit_gmx_order). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 21147 tokens (~213/item across 99 items; 99 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 2 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "prepare_vote_withdraw" implies "withdraw" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 100 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.brawlaphant/vealth MCP server?
io.github.brawlaphant/vealth is a hosted endpoint at https://vealth.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · vealth.net
claude mcp add --transport http brawlaphant-vealth 'https://vealth.net/mcp'
{
"mcpServers": {
"brawlaphant-vealth": {
"url": "https://vealth.net/mcp"
}
}
} {
"servers": {
"brawlaphant-vealth": {
"type": "http",
"url": "https://vealth.net/mcp"
}
}
} [mcp_servers.brawlaphant-vealth] url = "https://vealth.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"brawlaphant-vealth": {
"type": "remote",
"url": "https://vealth.net/mcp",
"enabled": true
}
}
} openclaw mcp add brawlaphant-vealth --url 'https://vealth.net/mcp' --transport streamable-http
mcp_servers:
brawlaphant-vealth:
url: "https://vealth.net/mcp" {
"McpServers": {
"brawlaphant-vealth": {
"Transport": "http",
"Url": "https://vealth.net/mcp"
}
}
} assistant mcp add brawlaphant-vealth -t streamable-http -u 'https://vealth.net/mcp'
{
"mcpServers": {
"brawlaphant-vealth": {
"type": "http",
"url": "https://vealth.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Oct 26 0
- Tool “compare_titles” rewrote its description, which is the text the model reads security
- Tool “worker_titles” rewrote its description, which is the text the model reads security
- 1 Oct 26 0
- New tool “submit_feedback” functional
- New tool “submit_funding” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Tool “prepare_post_work” rewrote its description, which is the text the model reads security
- Tool “start_here” rewrote its description, which is the text the model reads security
- New tool “prepare_physical_proof” functional
- New tool “provision_plan” functional
- New tool “submit_physical_proof” functional
- “prepare_claim” added an optional parameter “crew” cosmetic
- “prepare_post_work” added an optional parameter “flags” cosmetic
- “prepare_post_work” added an optional parameter “proofRequirements” cosmetic
- “prepare_post_work” added an optional parameter “safetyNotes” cosmetic
- “prepare_post_work” added an optional parameter “skillLevel” cosmetic
- “prepare_proof” added an optional parameter “crew” cosmetic
- “prepare_proof” reworded the description of “proofs” cosmetic
- 23 Sept 26 0
- “prepare_claim” added an optional parameter “attestAtLeast18” cosmetic
- “prepare_claim” added an optional parameter “attestSafetyRead” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 15 Sept 26 0
- Tool “hour_card” rewrote its description, which is the text the model reads security
- New tool “my_money” functional
- “hour_card” added an optional parameter “lang” cosmetic
- 14 Sept 26 0
- New tool “regen_provisioning_subscription_quote” functional
- New tool “regen_provisioning_subscription_status” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://vealth.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vealth.net | CN=YE2,O=Let's Encrypt,C=US | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5e021f9762975da00b3738cc39185efcc07 |
| SANs: *.vealth.net, vealth.net | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vealth.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| vealth.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data:; frame-src 'self' https://embed.music.apple.com; connect-src 'self' https://cloudflareinsights.com https://base.publicnode.com https://base.llamarpc.com https://mainnet.base.org https://1rpc.io https://regen-api.polkachu.com https://keys.coinbase.com https://rpc.wallet.coinbase.com https://api.fiscaldata.treasury.gov; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; object-src 'none'; upgrade-insecure-requests; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vealth.net/mcp | Verified | 200 | |
| http (plaintext) | http://vealth.net/mcp | HTTPS enforced | 301 | https://vealth.net/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
understand_need Turn a health or care problem into bounded coordination work ~140
Private, read-only coordination. Converts the person's own description into a nonclinical coordination frame, routes explicit emergency/crisis/withdrawal/safeguarding signals to qualified humans, and never diagnoses, treats, prescribes, or creates an employer-facing health record.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| safetySignal | string | – | Only pass a stronger signal when the user/context explicitly supports it. Never infer one from vague distress. |
| summary | string | yes | Minimum-necessary description of what is making life or care harder. Do not include names, date of birth, full address, medical-record number, insurance/member id, account credentials, or other ident… |
| Name | Type | Req | Description |
|---|---|---|---|
| claimId | string | – | – |
| claimable | boolean | – | – |
| definitionOfDone | object|array|string|null | – | – |
| fulfillableBy | array | – | – |
| funded | boolean | – | – |
| needs_from_caller | array | – | – |
| next_call | object | – | – |
| notClaimableReason | string | – | – |
| ok | boolean | – | – |
| payUsd | number | – | – |
| proofRule | string | – | – |
| tool | string | – | – |
| workId | string | – | – |
No examples provided.
verify_anchor Check whether a file was anchored, and when ~93
Given the SHA-256 of a file, say whether it is anchored, when, and return the merkle proof plus the transaction so the caller can check it independently without trusting Vealth. Use it to confirm someone held a document when they claim they did, or to confirm your own submission landed. Free and keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| sha256 | string | yes | SHA-256 of the file, 64 lowercase hex characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| claimId | string | – | – |
| claimable | boolean | – | – |
| definitionOfDone | object|array|string|null | – | – |
| fulfillableBy | array | – | – |
| funded | boolean | – | – |
| needs_from_caller | array | – | – |
| next_call | object | – | – |
| notClaimableReason | string | – | – |
| ok | boolean | – | – |
| payUsd | number | – | – |
| proofRule | string | – | – |
| tool | string | – | – |
| workId | string | – | – |
No examples provided.
verify_work Verify a work claim into a signed certificate ~164
Check a proof URI is safely machine-checkable, then get the exact path to Vealth's paid verification door: a SIGNED, re-checkable certificate anyone can reproduce — no oracle, no judge. Digital claims only; physical proof (photo + GPS + signature) is honestly routed to human review, never faked. This tool validates and instructs; the caller pays the door from their own wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| definitionId | string | – | Optional self-verifying definition id, if known. |
| proofUri | string | yes | https URL of the LIVE proof to verify. No auth, no query parameters. |
| standard | string | – | Optional standard key the claim is made against. |
| workId | string | – | Optional board packet id, to check its specific proof requirement. |
| Name | Type | Req | Description |
|---|---|---|---|
| claimId | string | – | – |
| claimable | boolean | – | – |
| definitionOfDone | object|array|string|null | – | – |
| fulfillableBy | array | – | – |
| funded | boolean | – | – |
| needs_from_caller | array | – | – |
| next_call | object | – | – |
| notClaimableReason | string | – | – |
| ok | boolean | – | – |
| payUsd | number | – | – |
| proofRule | string | – | – |
| tool | string | – | – |
| workId | string | – | – |
No examples provided.
work_status Where a packet stands right now ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| workId | string | yes | The packet id. |
| Name | Type | Req | Description |
|---|---|---|---|
| claimId | string | – | – |
| claimable | boolean | – | – |
| definitionOfDone | object|array|string|null | – | – |
| fulfillableBy | array | – | – |
| funded | boolean | – | – |
| needs_from_caller | array | – | – |
| next_call | object | – | – |
| notClaimableReason | string | – | – |
| ok | boolean | – | – |
| payUsd | number | – | – |
| proofRule | string | – | – |
| tool | string | – | – |
| workId | string | – | – |
No examples provided.
worker_titles The titles and credentials one wallet declares, with status and evidence ~178
The Vealth titles register for one wallet: every title the worker declared on their own signature (CHST, OSHA 30, CPR, a guard card, anything), each with a status derived from the worker's OWN declared dates (current, expired, unknown_expiry), a verify pointer to the ISSUER'S record (we carry the link, we never fetch it), board evidence in that title's scope (on-chain-confirmed settlements and reviews the wallet accepted), and the declaration's anchor hash. Self-declared and shown as such; nothing here gates a claim or makes hiring, employment, qualification, or fitness decisions for an employer. Public mirror: https://vealth.net/labor/worker/<wallet>/titles. Free, keyless, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | The worker's wallet address (0x…). |
| Name | Type | Req | Description |
|---|---|---|---|
| claimId | string | – | – |
| claimable | boolean | – | – |
| definitionOfDone | object|array|string|null | – | – |
| fulfillableBy | array | – | – |
| funded | boolean | – | – |
| needs_from_caller | array | – | – |
| next_call | object | – | – |
| notClaimableReason | string | – | – |
| ok | boolean | – | – |
| payUsd | number | – | – |
| proofRule | string | – | – |
| tool | string | – | – |
| workId | string | – | – |
No examples provided.
What is the io.github.brawlaphant/vealth MCP server?
io.github.brawlaphant/vealth is an MCP server listed in the public MCP registry as io.github.brawlaphant/vealth. Vealth work board: find real work, claim free with your wallet, prove it. Free onchain anchoring. This page covers its hosted endpoint (https://vealth.net/mcp).
Is the io.github.brawlaphant/vealth MCP server safe to use?
io.github.brawlaphant/vealth scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.brawlaphant/vealth MCP server expose?
io.github.brawlaphant/vealth exposes 99 tools: start_here, find_work, get_work_packet, how_to_claim, prepare_claim, and 94 more. Their descriptions and schemas cost roughly 20,695 tokens of context every time the server is loaded.
Does the io.github.brawlaphant/vealth MCP server require authentication?
No. We connected to io.github.brawlaphant/vealth without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.brawlaphant/vealth MCP server still maintained?
io.github.brawlaphant/vealth is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.