vrsai MCP MCP server

An official MCP server providing machine-native commerce capabilities with explicit contracts and machine-readable outcomes. It exposes durable tools for decision optimization, invoice matching, API readiness assessment, and preflight checks for package installation, payouts, and SQL execution, all settled via x402.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by vrsai

MCP endpoint (Streamable HTTP)

https://api.vrsai.tech/mcp

Vendor documentation

What you can do with it

Optimize resource allocation and selection under constraints
Match supplier invoices against purchase orders and receipts
Assess OpenAPI descriptions for autonomous agent usability
Preflight check SQL execution to prevent unsafe database changes

Tools advertised by the last live check:

openapi_agent_readiness
sql_preflight
invoice_match
payout_preflight
decision_optimization
package_install_preflight

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 a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http vrsai-mcp https://api.vrsai.tech/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 vrsai-mcp --url https://api.vrsai.tech/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable vrsai-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "vrsai-mcp": {
      "url": "https://api.vrsai.tech/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "vrsai-mcp": {
      "type": "streamableHttp",
      "url": "https://api.vrsai.tech/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start vrsai-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "vrsai-mcp": {
      "type": "http",
      "url": "https://api.vrsai.tech/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 vrsai-mcp https://api.vrsai.tech/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "vrsai-mcp": {
      "url": "https://api.vrsai.tech/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": {
    "vrsai-mcp": {
      "serverUrl": "https://api.vrsai.tech/mcp"
    }
  }
}

See all 353

Do you run vrsai MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing