Koskamo

Vivid MCP

An MCP server that allows AI agents to open Vivid Business accounts by extracting company details from chat interactions and registration documents, pre-filling the application, and initiating the verification process without requiring users to switch tabs.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vivid MCP logo, by vivid-moneyCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by vivid-money
MCP endpoint (Streamable HTTP)
https://api.prime.vivid.money/mcp
Vendor documentation

What its tools do

1 tool, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (1)

1 of 1 have a description · 0 of 1 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Open a Vivid Business account via AI chat
  • Extract company details from uploaded documents
  • Pre-fill account registration information
  • Initiate identity verification for banking

Source and maintenance

Community listingRegistry 0.1.0
Maintenance checked

Protocol and capabilities

Server
vivid-money-mcp 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
1 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "logging": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

This MCP server provides tools to create applications/legal entities/companies in Vivid money

Tools

1 advertised

build_onboarding_link
Advertised by the server during the last successful anonymous check.
Open-world

Build onboarding link for received legal entity data. This link can be used to finish the onboarding in Vivid system

build_onboarding_link input schema
{
  "type": "object",
  "required": [
    "legal_entity_data"
  ],
  "properties": {
    "legal_entity_data": {
      "type": "object",
      "properties": {
        "email": {
          "type": "string",
          "description": "Contact email address"
        },
        "phone": {
          "type": "string",
          "description": "Contact phone number"
        },
        "locale": {
          "type": "string",
          "description": "Locale code (e.g. 'de' 'en')"
        },
        "address": {
          "type": "object",
          "required": [
            "country_code",
            "city",
            "postal_code",
            "street",
            "house"
          ],
          "properties": {
            "city": {
              "type": "string"
            },
            "house": {
              "type": "string"
            },
            "state": {
              "type": "string"
            },
            "street": {
              "type": "string"
            },
            "comment": {
              "type": "string"
            },
            "postal_code": {
              "type": "string"
            },
            "country_code": {
              "type": "string",
              "description": "Alpha2 country code"
            }
          },
          "description": "Business address",
          "additionalProperties": false
        },
        "country": {
          "type": "string",
          "description": "ISO 3166-1 alpha-2 country code"
        },
        "last_name": {
          "type": "string",
          "description": "Last name of contact person"
        },
        "birth_date": {
          "type": "string",
          "description": "Birth date of contact person in RFC3339"
        },
        "brand_name": {
          "type": "string",
          "description": "Brand or trading name"
        },
        "first_name": {
          "type": "string",
          "description": "First name of contact person"
        },
        "legal_form": {
          "type": "string",
          "description": "Legal form acronym (e.g. 'Freiberufler' 'GmbH') OR code like 'DE206', requires country to be set"
        },
        "company_name": {
          "type": "string",
          "description": "Official company name"
        },
        "type_of_business": {
          "enum": [
            "LEGAL_ENTITY",
            "FREELANCE",
            "FREELANCE_NON_REG",
            "PARTNERSHIP",
            "LEGAL_ENTITY_IN_FORMATION",
            "NON_PROFIT_ORGANISATION"
          ],
          "type": [
            "null",
            "string"
          ],
          "description": "Type of business derived from legal form"
        },
        "registration_date": {
          "type": "string",
          "description": "Company registration date in RFC3339"
        },
        "monthly_credit_turnover": {
          "enum": [
            "",
            "0_5k",
            "5k_20k",
            "less20k",
            "less50k",
            "20k_50k",
            "more50k",
            "50k_165k",
            "more165k",
            "50k_200k",
            "50k_100k",
            "100k_200k",
            "200k_500k",
            "more500k",
            "500k_2m",
            "2m_5m",
            "5m_10m",
            "more2m"
          ],
          "type": [
            "null",
            "string"
          ],
          "description": "Expected monthly credit turnover range"
        },
        "business_activity_description": {
          "type": "string",
          "description": "Description of business activities"
        }
      },
      "description": "Legal entity information",
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}
build_onboarding_link output schema
{
  "type": "object",
  "required": [
    "onboarding_url"
  ],
  "properties": {
    "onboarding_url": {
      "type": "string",
      "description": "The generated onboarding URL"
    }
  },
  "additionalProperties": false
}
build_onboarding_link annotations
{
  "openWorldHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
682 ms
95th percentile latency
682 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 682 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http vivid-mcp https://api.prime.vivid.money/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add vivid-mcp --url https://api.prime.vivid.money/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable vivid-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "vivid-mcp": {
      "url": "https://api.prime.vivid.money/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "vivid-mcp": {
      "type": "streamableHttp",
      "url": "https://api.prime.vivid.money/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start vivid-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "vivid-mcp": {
      "type": "http",
      "url": "https://api.prime.vivid.money/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http vivid-mcp https://api.prime.vivid.money/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://api.prime.vivid.money/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "vivid-mcp": {
      "serverUrl": "https://api.prime.vivid.money/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Vivid MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.