DevStackPulse

io.github.raulvallejoPublished by GitHub account raulvallejov1.2.0Updated Nov 1, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

DevStackPulse is a remote MCP server that gives an assistant breaking-change alerts and weekly digests for the APIs and SDKs in a developer's stack.

What you can do
No tool list is published, so capabilities are inferred from the description. The server reports breaking changes affecting the APIs and SDKs a developer uses. It also delivers weekly digests summarizing those changes. Access is tied to a DevStackPulse account, either through OAuth sign-in or an API key.
When to use it
Useful when you maintain integrations against third-party APIs or SDKs and want an assistant to surface breaking changes and periodic summaries without checking each vendor's changelog by hand.
Requirements
A remote streamable HTTP endpoint; no local package or runtime. A DevStackPulse account is required. Authentication is OAuth, or an Authorization header carrying a Bearer API key created in the account's Profile & Settings under API Access.
Before you install
The server requires an account credential: either OAuth sign-in or a live API key sent in the Authorization header. Treat that key as a secret and revoke it if exposed. The service is hosted by a third party, so the stack information you register is shared with it.

Installation

In SourceWeft

  1. Open DevStackPulse in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.raulvallejo%2Fdevstackpulse/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "devstackpulse": {
      "type": "http",
      "url": "https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.2.0LatestNov 1, 2026
  2. v1.0.0Oct 25, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.