Search / tech.vrsai/mcp
protogridR0· no sign-inMachine-native capabilities with explicit contracts and machine-readable commerce.
v1.0.0 · active · website · descriptor JSON · versions
{
"mcpServers": {
"vrsai": {
"type": "http",
"url": "https://api.vrsai.tech/mcp"
}
}
}claude mcp add --transport http vrsai https://api.vrsai.tech/mcp[mcp_servers.vrsai]
url = "https://api.vrsai.tech/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vrsai": {
"type": "remote",
"url": "https://api.vrsai.tech/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"vrsai": {
"type": "http",
"url": "https://api.vrsai.tech/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=vrsai&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpLnZyc2FpLnRlY2gvbWNwIn0%3D"
}{
"servers": {
"vrsai": {
"type": "http",
"url": "https://api.vrsai.tech/mcp"
}
}
}{
"mcpServers": {
"vrsai": {
"httpUrl": "https://api.vrsai.tech/mcp"
}
}
}extensions:
"vrsai":
enabled: true
name: "vrsai"
type: streamable_http
uri: "https://api.vrsai.tech/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltool list is cacheable (ttlMs 300000)auth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length2 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations6 of 6 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 9,371 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +website +reachable +uptime-95% ~updated-56d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://api.vrsai.tech/mcp streamable-http | none | yes | 95% | 630 ms | 2026-07-28 | 2026-10-19 |
decision_optimizationdestructive | 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 — supplier/inventory allocation across sources and demands, task-to-resource assignment, budget-constrained option selection, or production/resource mix — into a bounded MILP model, solves it with a fixed deterministic solver profile, and independently re-verifies the candidate decision against the original problem before returning it. Returns OPTIMAL, FEASIBLE, INFEASIBLE, UNBOUNDED, or NO_SOLUTION with machine-readable evidence: verified feasibility, solver optimality/gap, binding constraints, and stable fingerprints. It does not perform vehicle routing, scheduling, calendar planning, 3D/carton packing, arbitrary LP/MIP solving, natural-language optimization modeling, forecasting, or external data retrieval. Paid invocation: 30000 micro-USD per successful execution. |
invoice_matchdestructive | 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 purchase orders, cumulative goods-receipt evidence, prior invoicing, price tolerances, quantities, units, and exact invoice arithmetic. Cumulative invoicing (prior plus current) is always compared against cumulative receipts and against the ordered quantity, so repeated partial invoices against partial deliveries cannot silently overbill. It returns PROCEED, REVIEW, or BLOCK with line-level discrepancy codes and evidence, and always discloses which checks were and were not performed. Use it for invoice matching, PO matching, 3-way matching, goods-receipt matching, overbilling prevention, and autonomous AP approval controls. It does not OCR documents, infer product matches, retrieve ERP data, determine tax, or execute payment. Paid invocation: 50000 micro-USD per successful execution. |
openapi_agent_readinessdestructive | 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 score, verdict, and actionable findings covering operation semantics, request and response contracts, authentication clarity, reference integrity, and machine usability. It does not apply when generating a new OpenAPI description from source code. Paid invocation: 30000 micro-USD per successful execution. |
package_install_preflightdestructive | 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 ALLOW, REVIEW, BLOCK, or UNKNOWN with machine-readable reasons. It accepts only an ECMA-427 Package URL with one exact published version; ranges, dist-tags, Git dependencies, archives, local packages, container images, other ecosystems, dependency graphs, repositories, SBOMs, and source-code or malware analysis are outside this version. It does not install, download, extract, clone, execute, or recommend a package version, and ALLOW never claims that a package is safe. Paid invocation: 10000 micro-USD per successful execution. |
payout_preflightdestructive | 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 caller-supplied trusted payment instructions, exact amount/currency policy, and supplied payout history; validates supported IBAN, US routing, and EVM destination structure; and detects destination changes, duplicate payouts, reused references, and first-seen destinations when history is complete. It returns PROCEED, REVIEW, or BLOCK with machine-readable evidence. Use it for payout validation, payment pre-validation, beneficiary-bank-detail change controls, duplicate-payment prevention, treasury controls, and agent payment guardrails. It does not verify bank-account ownership, perform Verification of Payee, AML/sanctions screening, submit payments, or guarantee settlement. Paid invocation: 50000 micro-USD per successful execution. |
sql_preflightdestructive | 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 PostgreSQL AST parser and prevents the costly mistake of an agent silently deleting, truncating, or dropping data it should not have touched. It detects unbounded DELETE and UPDATE (no WHERE clause), TRUNCATE, destructive DROP and CASCADE, mutation of caller-declared protected relations, and availability-sensitive DDL such as a non-concurrent CREATE INDEX or hazardous ALTER TABLE change. It returns a deterministic PROCEED, REVIEW, or BLOCK decision with stable reason codes, a per-statement inventory, and an explicit coverage report of exactly what was and was not assessed — parse failure and unparseable or unmodeled syntax always fail closed to REVIEW, never PROCEED. PostgreSQL is the only supported dialect in this version. It does not apply when executing SQL or connecting to a database. Paid invocation: 50000 micro-USD per successful execution. |
Schemas: list_tools.
{
"name": "tech.vrsai/mcp",
"icons": [
{
"src": "https://api.vrsai.tech/brand/mark-512.png",
"sizes": [
"512x512"
],
"mimeType": "image/png"
}
],
"title": "vrsai",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://api.vrsai.tech/mcp",
"type": "streamable-http"
}
],
"version": "1.0.0",
"websiteUrl": "https://vrsai.tech",
"description": "Machine-native capabilities with explicit contracts and machine-readable commerce."
}