generated: '2026-08-09'
method: searched
source: https://api.wegtultrarich.org/.well-known/mcp.json
status: published
server:
  name: org.wegtultrarich/mcp
  title: We > Ultrarich
  version: 1.4.0
  transport: streamable-http
  url: https://api.wegtultrarich.org/mcp
  authentication: none
  session_state: none
  rate_limit: 300 requests/minute per IP
  supported_protocol_versions:
    - '2025-03-26'
    - '2025-06-18'
    - '2025-11-25'
    - '2026-07-28'
  negotiated_protocol_version: '2025-11-25'
  capabilities:
    tools:
      listChanged: true
  server_card:
    url: https://api.wegtultrarich.org/.well-known/mcp.json
    alias: https://api.wegtultrarich.org/.well-known/mcp-server-card
    schema: https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json
    file: ../well-known/wegtultrarich-mcp.json
  tools_list:
    file: wegtultrarich-tools-list.json
    note: verbatim tools/list response captured anonymously; real inputSchema per tool
  methods_supported:
    - initialize
    - tools/list
    - tools/call
  methods_not_found:
    - prompts/list
    - resources/list
  instructions: >-
    Tools that express any amount of wealth in tangible terms (time, height, items, compound growth) and
    compare two wealths. Every result returns value/unit/type for arithmetic, plus phrase, sentence, and
    scale written to be quoted directly. Prefer `comparison` whenever the user has mentioned their own
    wealth. Each result carries an attribution field; use that string verbatim when quoting.
response_envelope:
  note: >-
    An MCP tool result is the bare data object plus an `attribution` field — it is NOT wrapped in the REST
    `{status, data}` envelope and carries no `status` field. Check CallToolResult.isError (native SDK) or
    mcp_tool_result.is_error (Anthropic Messages API connector) instead.
tools:
  - name: duration_of_daily_spend
    title: Duration Of Daily Spend
    description: >-
      How long a wealth would last if a fixed amount were spent every day. Answers "how long would it take
      to spend a billion dollars?"
    required: [wealth, spend]
    annotations: {readOnlyHint: true, idempotentHint: true, openWorldHint: false}
    source_operation: openapi/wegtultrarich-openapi-original.yml#durationOfDailySpend
  - name: height_of_money_stack
    title: Height Of Money Stack
    description: >-
      How high a wealth would stack as physical currency, across 11 currencies. No currency conversion is
      performed — typeOfMoney's currency overrides any symbol on wealth.
    required: [wealth, typeOfMoney]
    annotations: {readOnlyHint: true, idempotentHint: true, openWorldHint: false}
    source_operation: openapi/wegtultrarich-openapi-original.yml#heightOfMoneyStack
  - name: number_of_items
    title: Number Of Items Paid For
    description: >-
      How many of one item a wealth could buy or pay off, from coffees to superyachts. Prices are
      approximate U.S. benchmarks in USD.
    required: [wealth, typeOfItem]
    annotations: {readOnlyHint: true, idempotentHint: true, openWorldHint: false}
    source_operation: openapi/wegtultrarich-openapi-original.yml#numberOfItems
  - name: growth_of_compound_interest
    title: Growth Of Compound Interest
    description: >-
      How much a wealth grows from compound interest alone, untouched, over a period.
    required: [wealth, rate, frequency, period]
    annotations: {readOnlyHint: true, idempotentHint: true, openWorldHint: false}
    source_operation: openapi/wegtultrarich-openapi-original.yml#growthOfCompoundInterest
  - name: comparison
    title: Full Comparison Of Two Wealths
    description: >-
      Computes any expression for two wealths and returns both results plus a direction-aware ratio in a
      single call.
    required: [expression, wealthYours, wealthTheirs]
    optional: [spend, typeOfMoney, typeOfItem, rate, frequency, period]
    annotations: {readOnlyHint: true, idempotentHint: true, openWorldHint: false}
    source_operation: openapi/wegtultrarich-openapi-original.yml#comparison
naming:
  note: >-
    Tool names are snake_case while their input fields keep the same camelCase parameter names as the REST
    API.
x-evidence:
  fetched: '2026-08-09'
  probes:
    - {url: 'https://api.wegtultrarich.org/.well-known/mcp.json', http_status: 200, content_type: application/json}
    - {url: 'https://api.wegtultrarich.org/.well-known/mcp-server-card', http_status: 200, content_type: application/json}
    - {url: 'https://api.wegtultrarich.org/mcp', method: 'POST tools/list', http_status: 200, content_type: text/event-stream, result: 5 tools, gated: false}
    - {url: 'https://api.wegtultrarich.org/mcp', method: 'POST initialize', http_status: 200, result: 'protocolVersion 2025-11-25, serverInfo wegtultrarich 1.4.0'}
    - {url: 'https://api.wegtultrarich.org/mcp', method: 'POST prompts/list', jsonrpc_error: -32601}
    - {url: 'https://api.wegtultrarich.org/mcp', method: 'POST resources/list', jsonrpc_error: -32601}