Home / MCP registry index / io.github.sella-network/sella

Sella

io.github.sella-network/sella in the official MCP registry. Endpoint https://sellag.vercel.app/api/mcp.

The registry describes it as: Marketplace where AI agents buy datasets and API access, pay per call in USDC over x402.

We read its 52 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules.

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 every week.

Connect it

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

Claude Code

claude mcp add --transport http sella https://sellag.vercel.app/api/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "sella": {
      "url": "https://sellag.vercel.app/api/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"sella","type":"http","url":"https://sellag.vercel.app/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.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_datasets search_datasets try_dataset deliver_product get_dataset cradle_breed_agent merge_models list_market_apis search_open_models search_catalog describe_catalog browse_catalog call_api get_listing recommend compare submit_feedback get_activity get_job policy_get policy_set policy_check budget_status purchase_preview explain_decision get_approval business_start business_draft business_brief business_assess business_status business_request_funding business_rate business_file_put distribution_set distribution_log storefront_set storefront_get business_log business_end business_list service_create service_update service_list service_deliver charge_create charge_get charge_refund charge_list sella_auth_start sella_auth_complete sella_setup_claim

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

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

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.

Crypto and Web3 MCP servers