Zolva
REMOTE · ZOLVAAGENT.APP
Trading agents on Robinhood Chain: every buy, sell and hold with its reason, plus market prices.
Available components
Last scanned (18 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 909 tokens (~129/item across 7 items; 7 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 0
- Tool “get_market” rewrote its description, which is the text the model reads security
- Tool “list_markets” rewrote its description, which is the text the model reads security
- Tool “verify_agent” rewrote its description, which is the text the model reads security
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +5
- HTTPS: unverified → pass ▲ security
- Schema quality: 661 → 835 ▼ functional
- Schema quality: 661 → 728 ▼ functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “get_consensus” functional
- New tool “verify_agent” functional
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_market” rewrote its description, which is the text the model reads security
- Tool “list_markets” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://zolvaagent.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zolvaagent.app | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 322fa3e9985dd6ef0ebdea66f9e183de |
| SANs: zolvaagent.app, *.zolvaagent.app | ||||||
| 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 insecure
Validation of zolvaagent.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| zolvaagent.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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://zolvaagent.app/mcp | Verified | 200 | |
| http (plaintext) | http://zolvaagent.app/mcp | HTTPS enforced | 301 | https://zolvaagent.app/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 →
get_agent Get agent ~55
One published agent: settings, hourly value vs holding for 7 days, open positions, latest trades, and every decision of the last 24 hours with its reason.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The agent id from list_agents |
No output schema declared.
No examples provided.
get_consensus Agent positions by market ~107
Statistics, per market: how many Tested published paper agents (rules that passed Zolva's 6 year backtest) are long, short or in cash, and what they did in the newest hour. Returns the agent count each market is based on and says when it is too few. Paper trading, not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | – | Only this market, such as BTC or SOL-PERP |
| venue | string | – | Only spot or only perps markets |
No output schema declared.
No examples provided.
get_market Get market ~90
One market: up to 30 days of hourly closes, the published agents trading it, and its Longbow lending market if any (longbow: { lltvPct, borrowAprPct, availableUsdg, feedFrozen, url } or null; rates change, not investment advice).
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Market symbol, such as NVDA, SPY, ETH or BTC-PERP |
No output schema declared.
No examples provided.
list_agents List agents ~149
Published Zolva agents with their return, return vs simply holding the same markets, worst drop and trade count. Paper trading only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many agents to return, default 20 |
| market | string | – | Only agents watching this market symbol, such as NVDA, ETH or BTC-PERP |
| sortBy | string | – | return (default, highest first), vs_holding (most ahead of holding first) or drawdown (smallest worst drop first) |
| strategy | string | – | Only agents using this strategy |
| venue | string | – | Only spot agents (tokens, long only) or only perps agents (Lighter, long or short) |
No output schema declared.
No examples provided.
list_markets List markets ~156
Every market Zolva prices on Robinhood Chain: latest hourly price, 1 hour to 30 day changes, a 7 day sparkline and how many agents trade it. Perps (venue perps, symbols like BTC-PERP) also carry their funding rate. Spot tokens that Longbow (Morpho Blue lending) accepts as collateral for USDG carry longbow: { lltvPct, borrowAprPct, availableUsdg, feedFrozen, url }, otherwise null (borrowAprPct is null while the price feed is paused; rates change, not investment advice).
| Name | Type | Req | Description |
|---|---|---|---|
| assetClass | string | – | Only stocks or only crypto |
| venue | string | – | Only spot tokens or only Lighter perps |
No output schema declared.
No examples provided.
recent_activity Recent trades ~80
Trades by published agents over the last 48 hours, newest first, each with the agent's own reason.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | Only trades by this agent |
| limit | integer | – | How many trades to return, default 50 |
| market | string | – | Only trades in this market, such as NVDA or BTC-PERP |
No output schema declared.
No examples provided.
verify_agent Verify agent ~93
Replays one published agent with Zolva's open source engine over every hour it ran, on the closes it saw and the same funding, and compares every trade and its value with the record. Returns match or the first hour that differs; hours whose look-back predates stored prices (2026-11-14) are reported apart as unverifiable.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The agent id from list_agents |
No output schema declared.
No examples provided.
How do I install the Zolva MCP server?
Zolva is a hosted endpoint at https://zolvaagent.app/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 · zolvaagent.app
claude mcp add --transport http app-zolvaagent-zolva 'https://zolvaagent.app/mcp'
What is the Zolva MCP server?
Zolva is an MCP server listed in the public MCP registry as app.zolvaagent/zolva. Trading agents on Robinhood Chain: every buy, sell and hold with its reason, plus market prices. This page covers its hosted endpoint (https://zolvaagent.app/mcp).
Is the Zolva MCP server safe to use?
Zolva scores 75 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 Zolva MCP server expose?
Zolva exposes 7 tools: list_agents, get_agent, verify_agent, list_markets, get_market, and 2 more. Their descriptions and schemas cost roughly 730 tokens of context every time the server is loaded.
Does the Zolva MCP server require authentication?
No. We connected to Zolva without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zolva MCP server still maintained?
Zolva is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Zolva MCP server?
VerifyMCP ran 13 checks on Zolva, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.