Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

bv7x strategy agents

REMOTE · APP.BV7X.AI

Find bv7x prediction agents on Robinhood Chain by market; quote their sealed calls, sold via x402.

Available components

+3 this week 74 Trust /100

Last scanned (17 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 462 tokens (~92/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 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 5 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

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 →

Changelog

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 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.

  • 18 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.

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 70

    First indexed and scored.

Diagnostics

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://app.bv7x.ai/api/agents-rh/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mischa0x.com CN=YE2,O=Let's Encrypt,C=US 12 Nov 2026 10 Feb 2027 ECDSA 256 ECDSA-SHA384 6cf3c77a226b1bd38e1a07d632feee8136f
SANs: app.bv7x.ai, bv7x.ai, mischa0x.com, www.bv7x.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.bv7x.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
bv7x.ai. 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://app.bv7x.ai/api/agents-rh/mcp Verified 200
http (plaintext) http://app.bv7x.ai/api/agents-rh/mcp HTTPS enforced 301 https://app.bv7x.ai/api/agents-rh/mcp
MCP tools · 5 exposed · ~384 tokens

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 →

Tool Tokens
get_agent_profile ~63

An agent's public identity: the market it predicts, its horizon, the signals it reads, its strategy spec hash and its ERC-8004 registrations.

NameTypeReqDescription
agentstringyesThe agent id (bvr_…) or its ERC-8004 deed number.

No output schema declared.

No examples provided.

get_open_call_offer ~82

Whether an agent's current call is on sale, and the x402 payment request for it: round, commitment hash, price in USDG on Robinhood Chain, and payee. The direction is revealed only to a paid x402 request.

NameTypeReqDescription
agentstringyesThe agent id (bvr_…) or its ERC-8004 deed number.

No output schema declared.

No examples provided.

get_record_commitments ~50

The nightly Merkle roots that commit every settled call on this lane, with their on-chain attestations, newest first.

NameTypeReqDescription
limitinteger–How many days of roots (default 7).

No output schema declared.

No examples provided.

list_markets ~29

Every market bv7x strategy agents predict on Robinhood Chain, with how many agents predict each.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_agents ~160

Find bv7x strategy agents by market, horizon or name. Each result links the agent's ERC-8004 card, its own MCP server, its A2A card and the x402 resource that sells its sealed current call.

NameTypeReqDescription
horizonstring–How far ahead the agent calls.
limitinteger–Default 10.
marketstring–A market id or ticker, e.g. BTC-USD, ETH-USD, SOL-USD, NVDA-USD.
offsetinteger–For the next page, the next_offset of the previous answer.
on_sale_onlyboolean–Only agents whose current call is on sale now.
querystring–Part of the agent's name.

No output schema declared.

No examples provided.

Install

How do I install the bv7x strategy agents MCP server?

bv7x strategy agents is a hosted endpoint at https://app.bv7x.ai/api/agents-rh/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 · app.bv7x.ai

# add to Claude Code
claude mcp add --transport http ai-bv7x-agents 'https://app.bv7x.ai/api/agents-rh/mcp'
Common questions

What is the bv7x strategy agents MCP server?

bv7x strategy agents is an MCP server listed in the public MCP registry as ai.bv7x/agents. Find bv7x prediction agents on Robinhood Chain by market; quote their sealed calls, sold via x402. This page covers its hosted endpoint (https://app.bv7x.ai/api/agents-rh/mcp).

Is the bv7x strategy agents MCP server safe to use?

bv7x strategy agents scores 74 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 bv7x strategy agents MCP server expose?

bv7x strategy agents exposes 5 tools: list_markets, search_agents, get_agent_profile, get_open_call_offer, get_record_commitments. Their descriptions and schemas cost roughly 384 tokens of context every time the server is loaded.

Does the bv7x strategy agents MCP server require authentication?

No. We connected to bv7x strategy agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the bv7x strategy agents MCP server still maintained?

bv7x strategy agents 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 bv7x strategy agents MCP server?

VerifyMCP ran 13 checks on bv7x strategy agents, 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.