Home / MCP registry index / com.360dialog/mcp

360dialog

com.360dialog/mcp in the official MCP registry. Endpoint https://mcp.360dialog.com/mcp.

The registry describes it as: Manage WhatsApp Business accounts on 360Dialog: channels, templates, sandbox, inbox, and more.

Connect it

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

claude mcp add --transport http 360dialog https://mcp.360dialog.com/mcp

{
  "mcpServers": {
    "360dialog": {
      "url": "https://mcp.360dialog.com/mcp"
    }
  }
}

code --add-mcp '{"name":"360dialog","type":"http","url":"https://mcp.360dialog.com/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 lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_skills get_skill start_signup search_client_documentation get_client_documentation_page get_balance list_channels set_display_name get_channel_profile update_channel_profile get_invoices wait_for_onboarding_step get_company_details update_company_details check_number_eligibility start_number_onboarding start_payment_setup get_onboarding_status request_otp verify_otp list_templates show_template_preview get_template_json_example create_template delete_template get_webhook set_webhook test_webhook get_self list_users sandbox_register_number sandbox_complete_registration sandbox_send_message sandbox_configure_webhook sandbox_get_webhook_configuration sandbox_list_events getchat_send_message getchat_assign_conversation getchat_tag_conversation getchat_mark_conversation_as_read getchat_apply_saved_response getchat_list_conversations getchat_search_conversations getchat_get_conversation getchat_list_inboxes getchat_list_agents getchat_list_groups getchat_list_tags getchat_list_saved_responses mba_check_agent_eligibility mba_onboard_agent mba_delete_agent mba_get_agent_settings mba_update_agent_settings mba_list_allowlist_entries mba_add_allowlist_entry mba_remove_allowlist_entry mba_get_business_info mba_update_business_info mba_reset_business_info and 56 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-08): f20725c8f84ae00f. 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:

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

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.

Related

Email MCP servers