vrsai
REMOTE · API.VRSAI.TECH · SCANNED SEP 20
Machine-native capabilities with explicit contracts and machine-readable commerce.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (openapi_agent_readiness). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1340 tokens (~223/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 24% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the vrsai MCP server?
vrsai is a hosted endpoint at https://api.vrsai.tech/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.vrsai.tech
claude mcp add --transport http tech-vrsai-mcp 'https://api.vrsai.tech/mcp'
{
"mcpServers": {
"tech-vrsai-mcp": {
"url": "https://api.vrsai.tech/mcp"
}
}
} {
"servers": {
"tech-vrsai-mcp": {
"type": "http",
"url": "https://api.vrsai.tech/mcp"
}
}
} [mcp_servers.tech-vrsai-mcp] url = "https://api.vrsai.tech/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tech-vrsai-mcp": {
"type": "remote",
"url": "https://api.vrsai.tech/mcp",
"enabled": true
}
}
} openclaw mcp add tech-vrsai-mcp --url 'https://api.vrsai.tech/mcp' --transport streamable-http
mcp_servers:
tech-vrsai-mcp:
url: "https://api.vrsai.tech/mcp" {
"McpServers": {
"tech-vrsai-mcp": {
"Transport": "http",
"Url": "https://api.vrsai.tech/mcp"
}
}
} assistant mcp add tech-vrsai-mcp -t streamable-http -u 'https://api.vrsai.tech/mcp'
{
"mcpServers": {
"tech-vrsai-mcp": {
"type": "http",
"url": "https://api.vrsai.tech/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.vrsai.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vrsai.tech | CN=WE1,O=Google Trust Services,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 8cc74c7734142879137fb0d23f9271dd |
| SANs: vrsai.tech, api.vrsai.tech, *.api.vrsai.tech | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.vrsai.tech. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| vrsai.tech. | present | 2371 | 13 | Verified |
| api.vrsai.tech. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.vrsai.tech/mcp | Verified | 200 | |
| http (plaintext) | http://api.vrsai.tech/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
decision_optimization Decision Optimization ~196
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | – | – | – |
| diagnostics | object | yes | – |
| economics | object | yes | – |
| evidence | object | yes | – |
| machine_action | – | yes | – |
| problem_type | – | yes | – |
| quality | object | yes | – |
| status | – | yes | – |
No examples provided.
invoice_match Invoice Match ~252
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.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | object | yes | – |
| invoice | object | yes | – |
| match_mode | string | yes | – |
| policy | object | – | – |
| purchase_orders | array | yes | – |
| receipts | array | yes | – |
| recent_invoices | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| coverage | object | yes | – |
| decision | – | yes | – |
| input_fingerprint | string | yes | SHA-256 fingerprint ("v1:<hex>") of the exact submitted evaluation input tuple. Identical input and policy always produce the identical fingerprint. See fingerprint.ts. |
| invoice | object | yes | – |
| line_results | array | yes | – |
| machine_action | – | yes | – |
| reason_codes | array | yes | – |
| ruleset_version | string | yes | Version of the reason-code catalog and policy defaults that produced this result, independent of the capability's own contract version. See RULESET_VERSION in rules.ts. |
| totals | object | yes | – |
No examples provided.
openapi_agent_readiness OpenAPI Agent Readiness ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | yes | The OpenAPI description as a parsed JSON object (not a YAML/JSON string). Must include a top-level 'openapi' version field of family 3.0, 3.1, or 3.2. Only inline schemas and local references ('#/...… |
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | array | yes | – |
| findings | array | yes | – |
| openapi_version | string | yes | The detected 'openapi' version string, or 'unknown' if it could not be determined. |
| ruleset_version | string | yes | Version of the finding codes, dimension weights, and scoring thresholds that produced this result — independent of the capability's own contract version. See RULESET_VERSION in rules.ts. |
| score | integer | yes | – |
| summary | object | yes | – |
| verdict | – | yes | ready: score >= 85 and no blocking finding. needs_changes: score >= 60 and no blocking finding. not_ready: score < 60, or at least one blocking finding regardless of score. |
No examples provided.
package_install_preflight Package Install Preflight ~229
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_source_repository | string | – | Optional HTTPS source repository identity to compare only with cryptographically verified deps.dev provenance. This URL is never fetched. |
| purl | string | yes | ECMA-427 Package URL for one exact published npm or PyPI version. Ranges, dist-tags, qualifiers, and subpaths are not supported. |
| Name | Type | Req | Description |
|---|---|---|---|
| decision | – | yes | – |
| evidence | array | yes | – |
| input_fingerprint | string | yes | – |
| observations | object | yes | – |
| observed_at | string | yes | – |
| package | object | yes | – |
| policy_version | string | yes | – |
| reason_codes | array | yes | – |
| unknowns | array | yes | – |
No examples provided.
payout_preflight Payout Preflight ~215
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.
| Name | Type | Req | Description |
|---|---|---|---|
| history | object | – | – |
| payout | object | yes | – |
| policy | object | – | – |
| trusted_baseline | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | object | yes | – |
| checks | array | yes | – |
| coverage | object | yes | – |
| decision | – | yes | – |
| machine_action | – | yes | – |
| reason_codes | array | yes | – |
| ruleset_version | string | yes | – |
No examples provided.
sql_preflight SQL Preflight ~255
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | – |
| policy | object | – | – |
| sql | string | yes | A complete PostgreSQL statement or semicolon-separated statement list. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| coverage | object | yes | – |
| decision | – | yes | – |
| input_fingerprint | string | yes | SHA-256 fingerprint ("v1:<hex>") of the exact submitted {sql, context, policy} tuple. Identical input and policy always produce the identical fingerprint, independent of commercial/payment mode. See… |
| machine_action | – | yes | – |
| reason_codes | array | yes | – |
| ruleset_version | string | yes | Version of the reason-code catalog and policy defaults that produced this result, independent of the capability's own contract version. See RULESET_VERSION in rules.ts. |
| statement_count | integer | yes | – |
| statements | array | yes | – |
No examples provided.
What is the vrsai MCP server?
vrsai is an MCP server listed in the public MCP registry as tech.vrsai/mcp. Machine-native capabilities with explicit contracts and machine-readable commerce. This page covers its hosted endpoint (https://api.vrsai.tech/mcp).
Is the vrsai MCP server safe to use?
vrsai scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the vrsai MCP server expose?
vrsai exposes 6 tools: openapi_agent_readiness, sql_preflight, invoice_match, payout_preflight, decision_optimization, package_install_preflight. Their descriptions and schemas cost roughly 1,340 tokens of context every time the server is loaded.
Does the vrsai MCP server require authentication?
No. We connected to vrsai without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the vrsai MCP server still maintained?
vrsai is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.