← Registry

API Tools

wealthtech.dev

Provides a searchable catalog and comparison of wealth technology products' API access details and vendor-published MCP servers or AI connectors.

1 endpoint8 known toolsFirst detected October 23, 2026Last detected October 23, 2026

ENDPOINT 1

https://mcp.wealthtech.dev/mcp

No auth detected

MCP server metadata

Name
wealthtech.dev
Version
0.2.0
Capabilities
tools.listChanged
Server instructions

Read-only data from wealthtech.dev: how to connect to wealth technology products (advisor CRMs, planning, portfolio reporting, custodians, aggregation, compliance, market data), the MCP servers and AI connectors those vendors publish, and a dictionary of the SEC's monthly investment adviser file mapped to Form ADV. Every fact was read on a public page and carries a state (verified, third, unknown, unreadable), the date it was checked and a verbatim quote. Cite the sources[] in each result. "unknown" means the public pages read did not say; it is not a "no". Start with search_products or list_mcp_servers, then get_product or get_mcp_server for the quoted evidence. Licence: CC BY 4.0, attribute "wealthtech.dev".

Known tools 8

search_products

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.

Inferred read-only
get_product

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.

Inferred read-only
compare_access

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.

Inferred read-only
list_mcp_servers

MCP servers and AI connectors published by wealth technology vendors: endpoint, status (live or announced), kind, tool count and the products they connect to.

Inferred read-only
get_mcp_server

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[].

Potential side effects
get_changes

Dated changelog entries: new products, changed access facts, new MCP servers.

Inferred read-only
get_form_adv_column

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.

Inferred read-only
list_categories

The product categories wealthtech.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.wealthtech-dev]
url = "https://mcp.wealthtech.dev/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "wealthtech-dev": {
      "type": "http",
      "url": "https://mcp.wealthtech.dev/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: wealthtech-dev
Remote MCP URL: https://mcp.wealthtech.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "wealthtech-dev": {
      "url": "https://mcp.wealthtech.dev/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "wealthtech-dev": {
      "type": "http",
      "url": "https://mcp.wealthtech.dev/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "wealthtech-dev",
  "transport": "streamable-http",
  "url": "https://mcp.wealthtech.dev/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.