Skip to content

Patchwire MCP server

dev.monowire/patchwiremonowire.devstreamable-httpv1.0.0Scanned

Hourly security advisories for JS, AI and web3 packages: ranges, fixes and exploit conditions.

5 tools: 5 only read.

Tools: 0 delete, 0 irreversible, 0 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. 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.
Govern this server →

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 Patchwire MCP server can do

The Patchwire MCP server is published by monowire.dev, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.0.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.

5 tools

Only reads 5Show 5 read-only tools
  • get_advisoriesCheck npm packages for security advisories.No findings

    Why it is in this group

    • The name "get_advisories" says "get": a word for reading.
    Description, as the server wrote it
    Check npm packages for security advisories. Start here before installing, upgrading or deploying: send 1 to 50 package names (never versions) and get, per package, its total and up to 20 advisories of the last 120 days, newest first, each with vulnerable ranges, fixed versions and the conditions that make it exploitable. A package with none returns total 0. Compare the ranges with your lockfile. For a daily check, pass since (the time of your last check) to get only what is new. For one advisory in full use get_advisory; for the version to upgrade to, use latest_safe.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_advisoryRead one advisory in full by id: CVE, GHSA, MAL or Patchwire id, any case, aliases resolve.No findings

    Why it is in this group

    • The name "get_advisory" says "get": a word for reading.
    Description, as the server wrote it
    Read one advisory in full by id: CVE, GHSA, MAL or Patchwire id, any case, aliases resolve. Returns its ranges, fixed versions, exploit conditions with the source sentence they come from, a summary and the sources. Use it after get_advisories or list_feed gave you an id. An unknown id, or one older than 120 days, returns an error.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_platform_bulletinsGet the security bulletins and announced changes of hosting and data platforms, which are not npm packages and never show in a lockfile: Vercel, Supabase, Neon and the other platfo…No findings

    Why it is in this group

    • The name "get_platform_bulletins" says "get": a word for reading.
    Description, as the server wrote it
    Get the security bulletins and announced changes of hosting and data platforms, which are not npm packages and never show in a lockfile: Vercel, Supabase, Neon and the other platforms of the platform parameter. Returns up to 50, newest first; omit platform for all of them. For npm packages, use get_advisories.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • latest_safeFind the version to upgrade to for one npm package.No findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    Description, as the server wrote it
    Find the version to upgrade to for one npm package. Returns, per release line (major, or minor for 0.x), the version that fixes every known advisory of the last 120 days; a line still affected has safe: null and the ids that keep it affected; a line hit with no fix of its own (14.x when only 15.x is fixed) has safe: null and upgrade_to, the lowest safe version above it. Also lists advisories with no fix found, and says whether this package name itself is flagged as malicious. Use it after get_advisories, to pick one target version per line.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_feedList the latest advisories across every tracked stack, newest first, without a package list.No findings

    Why it is in this group

    • The name "list_feed" says "list": a word for reading.
    Description, as the server wrote it
    List the latest advisories across every tracked stack, newest first, without a package list. Filter by sector (js, stack, ai, crypto) and severity; by default the last 7 days and at most 20 advisories (days 1 to 30, limit 1 to 50). An empty list means nothing matched. To check your own packages, use get_advisories instead.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:22 UTC, unchanged since Oct 31, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Posture changes

  1. Oct 31, 2026
    • Tools that change things, listed without credentials: 1 to 0

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.

  1. Tools5 changed.~5 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 0.View diff
    • Tools that change things, listed without credentials: 1 to 0

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http patchwire https://patchwire.monowire.dev/mcp
claude mcp add --transport http patchwire https://patchwire.monowire.dev/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__patchwire__get_advisories",
      "mcp__patchwire__get_advisory",
      "mcp__patchwire__latest_safe",
      "mcp__patchwire__list_feed",
      "mcp__patchwire__get_platform_bulletins"
    ],
    "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 patchwire. Review it before you use it.

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/dev.monowire/patchwire/verify?hash=6e8aa1ad499c1bf4e7f7d587218f53ed0d28bc2222da0d3fad708e3d0fb9e22a" | jq -e '.changed == false'

Pinned hash 6e8aa1ad499c, from Nov 9, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.monowire/patchwire/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.monowire/patchwire
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.monowire/patchwire.svg)](https://radar.anlyon.com/servers/dev.monowire/patchwire)

Source: MCP Registry. Synced Oct 24, 2026, 14:17 UTC.

Patchwire MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Patchwire MCP server safe?

No scan can promise that. What its definitions show: 5 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 Patchwire MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Patchwire 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 Patchwire MCP server have?

5 tools: 5 read. get_advisories, get_advisory, latest_safe, list_feed and get_platform_bulletins.

Does the Patchwire MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Patchwire MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Patchwire MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.