Home / MCP registry index / io.usefulapi/slicktext

SlickText MCP by usefulapi

io.usefulapi/slicktext in the official MCP registry. Endpoint https://slicktext.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read SlickText contacts, lists, campaigns, analytics and inbox; create and update contacts.

Connect it

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

claude mcp add --transport http slicktext https://slicktext.usefulapi.io/mcp

{
  "mcpServers": {
    "slicktext": {
      "url": "https://slicktext.usefulapi.io/mcp"
    }
  }
}

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

Tools it advertises

slicktext_get_brand slicktext_get_credit_usage slicktext_list_contacts slicktext_find_contact slicktext_get_contact slicktext_list_custom_fields slicktext_list_lists slicktext_get_list slicktext_list_list_contacts slicktext_list_segments slicktext_list_segment_contacts slicktext_list_campaigns slicktext_get_campaign slicktext_get_campaign_stats slicktext_get_analytics slicktext_list_keywords slicktext_get_keyword slicktext_list_messages slicktext_list_conversations slicktext_get_conversation slicktext_list_inbox_tags slicktext_create_contact slicktext_update_contact slicktext_add_contact_to_lists

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-01): f06c1be96eee3997. 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.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-slicktext/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-slicktext)

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

Email MCP servers · Analytics and SEO MCP servers