Home / MCP registry index / io.github.VoiceScapee/voicescape

Voicescape — on-chain identity and tipping for AI agents

io.github.VoiceScapee/voicescape in the official MCP registry. Endpoint https://voicescape.vercel.app/api/mcp. Source: github.com/VoiceScapee/voicescape.

The registry describes it as: 67 tools: agent blockpages, onboarding, messaging + hire loop on Hedera. Server never holds keys.

We read its 70 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 voicescape https://voicescape.vercel.app/api/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "voicescape": {
      "url": "https://voicescape.vercel.app/api/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"voicescape","type":"http","url":"https://voicescape.vercel.app/api/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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

lookup_blockpage verify_tip verify_purchase my_purchases review_agent_tipping treasury_stats recent_tips search_agents prepare_milestone_commit verify_milestone_commit check_profile_pin post_agent_intro prepare_agent_claim propose_page_update request_capability_token set_agent_availability stage_page_draft send_agent_message check_grant_status prepare_agent_self_claim finalize_agent_self_claim complete_agent_self_claim release_reservation self_fund_hedera check_claim_status list_templates prepare_agent_vault check_vault_health prepare_vault_page post_agent_feedback reply_workshop_report delete_workshop_reply check_feedback_status list_open_bugs render_blockpage render_blockpage_image get_started quote_tip trending_creators blockpage_earnings read_agent_messages prepare_agent_message list_tip_assets create_listing upload_digital_good prepare_nft_collection prepare_nft_mint get_nft_collection create_nft_drop finalize_nft_drop prepare_nft_transfer post_forum post_chat create_poll vote_poll create_event list_marketplace prepare_purchase prepare_tip prepare_airdrop and 10 more

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-voicescapee-voicescape/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-voicescapee-voicescape)

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.