Skip to content
vrsai logo

vrsai MCP server

Which MCP servers are vrsai's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to vrsai

Whose server it is
  • Registry nametech.vrsai/mcpverified in the MCP registry

The registry name sits under vrsai.tech. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools6
  • Server calls itselfvrsai
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 610 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check npm or PyPI package versions before installation; match supplier invoices against purchase orders before payment; preflight SQL statements before AI agents run them.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "check npm or PyPI package versions before installation", the likely first call is package_install_preflight.
  • For "match supplier invoices against purchase orders before payment", the likely first call is invoice_match.
  • For "preflight SQL statements before AI agents run them", the likely first call is sql_preflight.
  • Parameters are untyped or undescribed in 3 of 6 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer708 ms
  • Space in an agent's context≈ 9,305 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsA · 92 of 100
  • Typed results6 of 6 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 3 of 6

What an agent can do with it

  • can do · check npm or PyPI package versions before installation
  • can do · match supplier invoices against purchase orders before payment
  • can do · preflight SQL statements before AI agents run them

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-26
  • openapi_agent_readiness

    Call before integrating an OpenAPI-described API with autonomous agents to determine whether the contract is machine-actionable. Deterministically analyzes a self-contained OpenAPI 3.0, 3.1, or 3.2 description and returns a readiness…

  • sql_preflight

    Call this immediately before an autonomous agent, coding assistant, or automated pipeline executes PostgreSQL write, DDL, or administrative SQL against a production-capable connection. It parses the complete statement set with a real…

  • invoice_match

    Call after invoice extraction and immediately before an accounts-payable or procurement agent approves a purchase-order-backed supplier invoice. Invoice Match performs deterministic three-way matching across invoice lines, one or more…

  • payout_preflight

    Call immediately before an AI agent, accounts-payable system, treasury workflow, marketplace, or autonomous payment service authorizes or submits an outbound payout. Payout Preflight deterministically compares the candidate payout with…

  • decision_optimization

    Call immediately before an autonomous system must choose among multiple feasible actions under limited resources, costs, capacities, eligibility rules, and an economic objective. Decision Optimization compiles a typed economic problem…

  • package_install_preflight

    Call immediately before installing or adding an exact third-party npm or PyPI package version. Checks current registry, known vulnerability/malicious-package, publisher withdrawal/deprecation, and verified provenance evidence and returns…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "vrsai": {
      "type": "http",
      "url": "https://api.vrsai.tech/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http vrsai https://api.vrsai.tech/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.vrsai.tech/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.