Speed To Lead MCP Server

by composedchaos Your server? Claim it

answering

Speed To Lead is answering right now. Last checked moments ago.

Field-service tools for agents: slot feasibility, drive time, service area, lead parsing, booking.

Uptime history 48 days of history · worst day 0%

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

411 ms

Response time

average over 24h

authentication required

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Speed To Lead every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add speed-to-lead --transport http https://api.composedchaos.net/stl-mcp/

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "speed-to-lead": {
      "url": "https://api.composedchaos.net/stl-mcp/"
    }
  }
}

~/.codex/config.toml

[mcp_servers.speed-to-lead]
url = "https://api.composedchaos.net/stl-mcp/"

.cursor/mcp.json

{
  "mcpServers": {
    "speed-to-lead": {
      "url": "https://api.composedchaos.net/stl-mcp/"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "speed-to-lead": {
      "url": "https://api.composedchaos.net/stl-mcp/"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://api.composedchaos.net/stl-mcp/	streamable-http	needs auth	405 ms	0 min ago

Alternatives to Speed To Lead

same job, measured the same way

Rivemcp

by paradoxsyn

MCP server for creating and editing Rive (.riv) animation files. 139 tools for AI-driven animation.

615 installs/wk local only

veddata

by sanzineo

MCP server for AI agents: discover a web page's data sources and drive the page to reach them.

local only

Layven

by layven

Shared drive for your agents and teammates.

answering

AgentDrive

by tokencanopy

Artifact store for AI agents — read, write, and search files by path; share by rendered URL.

answering

Persis

by alright-alright

Biological memory for AI agents. Pattern learning, decay, clustering, 8-drive behavior.

answering

Copilot Datagate

by afurlane

Policy-driven, read-only MCP server for safe database access from AI tools.

32 installs/wk local only

Smolanalytics

by arjun0606

End-to-end tests from one sentence: an agent drives a real browser, and passing runs replay free.

166 installs/wk local only

Mcacp

by oortonaut

MCP-to-ACP bridge — let any MCP client drive ACP coding agents

125 installs/wk local only

Speed To Lead — questions

Answers built from our own checks of this server.

Why is there no tool list for Speed To Lead?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Speed To Lead working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 411 ms. The bar chart above shows every period we have measured.

How do I connect Speed To Lead?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Speed To Lead need an API key?

Yes. Every time we knock, Speed To Lead answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Speed To Lead?

It answers our handshake in 411 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.