wealthtech.dev
REMOTE · MCP.WEALTHTECH.DEV
Read-only, sourced access facts for wealth tech products, vendor MCP servers and Form ADV columns.
Available components
Last scanned (7 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 867 tokens (~108/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ 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 5 Nov 2026 · Probed https://mcp.wealthtech.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wealthtech.dev | CN=YE2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5799724b5437c33ccff5ecd58067a99de71 |
| SANs: *.wealthtech.dev, wealthtech.dev | ||||||
| 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 mcp.wealthtech.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| wealthtech.dev. | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.wealthtech.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.wealthtech.dev/mcp | Inconclusive | 405 |
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 →
compare_access Compare API access across products ~69
Side by side: access level, auth, sandbox, docs, OpenAPI, webhooks, SDKs, rate limits, how to get access and partner program for 2 to 10 products, with the state and checked date of each value.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Product ids to compare. |
No output schema declared.
No examples provided.
get_changes What changed on wealthtech.dev ~52
Dated changelog entries: new products, changed access facts, new MCP servers. Use since to get only recent entries.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | ISO date (YYYY-MM-DD); entries on or after it. |
No output schema declared.
No examples provided.
get_form_adv_column Explain a column in the SEC investment adviser file ~130
What one column of the SEC's monthly investment adviser (Form ADV) CSV means: the Form ADV Part 1A item, the question as worded on the form, its type, observed values and gotchas. Matches the exact column name (e.g. "5E(1)" or "Organization CRD#") or a normalized name (crd_number); otherwise returns up to 10 columns whose name contains the text.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Column name, normalized name, Form ADV item (e.g. 5.F(2)(c)) or part of one. |
No output schema declared.
No examples provided.
get_mcp_server Get one MCP server or AI connector ~79
Full record for one vendor MCP server or AI connector: endpoint, transport, auth, scope, how it is enabled, price, listings and its tools (read or write), with quoted evidence in sources[].
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | MCP record id, e.g. wealthbox-mcp. Use list_mcp_servers to find ids. |
No output schema declared.
No examples provided.
get_product Get one product's developer access record ~106
Everything on record about connecting to one product: access level, auth methods, sandbox, docs, OpenAPI, webhooks, SDKs, rate limits, partner program, how to get access, what the docs don't say, and linked MCP servers. Each fact has its state, checked date and a verbatim quote in sources[].
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Product id, e.g. wealthbox, orion, schwab-advisor-services. Use search_products to find ids. |
No output schema declared.
No examples provided.
list_categories List product categories ~23
The product categories wealthtech.dev covers, with how many products each holds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_mcp_servers List wealth-tech MCP servers and AI connectors ~63
MCP servers and AI connectors published by wealth technology vendors: endpoint, status (live or announced), kind, tool count and the products they connect to.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | – | Only servers that connect to this product id. |
| status | string | – | – |
No output schema declared.
No examples provided.
search_products Search wealth technology products ~183
Find products by name, vendor or id, optionally filtered by category, API access level or whether the vendor has an MCP server or AI connector. Returns one row per product; call get_product for the quoted evidence behind each value.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | open = docs and keys self-serve; open-docs-gated-keys = docs public, keys by approval; partner-gated = partnership needed; unknown = no public API found; unreadable = the pages blocked automated read… |
| category | string | – | Category id, e.g. crm, planning, portfolio-reporting, custodian, aggregation. See list_categories. |
| has_mcp | boolean | – | true = only products with an MCP server or AI connector on record. |
| query | string | – | Words to match against product name, vendor, id and category. Omit to list all. |
No output schema declared.
No examples provided.
How do I install the wealthtech.dev MCP server?
wealthtech.dev is a hosted endpoint at https://mcp.wealthtech.dev/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 · mcp.wealthtech.dev
claude mcp add --transport http dev-wealthtech-mcp 'https://mcp.wealthtech.dev/mcp'
What is the wealthtech.dev MCP server?
wealthtech.dev is an MCP server listed in the public MCP registry as dev.wealthtech/mcp. Read-only, sourced access facts for wealth tech products, vendor MCP servers and Form ADV columns. This page covers its hosted endpoint (https://mcp.wealthtech.dev/mcp).
Is the wealthtech.dev MCP server safe to use?
wealthtech.dev scores 73 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 wealthtech.dev MCP server expose?
wealthtech.dev exposes 8 tools: search_products, get_product, compare_access, list_mcp_servers, get_mcp_server, and 3 more. Their descriptions and schemas cost roughly 705 tokens of context every time the server is loaded.
Does the wealthtech.dev MCP server require authentication?
No. We connected to wealthtech.dev without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the wealthtech.dev MCP server still maintained?
wealthtech.dev is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.