Stepladder is answering right now. Last checked 11 min ago.
Put timed plans on the person's phone: steps, questions and waits that ring when a rest is over.
Over the last week it answered 75.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.
claude mcp add stepladder --transport http https://stepladderapp.com/mcp
{
"mcpServers": {
"stepladder": {
"url": "https://stepladderapp.com/mcp"
}
}
}
[mcp_servers.stepladder]
url = "https://stepladderapp.com/mcp"
{
"mcpServers": {
"stepladder": {
"url": "https://stepladderapp.com/mcp"
}
}
}
{
"mcpServers": {
"stepladder": {
"url": "https://stepladderapp.com/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://stepladderapp.com/mcp | streamable-http | sign-in | 491 ms | 11 min ago |
Your agent asks you a question on your phone, waits for the answer, then resumes.
Research Scan finds and verifies the 5–10 recent papers that matter most for a research question.
Recurring agent jobs that run on our servers and ping you only when the result changed.
Bulk Google Trends: interest over time, regions, rising queries and plain-English trend summaries.
stdio MCP server wrapping the Redmine REST API: issues, projects, users, time, wiki, versions.
Zero-model recall over your docs: the section that answers a question, in about a millisecond.
Google Trends for any number of keywords on one scale: interest over time, regions, rising queries.
Google Trends interest over time and by region, rising queries and trending searches.
Answers built from our own checks of this server.