# BlockVectra Docs: Robinhood Chain & EVM (remote · docs.blockvectra.com)

Search and read Robinhood Chain and EVM RPC/API docs. No account, API key or local install.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `docs.blockvectra.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-blockvectra-docs/mcp-docs.md), [page](https://verifymcp.io/servers/com-blockvectra-docs/mcp-docs)

## Channel facts

- Endpoint: `https://docs.blockvectra.com/mcp/docs`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 408 tokens (~204/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (50% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the BlockVectra Docs: Robinhood Chain & EVM MCP server?

BlockVectra Docs: Robinhood Chain & EVM is a hosted endpoint at https://docs.blockvectra.com/mcp/docs, 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.

### Claude

```bash
claude mcp add --transport http com-blockvectra-docs 'https://docs.blockvectra.com/mcp/docs'
```

### Cursor

```json
{
  "mcpServers": {
    "com-blockvectra-docs": {
      "url": "https://docs.blockvectra.com/mcp/docs"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-blockvectra-docs": {
      "type": "http",
      "url": "https://docs.blockvectra.com/mcp/docs"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-blockvectra-docs]
url = "https://docs.blockvectra.com/mcp/docs"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-blockvectra-docs": {
      "type": "remote",
      "url": "https://docs.blockvectra.com/mcp/docs",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-blockvectra-docs --url 'https://docs.blockvectra.com/mcp/docs' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-blockvectra-docs:
    url: "https://docs.blockvectra.com/mcp/docs"
```

### Netclaw

```json
{
  "McpServers": {
    "com-blockvectra-docs": {
      "Transport": "http",
      "Url": "https://docs.blockvectra.com/mcp/docs"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-blockvectra-docs -t streamable-http -u 'https://docs.blockvectra.com/mcp/docs'
```

### Other

```json
{
  "mcpServers": {
    "com-blockvectra-docs": {
      "type": "http",
      "url": "https://docs.blockvectra.com/mcp/docs"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 79, +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.

### 2026-11-14 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 75, −4)

- [security regression] HTTPS: pass → unverified

### 2026-11-07 (score 79, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (2)

### `read_doc` (~142 tokens)

Read Documentation Page

Read the raw Markdown content of a documentation page from /md/{lang}/{path}.md. Path must be an internal relative path (e.g. 'quickstart', 'guides/ai-agents', 'api/json-rpc', 'chains').

Input parameters:

- `lang` (string): Published documentation language (case-insensitive, e.g. zh-hant or zh-Hant). Omit for English; unavailable languages return an error.
- `path` (string, required): Internal relative documentation path (e.g. 'quickstart', 'guides/ai-agents', 'api/json-rpc'). Do not include protocol, hostname, query string, fragment, or '..'.

### `search_docs` (~171 tokens)

Search Documentation

Find documentation by topic or task keywords in page titles, navigation titles, relative paths, and summaries. Read a result with read_doc using its path and the same lang; use read_doc directly for a known path. Omit lang for English; limit is 1-20 (default 5). If no results match, try broader keywords or read_doc with path 'quickstart'. Available without an API key.

Input parameters:

- `lang` (string): Published documentation language (case-insensitive, e.g. zh-hant or zh-Hant). Omit for English; unavailable languages return an error.
- `limit` (number): Maximum number of search results to return (1-20, default 5).
- `query` (string, required): Keywords to search for in documentation titles, navigation titles, paths, and summaries.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-blockvectra-docs/mcp-docs#diagnostics

## Score history

- 2026-11-21: 81
- 2026-11-20: 81
- 2026-11-19: 80
- 2026-11-18: 80
- 2026-11-17: 79
- 2026-11-16: 79
- 2026-11-15: 78
- 2026-11-14: 78
- 2026-11-13: 77
- 2026-11-12: 77
- 2026-11-11: 76
- 2026-11-10: 76
- 2026-11-09: 75
- 2026-11-08: 75
- 2026-11-07: 79
- 2026-11-06: 78

## Common questions

### What is the BlockVectra Docs: Robinhood Chain & EVM MCP server?

BlockVectra Docs: Robinhood Chain & EVM is an MCP server listed in the public MCP registry as com.blockvectra/docs. Search and read Robinhood Chain and EVM RPC/API docs. No account, API key or local install. This page covers its hosted endpoint (https://docs.blockvectra.com/mcp/docs).

### Is the BlockVectra Docs: Robinhood Chain & EVM MCP server safe to use?

BlockVectra Docs: Robinhood Chain & EVM scores 81 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 BlockVectra Docs: Robinhood Chain & EVM MCP server expose?

BlockVectra Docs: Robinhood Chain & EVM exposes 2 tools: read_doc, search_docs. Their descriptions and schemas cost roughly 313 tokens of context every time the server is loaded.

### Does the BlockVectra Docs: Robinhood Chain & EVM MCP server require authentication?

No. We connected to BlockVectra Docs: Robinhood Chain & EVM without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BlockVectra Docs: Robinhood Chain & EVM MCP server still maintained?

BlockVectra Docs: Robinhood Chain & EVM 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 BlockVectra Docs: Robinhood Chain & EVM MCP server?

VerifyMCP ran 12 checks on BlockVectra Docs: Robinhood Chain & EVM, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about BlockVectra Docs: Robinhood Chain & EVM: HTTPS. 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.

## Links

- Remote endpoint: https://docs.blockvectra.com/mcp/docs
- Repository: https://github.com/blockvectra/mcp
- Website: https://blockvectra.com/en/agents/?ref=official-mcp-registry
- Changelog RSS feed: https://verifymcp.io/servers/com-blockvectra-docs/mcp-docs.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-blockvectra-docs/mcp-docs/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-blockvectra-docs/mcp-docs.json
- HTML version of this page: https://verifymcp.io/servers/com-blockvectra-docs/mcp-docs
