Home / MCP registry index / io.github.oriondrayke/vino-and-views

Vino & Views

io.github.oriondrayke/vino-and-views in the official MCP registry. Endpoint https://api.vinoandviews.online/mcp/.

The registry describes it as: Free reports, EVM/Solana token payment links and capped zero-fee EVM USDC escrow. Wallet signatures.

We read its 23 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http vino-and-views https://api.vinoandviews.online/mcp/

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "vino-and-views": {
      "url": "https://api.vinoandviews.online/mcp/"
    }
  }
}

VS Code

code --add-mcp '{"name":"vino-and-views","type":"http","url":"https://api.vinoandviews.online/mcp/"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

capabilities payment_capabilities escrow_case prepare_escrow_action create_payment_request payment_request_status prepare_payment solana_payment_capabilities create_solana_payment_request prepare_solana_payment quote_usdc_cross_chain_transfer cross_chain_transfer_step claim_worth_it collectible_quote launchpad_fee_audit agent_budget_guard allowance_risk_check tx_preflight x402_health_check dependency_report launch_economics prepare_donation prepare_x402_donation

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-oriondrayke-vino-and-views/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-oriondrayke-vino-and-views)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Crypto and Web3 MCP servers