A
licenseA
qualityC
maintenanceEnables AI agents to operate Xental merchant accounts via natural language, provisioning virtual accounts, monitoring transactions, and executing payouts.
Last updated
13
MIT
Vivid MCP
Server Details
Open a Vivid Business account from your AI chat via MCP.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- vivid-money/vivid-mcp
- GitHub Stars
- 2
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4/5.0
Tool DescriptionsA
Average 4/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion. The tool's purpose is clearly defined as building an onboarding link.
Naming Consistency5/5
The single tool follows a clear verb_noun pattern (build_onboarding_link), which is consistent and conventional.
Tool Count3/5
A single tool is on the lower end of the typical range. While it serves a narrow purpose, one operation feels thin for a server that might need to support the full onboarding flow.
Completeness3/5
The tool covers a specific action (building an onboarding link), but the broader onboarding workflow likely includes other operations such as validating data or retrieving link status, which are missing.
Available Tools
1 toolbuild_onboarding_linkAInspect
Build onboarding link for received legal entity data. This link can be used to finish the onboarding in Vivid system
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| legal_entity_data | Yes | Legal entity information |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| onboarding_url | Yes | The generated onboarding URL |
Tool Definition Quality
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not contradict the annotations (openWorldHint=true, destructiveHint=false) and is consistent with 'build' implying a non-destructive, possibly external action. However, it adds little behavioral insight beyond the input scope; details like link expiration, side effects, or authentication are absent. The annotations already cover the safety profile, so this is adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, 22 words, and immediately front-loads the main action ('Build onboarding link'). The second sentence adds the purpose without redundancy. Every word contributes; no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is short but sufficient given the rich schema and existing output schema. It doesn't need to explain return values because an output schema is present. The core purpose and input context are covered adequately for the tool's complexity, though a note about prerequisites (e.g., completeness of legal entity data) could enhance clarity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for all nested fields, providing detailed meaning for 'legal_entity_data'. The tool description only mentions 'legal entity data' without adding parameter-specific syntax or examples, so it adds minimal value beyond the schema. Baseline of 3 applies because the schema carries the semantic load.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Build' and the resource 'onboarding link', with a specific scope ('for received legal entity data') and outcome ('finish onboarding in Vivid system'). Although no siblings exist to differentiate from, the purpose is unambiguous and specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use the tool: when legal entity data has been received and an onboarding link needs to be generated. It doesn't explicitly list exclusions or alternatives, but with no sibling tools, this is acceptable. The context is specific enough for an agent to identify the appropriate scenario.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityAmaintenanceBridges AI assistants with the Revolut Business API to enable banking operations such as listing accounts, checking balances, viewing transactions, managing counterparties, and initiating transfers through natural language.Last updated5929MIT
- Alicense-qualityCmaintenanceBanking infrastructure for AI agents: open accounts, issue cards, send SEPA/SWIFT payments, run mass payouts, and pay invoices via natural language.Last updated2MIT
- FlicenseBqualityDmaintenanceMCP server for DACH accounting automation. Connect AI assistants to sevDesk and Lexoffice — create invoices, manage contacts, handle bookings and vouchers for German-speaking businesses.Last updated1544