Home / MCP registry index / io.github.sorzio/sorzio

Sorzio

io.github.sorzio/sorzio in the official MCP registry. Endpoint https://www.sorzio.com/api/mcp. Source: github.com/sorzio/sorzio-mcp.

The registry describes it as: B2B web & LinkedIn enrichment, email verification, ICP scoring & AI copy for up to 25,000 leads.

Connect it

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

claude mcp add --transport http sorzio https://www.sorzio.com/api/mcp

{
  "mcpServers": {
    "sorzio": {
      "url": "https://www.sorzio.com/api/mcp"
    }
  }
}

code --add-mcp '{"name":"sorzio","type":"http","url":"https://www.sorzio.com/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-plugins

Tools it advertises

get_started open_dashboard get_account list_models estimate_cost get_history list_lists create_list add_rows get_rows export_list delete_list purge_lists list_sheets read_sheet list_prompts get_prompt save_prompt delete_prompt preview_prompt run_ai run_verify run_scrape get_run cancel_run retry_failed get_run_rows export_run list_flows get_flow save_flow delete_flow run_flow get_flow_run cancel_flow_run list_schedules create_schedule delete_schedule list_page_templates publish_list_pages get_page_analytics

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): 348b84a2bd0aa1f3. 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/io-github-sorzio-sorzio/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-sorzio-sorzio)

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 · Social media MCP servers