Home / MCP registry index / io.usefulapi/sociocs
Sociocs MCP by usefulapi
io.usefulapi/sociocs in the official MCP registry.
Endpoint https://sociocs.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: List contacts and messages, send texts and delete scheduled messages in Sociocs.
We read its 15 tools on 2026-11-16. 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 sociocs https://sociocs.usefulapi.io/mcp{
"mcpServers": {
"sociocs": {
"url": "https://sociocs.usefulapi.io/mcp"
}
}
}code --add-mcp '{"name":"sociocs","type":"http","url":"https://sociocs.usefulapi.io/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-pluginsTools it advertises
sociocs_list_channels sociocs_get_channel sociocs_list_contact_lists sociocs_list_contacts sociocs_search_contacts sociocs_get_contact sociocs_list_messages sociocs_search_messages sociocs_list_unreplied_messages sociocs_list_scheduled_messages sociocs_list_bulk_jobs sociocs_list_team_members sociocs_list_webhook_subscriptions sociocs_send_message sociocs_delete_scheduled_message
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-16):
a5bdb85aec1bf8f2. 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-usefulapi-sociocs)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.