patchbay
NPM · @PATCHBAY-NEBIUS/MCP
Audit any remote MCP server for OAuth 2.1 and security gaps.
Available components
Last scanned (21 hours ago)
Scores higher than 39% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 122 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1155 tokens (~231/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 Management37
- Stability observed for 11 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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 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.
- 16 Nov 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.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Nov 26 0
- Malware scan: unverified → pass ▲ security
- Schema quality: 208 → 231 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.3.2 → 0.4.1 functional
- 10 Nov 26 48
First indexed and scored.
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 21 Nov 2026 · Analysed npm/@patchbay-nebius/mcp@0.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 122 packages
| Packages resolved | 122 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
audit_mcp_server Audit an MCP server for OAuth 2.1 and security gaps ~524
Scan a remote MCP server URL (or a local MCP connector directory) for OAuth 2.1, RFC 8707 audience validation, RFC 8252 loopback redirects, OAuth metadata, scope posture, secret surface, tool manifest drift, and tool-description prompt injection patterns. Returns a letter grade, numeric score and the full findings list. Runs zero-auth probing by default (metadata-level checks only). Pass "authToken" to probe behind authentication. Pass "probeAudienceToken" to enable AUDIENCE-001 (cross-audience token check, RFC 8707). Pass "probeMissingAudToken" to enable AUDIENCE-002 (missing-aud-claim check, catches the if (aud && aud !== me) reject early-exit bug). Pass "probeDcrLoopback: true" to enable AUTH-006 (writes a throw-away client registration to the authorization server). Pass "probeHeadlessOauth: true" to enable the OAuth 2.1 conformance battery (PKCE-001 missing PKCE, PKCE-002 plain PKCE, IMPLICIT-001 implicit grant, REDIRECT-002 unregistered redirect_uri). The scanner never calls any of the server's tools.
| Name | Type | Req | Description |
|---|---|---|---|
| authToken | string | – | Bearer token to send on every probe request. Use for servers that require authentication beyond initialize. |
| probeAudienceToken | string | – | Bearer token minted for a DIFFERENT resource on the same authorization server. Enables AUDIENCE-001 (RFC 8707 cross-audience check). |
| probeDcrLoopback | boolean | – | Opt into AUTH-006 active Dynamic Client Registration loopback probe (RFC 8252 Section 7.3). Writes a throw-away client to the authorization server; off by default. |
| probeHeadlessOauth | boolean | – | Opt into the OAuth 2.1 conformance battery (PKCE-001, PKCE-002, IMPLICIT-001, REDIRECT-002). Registers a throw-away client via DCR, then sends four crafted /authorize requests. Off by default. |
| probeMissingAudToken | string | – | Bearer token whose JWT payload has NO aud claim at all. Enables AUDIENCE-002 (catches `if (aud && aud !== me) reject` early-exit bug per RFC 9068 Section 4). |
| target | string | yes | MCP server URL (https://...) or absolute path to a local connector directory. |
| timeoutMs | integer | – | Per-request timeout in milliseconds. Default 8000. |
No output schema declared.
No examples provided.
build_connector Build a connector ~170
Describe an integration in one sentence ("When X happens in A, do Y in B"). patchbay plans it, researches both APIs, generates a connector with tests and a README, then verifies it in a sandbox with up to N repair attempts. Default language is TypeScript (vitest); set lang: "py" for Python 3.12 (pytest). Falls back to the recorded TypeScript replay run when live API keys are missing.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Target language. "ts" (default) emits TypeScript+vitest; "py" emits Python 3.12+pytest. Live keys required for "py". |
| maxAttempts | integer | – | Repair attempts, default from PATCHBAY_MAX_ATTEMPTS |
| prompt | string | yes | One-sentence integration description |
No output schema declared.
No examples provided.
research_api Research an integration ~71
Plan + Tavily-backed API research only. Returns the connector plan, the ranked documentation sources, and a normalized API spec (endpoints, auth, example payloads). No code is generated and no sandbox is used, so this is cheap and fast.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | One-sentence integration description |
No output schema declared.
No examples provided.
scan_repo Scan a repo for integration opportunities ~201
Walk a repository (local directory or shallow-cloned GitHub URL) and report the integration opportunities patchbay could build: webhook handlers with TODO/empty bodies, .env.example entries pointing at vendor APIs with no implementation, TODO/FIXME comments mentioning vendors, and vendor SDKs imported but barely used. Understands TypeScript/JavaScript (Express/Next/Fastify routes) AND Python (FastAPI/Flask routes, pass bodies, raise NotImplementedError). Returns a ranked list, each item with a ready-to-run prompt the agent can hand straight to build_connector. Instant, free (no LLM / sandbox), auditable regex-only output.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to a repo directory on disk, or a GitHub URL (https://github.com/<owner>/<repo> — shallow-cloned to a tempdir and scanned). |
| topN | integer | – | How many top-ranked opportunities to return. Default 15. |
No output schema declared.
No examples provided.
verify_code Verify a connector ~189
Type-check and test an existing connector (files you provide as {path, content}) in an isolated Nebius sandbox, with up to N repair attempts from the strong model. For TypeScript (default) the gate is tsc + vitest; for Python (lang: "py") it is compileall + pytest. Requires live keys (NEBIUS_API_KEY, NEBIUS_AI_PROJECT); returns the final test report and the (possibly repaired) files.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Connector files. For TS, include src/connector.ts + a *.test.ts; for Python, include connector.py + test_connector.py. |
| lang | string | – | Target language the files are in. "ts" (default) or "py". If omitted, auto-detected from file extensions. |
| maxAttempts | integer | – | Repair attempts, default from PATCHBAY_MAX_ATTEMPTS |
No output schema declared.
No examples provided.
How do I install the patchbay MCP server?
patchbay runs locally as an npm package, launched with npx -y @patchbay-nebius/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @patchbay-nebius/mcp
claude mcp add godsmasher-patchbay -- npx -y @patchbay-nebius/mcp
What is the patchbay MCP server?
patchbay is an MCP server listed in the public MCP registry as io.github.GodSmasher/patchbay. Audit any remote MCP server for OAuth 2.1 and security gaps. This page covers its npm package (@patchbay-nebius/mcp).
Is the patchbay MCP server safe to use?
patchbay scores 68 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 patchbay MCP server expose?
patchbay exposes 5 tools: build_connector, research_api, scan_repo, verify_code, audit_mcp_server. Their descriptions and schemas cost roughly 1,155 tokens of context every time the server is loaded.
Is the patchbay MCP server still maintained?
patchbay is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the patchbay MCP server under?
patchbay declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the patchbay MCP server?
VerifyMCP ran 16 checks on patchbay, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.