Skip to content
Settro logo

Settro MCP server

Which MCP servers are Settro's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Settro

Whose server it is
  • Registry namenet.settro/sales-teamverified in the MCP registry

The registry name sits under settro.net. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools4
  • Server calls itselfsettro-sales-team
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 378 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: Take restaurant orders through SMS and social DMs; Move reel viewers into direct order conversations.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 4 of 4 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it0 of 2 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer387 ms
  • Space in an agent's context≈ 681 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsC · 67 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 4
  • Not saying whether it only reads or can destroy: 4 of 4

What an agent can do with it

  • not sure · Recover orders from missed restaurant phone calls
  • cannot · Take restaurant orders through SMS and social DMs
  • cannot · Move reel viewers into direct order conversations

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-26
  • estimate_missed_call_loss

    Estimate public missed-call leakage for a restaurant using Settro's public calculator model.

  • compare_direct_order_recovery_options

    Compare manual callback, marketplace redirect, and Settro direct-order recovery using public workflow criteria.

  • assess_social_ordering_readiness

    Score a restaurant's public social-ordering readiness using Settro's deterministic 100-point rubric.

  • generate_settro_fit_summary

    Summarize public Settro fit using POS compatibility, missed-call pain, social ordering interest, and direct-order channel needs.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "sales-team": {
      "type": "http",
      "url": "https://mcp.settro.net/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http settro https://mcp.settro.net/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.settro.net/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.