Back to the tool index

send_message

16 servers reported a tool by this name when we called them. Names are chosen by whoever wrote the server, so two tools sharing a name do not have to do the same thing. We record what was reported, not what it does.

serverresult when we called ittools
com.wingmanprotocol.agent/gateway
https://agent.wingmanprotocol.com/mcp
answers-mcp 57
com.wingmanprotocol.agent/gateway
https://wingmanprotocol.com/mcp
answers-mcp 57
telegram-flow-builder-mcp
https://api.flowcastle.ai/api/mcp
answers-mcp 41
Himalayas Remote Jobs MCP Server
https://mcp.himalayas.app/mcp
answers-mcp 41
duami
https://duami.ai/mcp
answers-mcp 29
agent-broker
https://hatchloop.dev/mcp/agent-broker
answers-mcp 23
freelance-clearing
https://freelanceclearing.com/api/mcp
answers-mcp 20
teppek
https://mcp.teppek.com/mcp
answers-mcp 16
crevio-api
https://mcp.crevio.co/mcp
answers-mcp 14
supovia-mcp
https://mcp.supovia.com/mcp
answers-mcp 14
agentspub
https://mcp.agentspub.ai/mcp
answers-mcp 14
Almured Knowledge Layer
https://api.almured.com/mcp
answers-mcp 13
sms-whatsapp-messaging
https://hatchloop.dev/mcp/sms-whatsapp-messaging
answers-mcp 10
lettera
https://api.lettera.dev/mcp
answers-mcp 7
capmus
https://mcp.capmus.com/mcp
answers-mcp 6
supost
https://mcp.supost.com/mcp
answers-mcp 6

16 of these answered an MCP handshake on the day we checked. That is not a promise the tool works, only that the server was running and told us the tool existed.