Smithery's October 2026 Change: Point BlockVectra MCP Directly

Smithery has announced that on October 31, 2026, it will stop connection management. According to its official announcement, that change covers the run.tools and server.smithery.ai proxy endpoints, managed identity, accounts and API keys, the API/Connect/Toolbox surfaces, and its CLI and SDK. Its public, non-proxy MCP registry will remain.

If your client uses Smithery to reach BlockVectra, plan to point it directly at the vendor endpoint instead. This is not a universal replacement for every MCP server: only BlockVectra's own MCP endpoint is covered here, and other servers should move to their respective official endpoints.

Use the direct BlockVectra endpoint

The endpoint is https://docs.blockvectra.com/mcp. The current guide describes a stateless Streamable HTTP transport using JSON-RPC 2.0 over POST. Update your existing client entry rather than adding a duplicate connection. Config keys differ across clients, so use the guide's client-specific examples rather than copying a universal JSON shape or inventing local CLI flags.

A browser GET to the endpoint returns 405. That response alone does not prove an outage; the endpoint expects POST.

To list tools without credentials, run:

curl -sS --max-time 20 \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \
  https://docs.blockvectra.com/mcp

This lists tools; it does not prove that a business RPC will succeed.

Verify before removing the old connection

Connecting, listing tools and reading documentation need no API key. As one small client-side check, call the read_doc tool with arguments path=quickstart and lang=en. It reads documentation only. Check for JSON-RPC errors and the tool's isError value, not just HTTP 200.

Indexed data and account tools need your own BlockVectra API key in the client's HTTP x-api-key header; Authorization: Bearer is also documented. Public RPC eligibility depends on the actual chain's public.methods. Do not assume every tool, transaction or dataset is keyless, and do not hard-code a tool count.

Do not carry a Smithery key into BlockVectra headers. Never place an API key or private key in tool arguments, URLs or chat. Avoid changing global permissions as a shortcut.

Complete the client handshake, tool list and doc read first. Then separately validate any authenticated or business tasks against the chains and methods you actually need before deleting the old connection. A successful doc read does not establish business-RPC or dataset coverage.

Client install choices and auth details: BlockVectra MCP server guide.