Patchwire
REMOTE · PATCHWIRE.MONOWIRE.DEV
Hourly security advisories for JS, AI and web3 packages: ranges, fixes and exploit conditions.
Available components
Last scanned (10 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 952 tokens (~190/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −4
- HTTPS: pass → unverified ▼ security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Tool “get_advisories” rewrote its description, which is the text the model reads security
- Tool “latest_safe” rewrote its description, which is the text the model reads security
- Schema quality: 163 → 190 ▼ functional
- “get_advisories” added an optional parameter “since” cosmetic
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +5
- The server rewrote its instructions, which are the text every model session reads security
- Tool “latest_safe” rewrote its description, which is the text the model reads security
- Tool “get_advisories” rewrote its description, which is the text the model reads security
- Tool “get_advisory” rewrote its description, which is the text the model reads security
- Tool “get_platform_bulletins” rewrote its description, which is the text the model reads security
- Tool “list_feed” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: fair → excellent functional
- “get_advisories” reworded the description of “packages” cosmetic
- “get_advisory” reworded the description of “id” cosmetic
- “get_platform_bulletins” reworded the description of “platform” cosmetic
- “latest_safe” reworded the description of “package” cosmetic
- “list_feed” reworded the description of “days” cosmetic
- “list_feed” reworded the description of “limit” cosmetic
- “list_feed” reworded the description of “section” cosmetic
- “list_feed” reworded the description of “severity” cosmetic
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://patchwire.monowire.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=monowire.dev | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d96ffd877f7badea0e85fbb18b34354a |
| SANs: monowire.dev, patchwire.monowire.dev, *.patchwire.monowire.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of patchwire.monowire.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| monowire.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://patchwire.monowire.dev/mcp | Verified | 200 | |
| http (plaintext) | http://patchwire.monowire.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_advisories Advisories for packages ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| packages | array | yes | npm package names as written in package.json, 1 to 50, for example ["next", "@supabase/supabase-js"]. Names only, never versions: compare the returned ranges with your lockfile. |
| since | string | – | Only advisories new since this ISO date or date-time ("2026-10-27" is UTC midnight, or "2026-10-27T08:00:00Z"): published, or first read by Patchwire, after it. For a daily check, pass the time of yo… |
No output schema declared.
No examples provided.
get_advisory One advisory in full ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | An advisory id: CVE (CVE-2026-12345), GHSA (GHSA-xxxx-xxxx-xxxx), MAL or a Patchwire id. Any case; aliases resolve. |
No output schema declared.
No examples provided.
get_platform_bulletins Platform bulletins ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | One platform: vercel, supabase, cloudflare, railway, neon, postgres, clerk. Omit for every platform. |
No output schema declared.
No examples provided.
latest_safe Safe version per release line ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | One npm package name as written in package.json, for example "next" or "@solana/web3.js". |
No output schema declared.
No examples provided.
list_feed Latest advisories ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days back, from 1 to 30. Default 7. |
| limit | integer | – | How many advisories at most, from 1 to 50. Default 20. |
| section | string | – | Sector: js (JS runtimes and frameworks), stack (hosting and data platforms), ai (AI SDKs and agent tools), crypto (web3 libraries). Omit for every sector. |
| severity | string | – | Only this severity; watch is an announced change or upcoming fix. Omit for all. |
No output schema declared.
No examples provided.
How do I install the Patchwire MCP server?
Patchwire is a hosted endpoint at https://patchwire.monowire.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · patchwire.monowire.dev
claude mcp add --transport http dev-monowire-patchwire 'https://patchwire.monowire.dev/mcp'
What is the Patchwire MCP server?
Patchwire is an MCP server listed in the public MCP registry as dev.monowire/patchwire. Hourly security advisories for JS, AI and web3 packages: ranges, fixes and exploit conditions. This page covers its hosted endpoint (https://patchwire.monowire.dev/mcp).
Is the Patchwire MCP server safe to use?
Patchwire scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Patchwire MCP server expose?
Patchwire exposes 5 tools: get_advisories, get_advisory, latest_safe, list_feed, get_platform_bulletins. Their descriptions and schemas cost roughly 888 tokens of context every time the server is loaded.
Does the Patchwire MCP server require authentication?
No. We connected to Patchwire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Patchwire MCP server still maintained?
Patchwire is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Patchwire MCP server?
VerifyMCP ran 12 checks on Patchwire, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Patchwire: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.