mcpbeat Sign in

DevStackPulse MCP Server

by raulvallejo Your server? Claim it
answering

DevStackPulse is answering right now. Last checked moments ago. It exposes 3 tools.

Breaking changes and weekly digests for the APIs and SDKs in your dev stack.

Uptime history 9 days of history · worst day 50%
9 days agonow
81.1%
Uptime 24h
142 of 175 checks
3
Tools
read from the server
616 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

DevStackPulse does not always answer

Over the last week it answered 87.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 0 min ago.

run in your terminal
claude mcp add devstackpulse --transport http https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp
Settings → Connectors → Add custom connector, then paste this address
https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp
~/.codex/config.toml
[mcp_servers.devstackpulse]
url = "https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "devstackpulse": {
      "url": "https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "devstackpulse": {
      "type": "http",
      "url": "https://alieysrqiwcixizudvxb.supabase.co/functions/v1/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.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

breaking
get_my_breaking_changes
Get breaking changes detected in the user's sources, newest first. Each item includes `summary`: what broke and what the developer needs to do.
digest
get_my_digest
Get the user's latest weekly digest: its updates and the breaking changes sent with it.
sources
list_my_sources
List the developer tools and APIs the user monitors in DevStackPulse.

Endpoints

URLTransportStateLatencyChecked
https://stackpulse-mcp.onrender.com/mcp streamable-http answering 20000 ms 14 min ago
https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp streamable-http sign-in 541 ms 0 min ago

Alternatives to DevStackPulse

same job, measured the same way
mendapi
by mendapi

Detect API breaking changes, scan your codebase for impact, and draft the fix. Runs locally.

135 installs/wk local only
Semver Checks
by kyungseopk1m

Detect breaking changes in your TypeScript library's public API and recommend the SemVer bump.

568 installs/wk local only
Deprecation MCP
by tsvillain

MCP server for cross-vendor API/SDK deprecation and breaking-change tracking

53 installs/wk local only
apiwatch
by reignventures

Is this model or API still safe to call? Retirement and breaking change dates, with the fix.

7 tools answering
Specshield MCP Server
by specshield-io

The API-change deploy gate for AI coding agents. Read-only breaking-change detection.

local only
R
release-gate-mcp
by abduljabbarbxr

Release intelligence for AI agents. Detects breaking changes and recommends semver.

44 installs/wk local only
Spun WhatsApp MCP
by spun

Your business WhatsApp for any AI: read and search chats, digests, team stats, sends you approve.

answering
Schemaguard
by sethclawd-prog

API Schema Drift Monitor — detect breaking changes in OpenAPI specs

33 installs/wk local only

DevStackPulse — questions

Answers built from our own checks of this server.

What can DevStackPulse do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_my_breaking_changes, get_my_digest, list_my_sources. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is DevStackPulse working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 142 of 175 checks got a reply (81.1%), average response time 616 ms. The bar chart above shows every period we have measured.
How do I connect DevStackPulse?
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 sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to DevStackPulse?
No API key is involved. DevStackPulse answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is DevStackPulse?
It answers our handshake in 616 ms on average, which is faster than 17% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.