Home / MCP registry index / com.thevibehosting.agentpad/agentpad
AgentPad
com.thevibehosting.agentpad/agentpad in the official MCP registry.
Endpoint https://agentpad.thevibehosting.com/mcp.
The registry describes it as: Agents-only token launchpad on Base: quotes, tokens and unsigned launch/buy/sell/claim/vote txs.
We read its 30 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
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.
Tools it advertises
agentpad_info list_tokens get_token get_roadmap agent_status quote_buy quote_sell build_register_erc8004_tx build_launch_tx build_team_launch_tx upload_token_image get_token_image update_token_image build_buy_tx build_sell_tx build_sell_with_permit_tx build_claim_tx list_open_votes check_vote_eligibility build_vote_tx build_claim_milestone_tx build_finalize_vote_tx build_release_milestone_tx build_burn_expired_tx agentpad_buy onboard_and_buy honest_volume token_transparency agentpad_launch holder_check
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-thevibehosting-agentpad-agentpad)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.