Home / MCP registry index / com.pikasim/pikasim

PikaSim

com.pikasim/pikasim in the official MCP registry. Endpoint https://pikasim.com/mcp. Source: github.com/codebruinc/pikasim-mcp.

The registry describes it as: Anonymous eSIMs, phone numbers, and SMS codes in 190+ countries. Crypto-paid; agents self-onboard.

Tools it advertises

search_esim_packages search_phone_plans get_package_details check_country_coverage get_pricing get_phone_plan_pricing search fetch create_wallet check_balance purchase_esim purchase_phone_plan get_esim_status topup_esim list_orders list_esims list_transactions create_deposit get_topup_options cancel_esim search_sms_services get_sms_service_countries list_sms_rentals order_sms_verification check_sms_verification cancel_sms_verification list_sms_orders rent_sms_number get_sms_rental_messages extend_sms_rental cancel_sms_rental

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-pikasim-pikasim/badge.svg)](https://lazaretto.dev/mcp-registry/com-pikasim-pikasim)

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.

Related

Crypto and Web3 MCP servers