Home / MCP registry index / io.github.callpaymin/callpaymin
Callpaymin
io.github.callpaymin/callpaymin in the official MCP registry.
Endpoint https://www.callpaymin.io/api/mcp.
The registry describes it as: Find experts, check availability, and book pay-per-minute calls on Callpaymin.
We read its 62 tools on 2026-11-03. 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 about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http callpaymin https://www.callpaymin.io/api/mcp{
"mcpServers": {
"callpaymin": {
"url": "https://www.callpaymin.io/api/mcp"
}
}
}code --add-mcp '{"name":"callpaymin","type":"http","url":"https://www.callpaymin.io/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.
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.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
search_experts get_expert list_categories check_expert_online get_reviews get_platform_stats get_country_rate_caps estimate_call_cost get_supported_currencies get_supported_payout_countries get_wallet_balance get_payment_methods disable_auto_recharge end_call get_call_session create_meeting_room list_my_meeting_rooms list_participants close_meeting_room list_my_calls get_receipt get_my_profile update_profile update_rate set_availability get_application_status get_earnings_summary get_releasable_balance list_payouts get_payout_methods favorite_expert unfavorite_expert list_favorites get_referral_code get_referral_stats apply_referral_code get_rate_coach_suggestion get_deep_link get_expert_availability list_my_bookings create_booking cancel_booking list_jobs list_my_jobs post_job respond_to_job close_job convert_currency start_chat send_message get_chat_summary join_meeting_room list_my_chats set_do_not_disturb clear_do_not_disturb submit_application get_tax_docs rate_call mute_participant toggle_recording and 2 more
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-03):
f262362eb72eb3d4. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/io-github-callpaymin-callpaymin)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. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.