VIL ZERO
REMOTE · VIL-ZERO-CORE.VAL.RUN
Autonomous venture engine for AI agents: discover, build, quote, and track capabilities.
Available components
Last scanned (8 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 12 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Sept 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://vil-zero-core.val.run/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.val.run | CN=YR2,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | RSA 2048 | SHA256-RSA | 5552b818fb6c579278489178077a291e46a |
| SANs: *.val.run, val.run | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vil-zero-core.val.run. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| run. | present | 37315 | 8 | Verified |
| val.run. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=2592000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vil-zero-core.val.run/mcp | HTTP error | 404 | |
| http (plaintext) | http://vil-zero-core.val.run/mcp | HTTPS enforced | 301 | https://vil-zero-core.val.run/mcp |
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 →
agent_handshake VIL ZERO agent handshake ~23
Return machine interfaces, supported intents, commerce rules, and preferred protocol.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_capability Find capability ~34
Rank live VIL ZERO capabilities against a machine requirement.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
list_capabilities List sellable capabilities ~22
List VIL ZERO machine-created micro-services currently available to agents.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
order_status Get order status ~29
Retrieve the current state of a VIL ZERO PayPal order.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | – |
No output schema declared.
No examples provided.
quote_purchase Create purchase quote ~36
Create a machine order with exact manual PayPal payment instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| businessId | string | yes | – |
| requestedCalls | integer | – | – |
No output schema declared.
No examples provided.
report_payment Report PayPal payment ~42
Report a PayPal transaction reference. Status remains unverified because PayPal is not connected.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | – |
| transactionReference | string | yes | – |
No output schema declared.
No examples provided.
scout_snapshot Get machine-demand Scout snapshot ~21
Return current public demand signals, clusters, and autonomous Scout runs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_need Submit unmet machine need ~49
Submit a missing capability. Existing capabilities are matched first; repeated unmet demand can reach Factory.
| Name | Type | Req | Description |
|---|---|---|---|
| deadlineSeconds | integer | – | – |
| description | string | yes | – |
| maxPrice | number | – | – |
No output schema declared.
No examples provided.
system_status Get VIL ZERO system status ~25
Return machine interfaces, Scout health, commerce mode, and number of sellable capabilities.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the VIL ZERO MCP server?
VIL ZERO is a hosted endpoint at https://vil-zero-core.val.run/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 · vil-zero-core.val.run
claude mcp add --transport http run-val-vil-zero-core-vil-zero 'https://vil-zero-core.val.run/mcp'
What is the VIL ZERO MCP server?
VIL ZERO is an MCP server listed in the public MCP registry as run.val.vil-zero-core/vil-zero. Autonomous venture engine for AI agents: discover, build, quote, and track capabilities. This page covers its hosted endpoint (https://vil-zero-core.val.run/mcp).
Is the VIL ZERO MCP server safe to use?
VIL ZERO scores 25 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 VIL ZERO MCP server expose?
VIL ZERO exposes 9 tools: agent_handshake, list_capabilities, find_capability, submit_need, quote_purchase, and 4 more. Their descriptions and schemas cost roughly 281 tokens of context every time the server is loaded.
Does the VIL ZERO MCP server require authentication?
Its publisher declares no required credentials for VIL ZERO. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the VIL ZERO MCP server still maintained?
VIL ZERO is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.