DevStackPulse MCP server
io.github.raulvallejo/devstackpulseraulvallejostreamable-httpv1.2.0Scanned
Breaking changes and weekly digests for the APIs and SDKs in your dev stack.
3 tools: 3 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the DevStackPulse MCP server can do
The DevStackPulse MCP server is published by the GitHub account raulvallejo. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools bring in text other people can write (list_my_sources, get_my_breaking_changes and get_my_digest).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Oct 25, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Only reads 3Show 3 read-only tools
get_my_breaking_changesGet breaking changes detected in the user's sources, newest first.Reads text others writeNo findings
Why it is in this group
- The name "get_my_breaking_changes" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get breaking changes detected in the user's sources, newest first. Each item includes `summary`: what broke and what the developer needs to do.
Annotations the server declares
- openWorldHint: true
- readOnlyHint: true
get_my_digestGet the user's latest weekly digest: its updates and the breaking changes sent with it.Reads text others writeNo findings
Why it is in this group
- The name "get_my_digest" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get the user's latest weekly digest: its updates and the breaking changes sent with it.
Annotations the server declares
- openWorldHint: true
- readOnlyHint: true
list_my_sourcesList the developer tools and APIs the user monitors in DevStackPulse.Reads text others writeNo findings
Why it is in this group
- The name "list_my_sources" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List the developer tools and APIs the user monitors in DevStackPulse.
Annotations the server declares
- openWorldHint: true
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:23 UTC, unchanged since Nov 2, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata
- https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp/.well-known/oauth-protected-resource
- Authorization servers
- https://alieysrqiwcixizudvxb.supabase.co/auth/v1
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
Posture changes
- Nov 2, 2026
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: none to https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp/.well-known/oauth-protected-resource
- Authorization servers: none to https://alieysrqiwcixizudvxb.supabase.co/auth/v1
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Protocol version: 2025-06-18 -> none (and 6 more).View diff
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: none to https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcp/.well-known/oauth-protected-resource
- Authorization servers: none to https://alieysrqiwcixizudvxb.supabase.co/auth/v1
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http devstackpulse https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcpclaude mcp add --transport http devstackpulse https://alieysrqiwcixizudvxb.supabase.co/functions/v1/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__devstackpulse__list_my_sources",
"mcp__devstackpulse__get_my_breaking_changes",
"mcp__devstackpulse__get_my_digest"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as devstackpulse. Review it before you use it.
Capability tags behind 3 rules
- mcp__devstackpulse__list_my_sources untrusted-input
- mcp__devstackpulse__get_my_breaking_changes untrusted-input
- mcp__devstackpulse__get_my_digest untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.raulvallejo/devstackpulse/verify?hash=539b051c01d3f6aeeceecace312eae676d6bc5ed53c097e3aeb6e72727723a8b" | jq -e '.changed == false'Pinned hash 539b051c01d3, from Oct 25, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.raulvallejo/devstackpulse/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.raulvallejo/devstackpulse)Source: MCP Registry. Synced Nov 1, 2026, 10:17 UTC.
DevStackPulse MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the DevStackPulse MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the DevStackPulse MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the DevStackPulse MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the DevStackPulse MCP server have?
- 3 tools: 3 read. list_my_sources, get_my_breaking_changes and get_my_digest.
Does the DevStackPulse MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the DevStackPulse MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the DevStackPulse MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.