mcpbeat Sign in

Speed To Lead MCP Server

by composedchaos Your server? Claim it
answering

Speed To Lead is answering right now. Last checked 6 min ago.

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

Uptime history 91 days of history · worst day 0%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
407 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.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add speed-to-lead --transport http https://api.composedchaos.net/stl-mcp/
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "speed-to-lead": {
      "type": "http",
      "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

URLTransportStateLatencyChecked
https://api.composedchaos.net/stl-mcp/ streamable-http needs auth 398 ms 6 min ago

Alternatives to Speed To Lead

same job, measured the same way
Buoy Gg
by buoy-gg

Let AI agents read and drive a running React Native or Flutter app through Buoy's devtools.

1 499 installs/wk local only
Agent Shaniu (SHANIU)
by m284743

First AI-driven community meme coin on BSC. Mint, trade and referral tools for AI agents.

7 tools answering
veddata
by sanzineo

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

102 installs/wk local only
Layven
by layven

Shared drive for your agents and teammates.

answering
InDesign MCP Server
by zachshallbetter

Drive Adobe InDesign from any MCP client: 135+ tools for layout, styles, books and PDF export.

301 installs/wk local only
A
AgentDrive
by tokencanopy

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

answering
Copilot Datagate
by afurlane

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

67 installs/wk local only
oassis — web for agents
by oassis

Read, map and crawl the web, and drive a real browser. Pay per call, no key, no signup.

14 tools answering

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 91 of 91 checks got a reply (100.0%), average response time 407 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 in the form 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 407 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.