vrsai

Name: vrsai
Author: tech.vrsai

MCP serverMCP

Machine-native capabilities with explicit contracts and machine-readable commerce.

by tech.vrsaihomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"vrsai","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability107/107 checks ok

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	58 ms	server vrsai 1.0.0 · protocol 2025-06-18 · 6 tools
8 h ago	mcp initialize	ok	200	52 ms	server vrsai 1.0.0 · protocol 2025-06-18 · 6 tools
14 h ago	mcp initialize	ok	200	51 ms	server vrsai 1.0.0 · protocol 2025-06-18 · 6 tools
21 h ago	mcp initialize	ok	200	44 ms	server vrsai 1.0.0 · protocol 2025-06-18 · 6 tools
28 h ago	mcp initialize	ok	200	54 ms	server vrsai 1.0.0 · protocol 2025-06-18 · 6 tools
35 h ago	mcp initialize	ok	200	69 ms	server vrsai 1.0.0 · protocol 2025-06-18 · 6 tools
2 d ago	mcp initialize	ok	200	126 ms	server vrsai 1.0.0 · protocol 2025-06-18 · 6 tools
2 d ago	mcp initialize	ok	200	35 ms	server vrsai 1.0.0 · protocol 2025-06-18 · 6 tools
2 d ago	mcp initialize	ok	200	56 ms	server vrsai 1.0.0 · protocol 2025-06-18 · 6 tools
3 d ago	mcp initialize	ok	200	213 ms	server vrsai 1.0.0 · protocol 2025-06-18 · 6 tools

Tools observed via MCP handshake

openapi_agent_readiness — Call before integrating an OpenAPI-described API with autonomous agents to determine whether the contract is machine-actionable. Deterministically analyzes a se
sql_preflight — Call this immediately before an autonomous agent, coding assistant, or automated pipeline executes PostgreSQL write, DDL, or administrative SQL against a produc
invoice_match — Call after invoice extraction and immediately before an accounts-payable or procurement agent approves a purchase-order-backed supplier invoice. Invoice Match p
payout_preflight — Call immediately before an AI agent, accounts-payable system, treasury workflow, marketplace, or autonomous payment service authorizes or submits an outbound pa
decision_optimization — Call immediately before an autonomous system must choose among multiple feasible actions under limited resources, costs, capacities, eligibility rules, and an e
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, p

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrytech.vrsai/mcp

first seen 1 mo ago · fetched 30 h agoopen ↗

Field history (6 recent events)

1 mo ago · declared · summary → "Machine-native capabilities with explicit contracts and machine-readable commerce."
1 mo ago · declared · description → "Machine-native capabilities with explicit contracts and machine-readable commerce."
1 mo ago · declared · publisherName → "tech.vrsai"
1 mo ago · declared · homepageUrl → "https://vrsai.tech"
1 mo ago · declared · version → "1.0.0"
1 mo ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from