The computer is off.

No. 055 Ledger of 18 November 2026Ledger 18 Nov 2026 From the author

playb0t // Security Research

mcp-remote OAuth trust-boundary research

Listed by sixteen registries and databases, copied in eighty-three places, written up once, acted on by twenty-four projects. No independent verification on record. No fix on record.

Five CVE records were published on 24 September 2026 for mcp-remote, the npm package that connects local AI clients to remote MCP servers. This page logs, with a date and a source for every line, who has republished the records, who has acted on them, and what has not happened yet.

Published CVE records
5
published 24 Sep 2026 · CNA MITRE · all five scored by CISA-ADP
Peak CISA score
9.8 Critical
CVE-2026-51996 · and 9.1 Critical, CVE-2026-51994
Public files that pin a listed version
880
468 of them pin 0.1.38, the last version the records name. · GitHub code search · counted 16 Nov
Upstream fixes stated
0
latest 0.16.6 of 11 November 2026 · the discovery path runs in 68 of 70 stable releases 0.1.32–0.16.6

read 21 Oct 2026 Downloads since the private report of 17 February 2026

19,935,310

17 February 2026 – 18 October 2026 · api.npmjs.org

The wall of 68 releases

  • 0.1.38 the records end here
  • 0.14.3 the CLI was run in full here
  • 0.15.1 the CLI was run in full here, 15 October
  • 0.16.6 the CLI was run in full here, 14 November

The five records: state and CISA score

  1. CVE-2026-51996

    MD5-based storage namespace hardening

    9.8 Critical · 0.1.16–0.1.38

    View ↗

  2. CVE-2026-51994

    SSRF via unvalidated resource_metadata

    9.1 Critical · 0.1.32–0.1.38

    View ↗

  3. CVE-2026-51997

    Incomplete internal-address validation before browser launch

    8.8 High · 0.1.16–0.1.38

    View ↗

  4. CVE-2026-51995

    Blind SSRF via authorization_servers[]

    7.5 High · 0.1.32–0.1.38

    View ↗

  5. CVE-2026-52001

    Explicit token-origin binding as transport hardening

    7.5 High · 0.1.18–0.1.38

    View ↗

ledger of 18 November 2026

Registry state

The records

Registry state as recorded in this dated ledger. The live cards above read official states and CISA scores again in your browser.

RecordCISA scoreCISA SSVCNVDGitHub advisoryOSVEUVDEPSS
CVE-2026-51994F-01 · CISA: CWE-918SSRF via unvalidated resource_metadata9.1Criticalautomatabletotal impactDeferredunreviewedno packagelistedEUVD-2026-86017score 9.10.45%
CVE-2026-51995F-02 · CISA: CWE-200Blind SSRF via authorization_servers[]7.5Highautomatablepartial impactDeferredunreviewedno packagelistedEUVD-2026-86018score 7.50.47%
CVE-2026-51996F-04 · CISA: CWE-328MD5-based storage namespace hardening9.8Criticalautomatabletotal impactDeferredunreviewedno packagelistedEUVD-2026-86019score 9.80.47%
CVE-2026-51997F-08 · CISA: CWE-20, CWE-94, CWE-918Incomplete internal-address validation before browser launch8.8Highnot automatabletotal impactDeferredunreviewedno packagelistedEUVD-2026-86020score 8.80.53%
CVE-2026-52001F-11 · CISA: CWE-200Explicit token-origin binding as transport hardening7.5Highautomatablepartial impactDeferredunreviewedno packagelistedEUVD-2026-86021score 7.50.47%
CVE-2026-51998reserved, not published; the author states it belongs to the same request
CVE-2026-51999reserved, not published; the author states it belongs to the same request

Registry state as recorded in the ledger of 18 November 2026. CISA scores and SSVC decisions are shown as CISA published them; the section The five records, read now reads the CISA score again on each load. OSV carried a “fixed 0.1.38” marker from 25 September to 21 October and then withdrew it; all five records now list 0.1.38 as last affected, and no maintainer statement of a fix exists. The correction is recorded under Divergences.

None of the records is in CISA's Known Exploited Vulnerabilities catalog (catalog of 17 Nov).

Research repository playb0t/mcp-remote-oauth-security · 3 stars · 3 forks · 58 views from 32 visitors in 14 days · referrers in the 14 days to 18 Nov (visits): github.com 5, avd.aliyun.com 1, playb0t.com 1 (GitHub repository statistics, ledger of 18 Nov 2026)

Exposure, by public numbers

Downloads of the versions the records list, public version pins and package mappings. These counts do not measure installations, active users or compromise.

Downloads of the versions the records list

Listed versions · ledger of 18 Nov 2026

302,739

of 1,482,459 npm downloads · 20.4 %

  • later releases, up to 0.16.6 (latest, published 11 November 2026): 79%

npm per-version counter · saved ledger reading; no live request was made for this HTML.

Downloads, not people: one build pipeline can account for hundreds. The records' text stops at 0.1.38, and no later release is stated fixed by the maintainer. On 14 October 2026 the maintainer published 0.14.4, 0.14.5, 0.15.0 and 0.15.1 between 18:27 and 22:36 UTC; none of the four release notes names any of the five records, and 0.15.1 was the current release until 20 October. The 9 October loopback run of 0.14.3 was repeated on 0.15.1 on 15 October by the author's agent, with the same procedure: the client followed the server-named discovery destination through a redirect, requested authorization-server metadata there, and in the full trace sent a token request carrying an Authorization header to that server's token endpoint (seen on 0.14.3 and 0.15.1 alike; the 9 October snapshot closed before that request). These are the request paths of CVE-2026-51994 and CVE-2026-51995. The helper functions behind all five records are byte-identical between 0.14.3 and 0.15.1; the paths of the other three records were confirmed in code and by the extracted functions, not by a full run. The bundled SDK is still @modelcontextprotocol/client 2.0.0. Requests to extend the first two records to 0.14.3 have been pending at MITRE since 10 October. On 20 October 2026 17:19 UTC the maintainer published 0.15.2 (release note: 'open the browser for the client registered after a stale one is cleared', #383). The published package was downloaded from the registry on 21 October and compared with 0.15.1 file by file: the differences are the version string, the main chunk's file name and one added statement in that chunk (`this.pendingFlow = null`); the six bundled @modelcontextprotocol/client 2.0.0 module markers and the discovery, resource-selection and callback helpers are present unchanged. The author's agent's fragment matcher separately matched 8 of 8 selected client/core 2.0.0 fragments in 0.15.2. On 2 November 2026 05:25 UTC the maintainer published 0.16.0 (release note: a `--bind-host` option for the callback server, #386); the release notes of 0.15.2 and 0.16.0 name none of the five records. On 3 November the author's agent repeated the 15 October procedure on the published 0.15.2 and 0.16.0 (archives checked against the registry's integrity values): the client followed the server-named discovery destination through a redirect and requested authorization-server metadata at the origin the resource metadata named, on both releases, in the same three loopback scenarios; the full traces again carried one token request with an Authorization header to the fixture's own token endpoint. The ten helper functions behind the five records are byte-identical across 0.15.1, 0.15.2 and 0.16.0; the published distribution changes are the version string, one OAuth state reset in 0.15.2 and the bind-host plumbing in 0.16.0. Two paths were measured at runtime for the first time: on both releases the authorization URL taken from the server's metadata reached the installed browser-opener call and a controlled child process (no browser launched, no code execution shown), and bearer transfer across a cross-origin redirect of the SSE transport was not reproduced on the tested dependency graph, where a foreign endpoint is rejected. The October helper sources, missing from the 15 October folder, are published in full with the 3 November results. On 5 November 2026 20:42 UTC the maintainer published 0.16.1 (release note: build against zod 4.6.6 or later, outside GHSA-mrhx-c7xc-m3w5, #387, a zod advisory that is not one of the five records). The note names none of the five records. The source comparison v0.16.0...v0.16.1 is one commit touching two files, package.json and pnpm-lock.yaml: no line of mcp-remote's own code changed, and the release claims no fix for any of the five records. The published package was compared with 0.16.0 on 6 November: the bundled zod moves from 4.4.3 to 4.6.7; outside zod the differences are the version string, the main chunk's file name and bundler renames; the bundled @modelcontextprotocol/client 2.0.0 stays, and the src/lib sections the records concern are unchanged after renames are normalised. mcp-remote's own code in 0.16.1 is the code measured on 0.16.0 on 3 November. On 6 November 2026 the maintainer published 0.16.2, 0.16.3 and 0.16.4 between 22:30 and 22:54 UTC. The release notes name none of the five records. The published 0.16.3 still carries @modelcontextprotocol/client 2.0.0. The published 0.16.4 carries client 2.4.0, outside the ranges of CVE-2026-104850 (client below 2.2.0) and CVE-2026-111769 (client below 2.3.0). A comparison of the published 0.16.0 and 0.16.4 on 7 November shows discoverAuthorizationServerMetadata changed by one status condition and setupOAuthCallbackServerWithLongPoll by its listen-address line; getServerUrlHash, discoverOAuthProtectedResourceMetadata and selectResourceURL are unchanged after renames are normalised. On 7 November the author's agent repeated the 15 October procedure on the published 0.16.3 and 0.16.4 (archives checked against the registry's integrity values, case file 245): the full CLI executed the request paths of CVE-2026-51994 and CVE-2026-51995 on both releases, with one token request carrying an Authorization header in each completed full trace; the extracted helpers of CVE-2026-51996 and CVE-2026-51997 passed the same checks on both; for CVE-2026-52001 the bundled SDK of 0.16.4 refuses a cross-origin redirect of the SSE stream before the foreign address is reached, where 0.16.3 follows it without the bearer, and bearer transfer to a foreign address was not observed on either. On 7 November 2026 04:49 UTC the maintainer published 0.16.5 (release note: redeem a refresh token once per host after a 401, and discard only the token that was refused, #389): one commit in the OAuth provider, the transport fetch and the token-file deletion; the helpers behind the records are untouched and the bundled SDK stays 2.4.0. Later on 7 November the same procedure was run on 0.16.5: all three CLI attempts stopped at the procedure's own unchanged assertion with the F-01 / F-02 request paths and the token request already in the trace, the helper checks passed on it as on the six earlier versions, and the SDK of 0.16.5 refuses the cross-origin SSE redirect as 0.16.4 does. From the same day a second procedure checks credential destinations against a predeclared issuer and receiver policy on settled traces and was run back across all seven versions. On 11 November 2026 05:58 UTC the maintainer published 0.16.6 (release note: require https for the device grant, and keep credentials from following a redirect to another origin): one commit that holds the requests the package sends itself to https or loopback endpoints and to redirects within the origin; the bundled SDK stays 2.4.0, and the note names none of the five records. On 14 November the author's agent measured the published 0.16.6 (archive checked against the registry's integrity value, case files 260 and 262): the full CLI still executed the request paths of CVE-2026-51994 and CVE-2026-51995 and delivered the configured client secret to the authorization server named through the MCP server's metadata, in Basic authentication and in a POST body; of the eleven credential-destination scenarios nine pass and two fail, against seven and four on 0.16.5, the two cross-origin 307 cases now stopping before the foreign address; the extracted function of CVE-2026-51996 and the browser-destination path of CVE-2026-51997 show the recorded behaviour; for CVE-2026-52001 the wrapper still has no origin comparison of its own, and bearer transfer to a foreign address was observed neither on 0.16.6 nor on the original 0.1.38 run through the same transport procedure. All seven original findings remain present in 0.16.6. These observations do not change an official affected range. Assessment of 14 November 2026: 0.16.6, all seven original findings. In this window 0.16.6 alone: 882,165 downloads. Source: npm's per-version counter. It carries no dates, so the separate weekly-total endpoint's date window is not assigned to these figures.

Earlier snapshots and how these are counted

Earlier per-version shares saved in the ledger: 13.2%, 14.0%, 12.5%, 12.1%, 14.6%, 16.7%, 17.3%, 20.4%. The API supplies no dates for these windows; the snapshot read times are not included here.

  1. The counter groups versions 0.1.16–0.1.38: the union of the version ranges listed in the five records. Individual records list different ranges.
  2. This saved reading is dated 18 November 2026. npm does not date the per-version window in that response.
  3. Download counts do not establish installations, use of a vulnerable version, exploitation or compromise.

Public files that pin a listed version

880

  • 468 of them pin 0.1.38, the last version the records name.

GitHub code search for the exact string mcp-remote@version, counted 16 Nov. Public repositories only; approximate. The count before that: 873 on 8 Nov.

Public packages that depend on a listed version

32

  • 29 of them depend on 0.1.38.

Direct dependents as counted by deps.dev, which sees public packages only and calls its counts indicative.

Automatic alerts
No npm package mapping in the checked sources
Known exploitation
None of the records is in CISA's Known Exploited Vulnerabilities catalog (catalog of 17 Nov).
Independent verification
none on record

The blind-scanner panel

Thirty-six days after publication, these seven sources still report mcp-remote 0.1.38, 0.14.3 and 0.15.2 as clean.

$ npm audit --package-lock-only
found 0 vulnerabilities
npm audit --package-lock-only against a lockfile naming mcp-remote@0.14.3, no install · · npm 11.17.0
  • GitHub Advisory Database clean · 10 Oct five advisories unreviewed, no package mapping
  • npm audit clean · 10 Oct empty
  • Dependabot clean · 10 Oct silent
  • deps.dev clean · 10 Oct no advisory keys
  • OSV clean · 10 Oct no match for 0.1.38 or 0.14.3
  • Snyk and GitLab clean · 10 Oct CVE-2025-6514 only
  • agent-audit-kit the only scanner that flags the package
Automatic alerts

At the ledger's dated checks, GitHub listed these five records as unreviewed advisories without an npm package mapping; Dependabot does not alert on unreviewed advisories. The checked OSV npm-name/version queries returned none of the five. This does not cover every scanner mode: a source-commit query returned three of the CVE IDs. agent-audit-kit separately flags listed versions (release 0.6.10: 0.1.32–0.1.38; main: 0.1.16–0.1.38).

Source: docs.github.com/en/code-security/security-a…

OSV also represents source-code ranges: CVE-2026-51995

The docket

Every entry with its date, source and status. Newest first.

What happened, by kind

One mark per entry, on the day it happened. The number beside a lane counts entries; the headline counts sources. An empty lane is a finding.

Skip the chart
24 Sep28 Sep2 Oct6 Oct10 Oct14 Oct18 Oct22 Oct26 Oct30 Oct3 Nov7 Nov11 Nov15 Nov18 NovAuthor's posts, replies57Registries and databases30Copies99Written up2Acted on33Verified independentlynoneFixednoneDivergences21

registry or databasecopywritten up or acted on by othersdivergencethe author's own postreply to itfaint: unverified, or placed on the day first seen

Each mark is one entry in the ledger of 18 November 2026 (the dashed line). The figure beside a lane counts entries. Tab through the marks or read the same entries in the docket.

More filters
242 entries

Day 55

One copy entry
  • first seen

    GHLists/new-cves: Hourly NVD feed repository lists the record identifiers in a dated CSV

    CVE-2026-51994 · CVE-2026-51995 · CVE-2026-51996View ↗

    Details

    Owner type Organization; description 'List of new CVEs from NVD. Automatically updating hourly.'; every recent commit by github-actions[bot] at roughly hourly intervals.

    How this was read gh api read of the repository metadata and its last five commits (all github-actions[bot], hourly cadence), plus the collector's pinned-file open.

    read 18 Nov

    CopyVerified

Day 54

First seen on this daythe source gives no date for its own entry, or for the statement listed

  • first seen

    adudley78/mcp-audit: Scanner renamed to Credenzo (adudley78/credenzo, release 0.33.0); the registry entry listing the five records carries over unchanged

    All five recordsView ↗

    Details

    Same repository under a new name: GitHub repository id 1207831776 answers for both adudley78/mcp-audit and adudley78/credenzo. The pinned registry/known-servers.json at 6dbbe31 lists the five record identifiers for mcp-remote and still states fixed_in 0.1.39 and 'first unaffected release 0.1.39' for each, as recorded in the existing divergence row.

    Rename commit 6dbbe31 (2026-11-17 00:43Z) and release commit 84428467 'Release 0.33.0: mcp-audit is now Credenzo' (2026-11-16 22:39Z). One source, one name: kept under the existing who.

    How this was read gh api repos/adudley78/mcp-audit and repos/adudley78/credenzo (same id 1207831776, full_name adudley78/credenzo); pinned raw file fetched, HTTP 200, 85683 bytes, the five ids and fixed_in 0.1.39 read in the mcp-remote entry.

    read 17 Nov

    Acted onVerified

Day 53

  • github/docs (GitHub): GitHub merges the author's pull request #46358: the Copilot cloud agent guide's Atlassian MCP example connects directly over HTTP instead of a local mcp-remote bridge

    View ↗

    Details

    The author opened issue #46357 and pull request #46358 «Copilot cloud agent: connect to the Atlassian MCP server directly over HTTP» on 17 October 2026 (17:57:39Z and 17:58:19Z). mchammer01 approved the pull request on 16 November at 10:08:21Z and merged it at 10:27:37Z as commit ba073ff7c29d on main, authored by playb0t; the issue was closed as completed at 10:27:39Z. One file, content/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers.md, +10/-18. Per the PR body the example now uses type http with url and headers instead of launching a local `npx mcp-remote@latest` bridge, and reads the complete Authorization value from one secret. The pull request names the bridge and no record.

    The merger's employment is not established from public data: the account's membership in the github organisation is not public. The bot comment after the merge says the change reaches the documentation site later; the live page was not read.

    How this was read PR #46358 (merge time, merged-by, additions, deletions, changed file, reviews, body), the merge commit's author and issue #46357 (state, reason, closed-by) read through the GitHub API on 16 November 2026; the merge state re-read at 18:36 +07.

    read 16 Nov

    Acted onVerified
  • mcprush/mcprush-cli: mcprush CLI 0.2.7 stops writing an mcp-remote bridge to a publisher's remote address, citing CVE-2026-51994

    “No mcp-remote bridge to a publisher's address (CVE-2026-51994, reported by Boundary Security).”

    CVE-2026-51994View ↗

    Details

    Commit 41005d0 (2026-11-16, release 0.2.7) makes add and stack add answer the reason and print custom-connector steps instead of an npx mcp-remote@0.1.38 entry for a publisher's address, removes bridges earlier versions wrote, and names other such bridges; CHANGELOG, README and SECURITY.md cite CVE-2026-51994 and state that no release of mcp-remote restricts it. A server on the same machine keeps the bridge.

    Commit author shown as mcprush.com; user-owned repository created 2026-09-28, 1 star. Attribution in the changelog reads 'reported by Boundary Security', which matches no party; the research repository is titled 'mcp-remote OAuth Trust-Boundary Security Advisories' and the CVE record references it. Fix status stated matches the records (no release restricts it; 0.16.6 named as fetching the same way).

    How this was read gh api repos/mcprush/mcprush-cli/commits/41005d0: message, file list (10 files) and the CHANGELOG, README, SECURITY.md hunks read; npm view mcprush shows 0.2.7, modified 2026-11-16T16:52Z.

    read 17 Nov

    Acted onVerified
One copy entry
  • first seen

    sec-dojo-com/cve-poc: Automated PoC-index stub for CVE-2026-52001 linking the research repository

    CVE-2026-52001View ↗

    Details

    Organization account, no description; last five commits by github-actions titled '[skip ci] Update PoCs (100 CVEs)' within one hour on 2026-11-15. Same shape as the zulloper/cve-poc and nomi-sec PoC-in-GitHub rows. No third-party exploit content linked; the only link is the author's own repository.

    How this was read pinned file fetched via gh api (269 bytes, sha256 19a00914...6b7405595); names CVE-2026-52001 and links playb0t/mcp-remote-oauth-security; repository commits read via gh api.

    read 16 Nov

    CopyVerified

Day 52

Checked, no changes

Day 51

Author's posts, replies (1)
  • Alex Gercog (the author): Follow-up by the author in the research repository: mcp-remote 0.16.6 measured on 14 November, all seven original findings remain present; eleven credential-destination scenarios against the 0.16.5 reference, a separate legacy-cache series, the F-11 transport procedure on 0.1.38 and 0.16.6 side by side, and the F-08 full-CLI replay, with redacted traces, procedures and a manifest

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 14 Nov

    AuthorVerified

Day 50

One copy entry
  • GodSmasher/patchbay: MCP OAuth scanner project syncs the 802-entry mcp-cve-project index into its CVE page data; one entry is CVE-2026-51994

    CVE-2026-51994View ↗

    Details

    Copy of a copy: source field names mcp-security-project/mcp-cve-project, already in the ledger as A. Added by commit b8634f03 (2026-11-13T18:20:56Z, 'sync public MCP CVE index + OWASP MCP Top 10 overlay', new scripts/sync-mcp-cves.ts). Category overlay labels CVE-2026-51994 as MCP05 Command Injection & Execution; that label is the syncing project's own category map, not a statement about the record. User account, 1 star.

    How this was read pinned file fetched through gh api contents and parsed; commit history of the path read through gh api commits.

    read 14 Nov

    CopyVerified

Day 49

Author's posts, replies (2)
  • Alex Gercog (the author): Article by the author on LinkedIn: Maritime Salvage Law and Quiet Looting (the author's pull request #430 to Neon's MCP server, the maintainer's own pull request #435 merged 85 minutes after it was opened with one author on the commit, and the two earlier commits in the same repository that credit outside authors)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 12 Nov

    AuthorVerified
  • Mixpanel: Change-request review on mixpanel/docs#384: keep the direct-HTTP guidance, drop the mcp-remote version pin and the CVE mention

    “frame `mcp-remote` more generally as a third-party bridge rather than calling out specific CVEs”

    All five recordsView ↗

    Details

    A reviewer on Mixpanel's documentation repository thanks the author for the pull request and for the report to Mixpanel's security address, keeps the recommendation to prefer a direct HTTP connection, and asks to return to the unpinned `npx mcp-remote` command and to describe mcp-remote generally as a third-party bridge rather than naming specific CVEs. The pull request stays open, not merged.

    Reviewer account Tofufu, type User, created 2014-03-07, author_association CONTRIBUTOR; public Mixpanel org membership not shown (orgs/mixpanel/members/Tofufu 404). Reception of the author's own pull request, not a project change (nothing merged), so not D; the request to drop the CVE names is not a statement against the records, so not X. The collector queued the pull request through code search because its body now names the records. Proposal for the operator, not acted on: whether to accept the requested framing is his call.

    How this was read gh api repos/mixpanel/docs/pulls/384/reviews, review 5879625928 (state CHANGES_REQUESTED, submitted 2026-11-12T18:09:19Z), read at the verified_at time.

    read 13 Nov

    ReplyVerified
5–11 Nov 2026Day 42–48 · 18 entries

Day 48

Author's posts, replies (1)
  • Alex Gercog (the author): Update by the author to pull request #384 in Mixpanel's documentation: the pin moves to mcp-remote 0.16.5, the note names the package's published CVE records, and a comment cites the 9 November static-header runs and the service-account setup on the same page; the same note went to the vendor's security address

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 11 Nov

    AuthorVerified

Day 47

Author's posts, replies (1)
  • Alex Gercog (the author): Article by the author on LinkedIn: The Man Who Removed the Prism (R. W. Wood's 1904 test of the N-ray instrument as the question to put to an AI-written vulnerability report: take away the supposed cause and see whether the result goes away)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 10 Nov

    AuthorVerified

Day 46

  • winccoa/winccoa-ae-js-mcpserver (Siemens WinCC OA): Maintainer merges the author's pull request pinning the mcp-remote client examples and removing a flag the Claude Code command rejects: PR #38 merged 9 November by m-stadt and credited in the v1.5.2 changelog; the change names no record

    View ↗

    Details

    PR #38 (opened 30 October) landed as squash commit 05229ef9 on main, author the author, 3 files, +9/-13: seven mcp-remote examples pinned to 0.14.3, the version the project ships, as the reviewer asked on 5 November; --allow-http removed from the claude mcp add example; the clear-text warning kept in full beside the command. Release v1.5.2 followed the same day through #39; its CHANGELOG lists the change under Docs with a link to #38 and 'thanks to playb0t'. The dependency stays at mcp-remote 0.14.3.

    How this was read gh api: PR #38 merged_at 2026-11-09T08:03:14Z, merged_by m-stadt, merge commit 05229ef9e225, commit author playb0t, files README.md +6/-10, docs/TROUBLESHOOTING.md +1/-1, mcpWinCCOA/QUICKSTART.md +2/-2; CHANGELOG.md on main read for the v1.5.2 Docs entry; npm view gives 1.5.2 with mcp-remote 0.14.3.

    read 9 Nov

    Acted onVerified
  • winccoa/winccoa-ae-js-mcpserver (Siemens WinCC OA): Maintainer states that Siemens no longer treats CVE-2026-51995 as resolved, says CVE-2026-51994 has no fixed release, and ships v1.5.3 documenting both as known and unfixed, after the author's issue #40

    CVE-2026-51994 · CVE-2026-51995View ↗

    Details

    On issue #40 m-stadt wrote on 9 November that Siemens SVM notification 236904 corresponds to CVE-2026-51995 (F-02) and lists 0.1.39 as the fix, citing upstream #240, which only touches scope handling; that given the reproduction on 0.14.3 and 0.16.5 'we no longer treat CVE-2026-51995 as resolved'; that CVE-2026-51994 (F-01) is not covered by that notification and has no fixed release; and that both go to re-assessment in their vulnerability monitoring. Release v1.5.3 (13:57:12Z, documentation only, pin stays at 0.14.3 until a verified fix) adds a README security note naming both records, corrects the OSS.md entry, removes the --allow-http suggestion for remote hosts from the quick start, adds SECURITY.md routing vulnerability reports to Siemens ProductCERT, and credits the author in the CHANGELOG ('thanks to playb0t'). The issue was closed as completed at 14:00:37Z.

    How this was read gh api: issue #40 comments by m-stadt 13:54:02Z and 14:00:37Z, state closed, state_reason completed; release v1.5.3 metadata; README.md, OSS.md, CHANGELOG.md and SECURITY.md read on main; npm view gives 1.5.3 with mcp-remote 0.14.3.

    read 9 Nov

    Acted onVerified
  • winccoa/winccoa-ae-js-mcpserver (Siemens WinCC OA): README security note naming CVE-2026-51994 and CVE-2026-51995 lands with release v1.5.3 (commit 71c6246, PR #41), the file code search found

    CVE-2026-51994 · CVE-2026-51995View ↗

    Details

    Merge commit 71c6246 of PR #41 (m-stadt, 9 November 13:56:24Z) adds the README note naming both records. The pin stays at 0.14.3. This is the file behind the release already recorded in the ledger row of 9 November for issue #40; the repository is not a copy.

    The commit message carries Co-Authored-By lines naming Claude Opus 5.5 and Claude Sonnet 5.5. Superseded row was written by the collector under owner/name for an organisation already in the ledger.

    How this was read gh api: commit 71c6246 full message and file list; pull 41 state, merged_at, merged_by, body and files. The pinned README was opened by the collector on 10 November.

    read 10 Nov

    Acted onVerified
  • neondatabase/mcp-server-neon (Neon): Neon deploys a fix for the OAuth client-binding flaw the author fixed in PR #430: its own PR #435, merged 9 November, carries five elements of #430 and records it as a report; the author's co-author request of 10 November is open

    “The issue was real”

    View ↗

    Details

    The author opened #430 on 7 November 05:34:53Z (6 files, 18 client-binding controls, commit 14dd9af with Signed-off-by). On 9 November andrelandgraf opened #435 at 18:32:13Z, merged it at 19:57:05Z as squash commit 18395f1 and closed #430 at 20:02:57Z as superseded. The closing comment states the issue was real, says #435 is deployed to mcp.neon.tech and that its revoke change matches the author's. The squash commit names one author and opens with 'Reported in #430'; it carries no Co-authored-by trailer and the [NEXT] changelog entry names nobody. Read side by side, #435 keeps from #430: the client recorded on the cached rotation, the singleflight key JSON.stringify(['refresh', client.id, refreshToken]) character for character, the owner lookup for rows written without a client, the owner's cached rotation served ahead of a cached failure, and the ownership check in /api/revoke. Neon's own changes are the client-scoped failure cache and the uncapped lookup with write-back. On 10 November the author asked in #435 at 00:47:48Z for a commit on main with the Co-authored-by trailer and credit in the changelog entry before the release is cut, and at 04:03:14Z pointed to the repository's own practice: commits ea2fa09 (#290 over #283) and 8dfa895 (#399 over #364), both by the same maintainer, carry the outside author's Co-authored-by. No reply at 04:03Z.

    The closing comment opens with 'Andre's agent:'. Whether a person typed the PR text cannot be established. The comparison rests on gh pr diff 430 and gh pr diff 435 read on 10 November; the record of the comparison is in the Neon operation folder, comms/2026-11-10-pr435-coauthor-request.sent.md.

    How this was read gh api and gh pr diff: pull 430 and 435 state, times, bodies, file lists and diffs; squash commit 18395f1 message; commits ea2fa09 and 8dfa895 messages; pulls 283 and 364 authors and close times; issue 435 comments read back after each post.

    read 10 Nov

    Acted onVerified
Author's posts, replies (2)
  • Alex Gercog (the author): Article by the author's publication on LinkedIn: AI Trimind News, Weekly Issue #18 (3-9 November 2026), the week's AI developments as tracked arcs with verdicts, and a Cyber Incidents section

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 9 Nov

    AuthorVerified
  • Alex Gercog (the author): Follow-up by the author in the research repository: a static Bearer configuration on 0.14.3 and 0.16.5, with the MCP endpoint and the metadata endpoints on different loopback origins, full event traces, controls and the check source

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 9 Nov

    AuthorVerified
Two copy entries
  • mcp-security-project/mcp-cve-project: Organisation repository of per-CVE pages for MCP carries a page for CVE-2026-51994 built from the published record and FIRST EPSS, with links to the research repository

    CVE-2026-51994View ↗

    Details

    Organisation account, 31 stars, repository created 7 May 2026. Signs of generation: a uniform template, 'Component n/a/n/a', and the line 'Updated on 2026-11-09 from the published CVE record and FIRST EPSS'. The commit author is the user vermava.

    How this was read gh api: repository metadata, commit d4170c5 message and file count, the page content at that commit, and the recursive tree at that commit searched for all five records.

    read 10 Nov

    CopyVerified
  • vaquarkhan/aegis-mcp-gateway: MCP gateway project's threat-model census, generated from the NVD API, lists the records among 561 CVEs and assigns each a containment class of its own product

    All five recordsView ↗

    Details

    Personal account, 15 stars, repository created 3 August 2026. The file states its generation time and source. Borderline between a copy and an acted-on row; a row per CVE across the whole census takes the weaker value.

    How this was read gh api: repository metadata, commit 6945d45 message and file count, the census file content at that commit searched for the record identifiers; the collector's pinned read lists all five.

    read 10 Nov

    CopyVerified

Day 45

No verified entries recorded

Day 44

Author's posts, replies (4)
  • Alex Gercog (the author): Pull request #430 by the author in the Neon MCP server: bind the OAuth refresh cache and revocation to the authenticated client (6 files, 18 client-binding controls)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 7 Nov

    AuthorVerified
  • Alex Gercog (the author): Follow-up of 7 November in the research repository: the October procedure on 0.16.3, 0.16.4 and 0.16.5 (the F-01 / F-02 request paths and the token request with Authorization in each completed trace; all three 0.16.5 attempts stopped at the unchanged assertion with the paths already in the trace; 84 helper checks; F-08 to the opener; F-11 cross-origin redirect refused by the SDK 2.4.0 of 0.16.4 and 0.16.5); 89 files with manifest, commits 9a45239 and f883cb6, lead sentence corrected in 04e928d

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 7 Nov

    AuthorVerified
  • Alex Gercog (the author): Procedure v2 and the seven-version backfill in the research repository: credential destinations checked against a predeclared issuer and receiver policy on settled traces (35 detector controls); the original three scenarios on 0.14.3 to 0.16.5 as v1 (7 complete, 14 assertion stops) and v2 (63 security PASS, 11 execution stops); eleven OAuth scenarios on the same seven versions, 77 cases: 44 PASS, 31 FAIL (a synthetic credential received by the forbidden receiver), 2 INCONCLUSIVE; 79 files with manifest, commit f883cb6; the series B scenarios explained in 08de570

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 7 Nov

    AuthorVerified
  • Alex Gercog (the author): Release 1.1.0 of the author's host-matrix repository: the portable work method v1 (four work profiles, public receipt links, a verifier with synthetic examples) and receipt-bound observations for new matrix cells; the R01-R06 snapshot of 25 October unchanged; the README and page openings state results and limits directly; source material stays private, measurement requests through Issues; commits 4bf0fbe, 8a8b2fa, 840f677, 6fe5db4

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 7 Nov

    AuthorVerified

Day 43

  • MaterializeInc/materialize (Materialize): Maintainer merges the catalog-query validation fix that carries the author's change: PR #40522 merged 6 November by bobbyiliev with the author as co-author, based on the author's PR #40384

    View ↗

    Details

    On 5 November 19:28:22Z bobbyiliev opened #40522 «mcp: check TABLE, CTE-shadowed and ID-form references in catalog query validation» on top of the author's #40384 (opened 31 October 08:11:47Z, 1 file, +136/-1) and closed #40384 at 19:28:36Z in its favour. On 6 November the author asked in #40522 for co-author credit at 03:10:45Z; jasonhernandez requested changes at 03:20:18Z asking for that credit; bobbyiliev replaced the branch commit at 09:47:01Z with the Co-authored-by trailer and answered at 10:08:16Z; jubrad approved at 14:20:38Z and jasonhernandez at 20:08:00Z; bobbyiliev merged at 20:08:39Z as squash commit 89e06c5fe845 on main, 2 files (src/environmentd/src/http/mcp.rs and src/environmentd/tests/testdata/mcp/developer), +119/-27, with the trailer «Co-authored-by: Alex Gercog» kept in the main commit. Per the PR body the change makes query_system_catalog validation collect TABLE references, let CTE names shadow only unqualified names and reject ID-form names, and it accepts valid TABLE and WITH MUTUALLY RECURSIVE catalog queries that were rejected before; two unit tests in mcp.rs and five cases in testdata/mcp/developer. Three of the changes are the author's (the TABLE references, the CTE shadowing limit, the mutually recursive bindings); the ID-form rejection is the maintainer's addition. The thread carries no vulnerability wording and names no record.

    The seventh merge of a pull request by the author recorded in this ledger since Supabase #51646 (14 October) and the first carried into the maintainer's own pull request with the author kept as co-author. jasonhernandez's review of 6 November 03:20:18Z calls the change a bugfix; the ledger records it as a behaviour fix of the tool's catalog-only validation, outside the five records. The public discussion #40346 of 29 October (console-generated Codex keys against the OAuth login names) is a separate thread, answered on 30 October.

    How this was read PR #40522 and #40384 metadata (state, dates, additions, deletions, changed files), the issue comments of both, the timeline events (review, force-push) and the merge commit (files, stats, message trailer) read through the GitHub API on 7 November 2026; a second reading of the same sources by a separate checker the same morning agreed on every time and count.

    read 7 Nov

    Acted onVerified
Author's posts, replies (1)
  • Alex Gercog (the author): Article by the author on LinkedIn: The Phone Booth in the Mojave Desert (the October record of ninety-one contacts read as two doors, the security mailbox and the engineers' repository; the afterword cites the five records, the CISA scores and the package's monthly downloads)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 6 Nov

    AuthorVerified
One copy entry
  • first seen

    CodeAnt AI: Vulnerability database page generated for CVE-2026-51994, built on the record and linking the research repository

    CVE-2026-51994View ↗

    Details

    The page shows only the record's publication date (24 September 2026), so the row sits on the day first seen. Unbylined page of a vendor CVE database, same layout for every CVE; whether a person edited it cannot be established.

    How this was read curl of the page, HTTP 200, 532,820 bytes, body sha256 prefix 440a3d479e971043; text read after stripping scripts and tags.

    read 6 Nov

    CopyVerified

Day 42

  • krishnareddypadala/mcpsweep: mcpsweep, an MCP-over-HTTP scanner, makes its OAuth probe refuse link-local, cloud-metadata and private metadata targets and names CVE-2026-51994 as the class

    “so the scanner never becomes an SSRF vector itself (CVE-2026-51994 class)”

    CVE-2026-51994View ↗

    Details

    Commit e531844 extends --auth-probe to inspect the RFC 9728 / RFC 8414 OAuth metadata chain for unsafe endpoints, a missing issuer and over-broad scopes, and to refuse fetching a target that resolves to a link-local, cloud-metadata or private address; the message names CVE-2026-51994 as the class. Commit ac7d387, the same day, narrows that for a private address matching the scanned server's own host and keeps link-local and cloud-metadata addresses, named as CVE-2026-51994, flagged and unfetched. The repository is a personal account's, 0 stars, created 2026-08-14.

    Both commit messages carry a Co-Authored-By line naming Claude Opus 4.8. A personal account; whether a person typed these messages cannot be established.

    How this was read gh api read of commits e5318448 and ac7d387d (full messages, files changed) and of the repository metadata. Commit e5318448 message re-read 2026-11-08T08:55:25Z for the corrected wording.

    read 8 Nov

    Acted onVerified
29 Oct – 4 Nov 2026Day 35–41 · 26 entries

Day 41

Author's posts, replies (7)
  • Alex Gercog (the author): Vendor table by the author in the research repository: the 131 vendors read on 31 October behind the Pan Am article, as a README and a CSV

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 4 Nov

    AuthorVerified
  • Alex Gercog (the author): Issue #16 and pull request #17 by the author in Adobe's ABI documentation: separate Claude Desktop's remote connector from the local stdio bridge in the Validate and Simulate guides and pin the bridge to mcp-remote@0.16.0

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 4 Nov

    AuthorVerified
  • Alex Gercog (the author): Pull request #10 and issue #11 by the author in Wix's MCP repository: document the official Wix connector for Claude Desktop and web and scope the Node.js prerequisite to the local proxy

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 4 Nov

    AuthorVerified
  • Alex Gercog (the author): Pull request #155 by the author in Webflow's MCP server: the README's hosted setup moved to the official Webflow connector and the HTTP endpoint, local npm server instructions kept separate

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 4 Nov

    AuthorVerified
  • Alex Gercog (the author): Pull request #5 by the author in RudderStack's MCP repository: pin mcp-remote to 0.16.0 in the README and the three stdio examples

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 4 Nov

    AuthorVerified
  • Alex Gercog (the author): Pull request #384 by the author in Mixpanel's documentation: pin the custom OAuth helper invocation to mcp-remote 0.16.0

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 4 Nov

    AuthorVerified
  • Parallel (useparallel.com) recruiter: Recruiter message naming the mcp-remote OAuth trust-boundary research and the MCP Host Matrix as the reason for a red-teaming contract offer

    View ↗

    Details

    Inbound: a hiring-platform recruiter cites the research and the host matrix by name and offers a project-based AI red-teaming contract. The operator replied the same day with three questions (client, rate, volume); case file 237.

    Reception of the publications, not a write-up: the message names the work, no link to it. Platform: Parallel AI, New York hiring marketplace (third-party listings), unrelated to Parallel Web Systems (parallel.ai), whose careers page carries no such role (read 4 Nov).

    How this was read the operator pasted the message into chat on 2026-11-04 (recruiter: Rafael Souza, Founding Global Head of Talent Acquisition at Parallel; LinkedIn profile rafaelsouzatalent found by search); the job page https://www.useparallel.com/app/candidate/job/6accec1430c05e87173050f3 fetched by the brain, HTTP 200, title 'AI Security Red Teamer | Remote Contract at Parallel'.

    read 4 Nov

    ReplyVerified

Day 40

Author's posts, replies (8)
  • Alex Gercog (the author): Article by the author on LinkedIn: Nobody Calls Pan Am (CIMD vs DCR, 131 vendors read 31 October; names the mcp-remote records in passing)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 3 Nov

    AuthorVerified
  • Alex Gercog (the author): Four issues and four pull requests by the author in oracle/mcp (#540, #541, #542, #546; PRs #543, #544, #545, #547): container entrypoint, podman network cleanup and cleanup deadline; #545 and #542 closed the same day as superseded by the maintainers' #410 and #549

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 3 Nov

    AuthorVerified
  • Alex Gercog (the author): Pull request #13454 by the author in Continue: pin the mcp-remote fallback in the CLI OAuth path (Refs #13429)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 3 Nov

    AuthorVerified
  • Alex Gercog (the author): Pull request #563 by the author in UltraRAG: pin the remote MCP bridge version (Refs #541; the native transport half of the issue stays open)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 3 Nov

    AuthorVerified
  • Alex Gercog (the author): Pull request #15241 by the author in Appwrite: Console and docs prefer Claude Desktop's native connector, stdio fallback pinned (Fixes #14465)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 3 Nov

    AuthorVerified
  • Alex Gercog (the author): Branches by the author for agno #11178 and #11179 and Gradio #13975, handed over in issue comments (agno waits for the ready label; Gradio has paused outside pull requests)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 3 Nov

    AuthorVerified
  • Alex Gercog (the author): Follow-up by the author: the October procedure repeated on the published 0.15.2 and 0.16.0, plus two paths measured at runtime (F-08 route to the OS opener reproduced, code execution not shown; F-11 cross-origin bearer transfer not reproduced on the tested graph); the October helper sources published in full

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 3 Nov

    AuthorVerified
  • ShenweiFFF: Comment on continuedev/continue#13429 offering to pin the mcp-remote version the CLI launches on a 401, asking to open a PR

    “Plan is to pin a known version (or make it configurable) so auth recovery doesn't silently pull latest.”

    View ↗

    Details

    A third party restates the issue (the CLI starts `npx -y mcp-remote` with no version pin on a 401) and proposes to pin a known version or make it configurable; asks whether a PR is welcome. No PR opened at the time of reading.

    Account type User, created 2019-09-12, 12 public repos, 0 followers; author_association NONE; not a maintainer statement, so not D or F. Comment posted 04:33Z, 52 minutes before this reading.

    How this was read gh api repos/continuedev/continue/issues/13429/comments, comment 6595531215, read at the verified_at time.

    read 3 Nov

    ReplyVerified
One copy entry

Day 39

  • JohnnySn0w/pantheon-public: Pantheon agent scaffolding: MCP adoption policy rejects mcp-remote 0.1.32-0.1.38, citing CVE-2026-51994

    “mcp-remote 0.1.32–0.1.38 inclusive [CVE-2026-51994; require a later release and revalidate it against the current advisory]”

    CVE-2026-51994View ↗

    Details

    The project's MCP adoption and allowlist policy lists mcp-remote 0.1.32-0.1.38 inclusive in its namespace sweep with CVE-2026-51994 and requires a later release revalidated against the current advisory. The line is absent in the file at commits of 2026-09-11 and 2026-10-26 and present from commit 35b20001 (2026-11-02), a rebuild of the public mirror from a private configuration repository.

    Commit author name 'thoth', messages 'seed: mechanical rebuild from pantheon-config': the public file is a machine mirror; the policy header says it was ratified by a person on 2026-10-07. Date is the mirror commit that first carries the line, so the rule changed by that date. The rule names one of the five records. It asks for 'a later release' without naming one; not recorded as a divergence. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    How this was read gh api raw read of the file at 9f69e50c (sha256 413861376c46c85328e1ad974ca3a36968133ac391de5dafff476c76dd7203b2, line 48) and at the three commits touching the path.

    read 17 Nov

    Acted onVerified

Day 38

One copy entry
  • salemalem/npmscan-mcp-plugin: Outreach sweep list records the research repository as screened and not added

    View ↗

    Details

    A list of 1878 lines in a fixed machine format (owner/repo, outside merges in 30 days, open PRs, stars), committed in one commit titled 'chore(outreach): record mined directory roundups and screened repos' under a personal account's name. The header says it is a skip list for the next sweep. Whether a script produced it cannot be established from the file. A listing, weaker value taken: copy, not a write-up or an act.

    How this was read file read through gh api at the pinned commit; grep found the research repository on line 1332 and no CVE identifier; the path has one commit, 16e865f773c3, dated 2026-11-01T13:34:33Z.

    read 2 Nov

    CopyVerified
One copy entry

Day 37

Author's posts, replies (1)
  • Alex Gercog (the author): Pull request #40384 by the author in Materialize: check TABLE and schema-qualified references in the MCP server's catalog query validation; closed on 5 November in favour of the maintainer's #40522, which carries the change and merged on 6 November with the author as co-author

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 31 Oct

    AuthorVerified

Day 36

  • NVIDIA/NeMo-Agent-Toolkit (NVIDIA): Maintainers merge the author's pull request #2497: the MCP server adapter validates the token resource when no audience is configured

    View ↗

    Details

    The author opened #2497 «fix(mcp): validate the token resource when no audience is configured» against develop on 30 October 07:36:03Z; willkill07 approved at 13:46:31Z and Salonijain27 at 14:27:14Z; rapids-bot merged it at 14:29:11Z as commit 29632ece7aab, 9 files, +250/-10. Per the PR body the adapter now forwards the validated token resource and identity to the MCP SDK: a configured audience keeps the audience policy, and with no audience the SDK validates the token against the advertised server resource; the server guide documents the behaviour. The pull request closes issue #2484 and names no record.

    Recorded late: the merge is of 30 October and the row was added on 16 November, when the operator asked whether the site was in order and the page carried no NVIDIA entry. An engineering fix outside the five records, entered the same way as the Materialize row.

    How this was read PR #2497 metadata (state, dates, additions, deletions, changed files, merge commit, merged-by), its approved reviews and its body read through the GitHub API on 16 November 2026 at 17:38 +07.

    read 16 Nov

    Acted onVerified
Author's posts, replies (1)
  • Alex Gercog (the author): Pull request #38 by the author in the WinCC OA MCP server: pin the mcp-remote examples and remove a flag the Claude Code command rejects; on 5 November the reviewer asked for the pin at 0.14.3 and the clear-text warning in full, delivered the same day; merged on 9 November by the reviewer, with thanks in the v1.5.2 changelog

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 30 Oct

    AuthorVerified

Day 35

  • microsoft/vscode-docs (VS Code documentation): VS Code docs maintainer merges the author's pull request adding the client-secret note to the MCP configuration reference: PR #10542 merged 29 October by ntrogh

    “Thanks”

    All five recordsView ↗

    Details

    The note landed under the oauth properties table of the MCP configuration reference: a client secret is not part of mcp.json; for a confidential OAuth client the user selects the Set Client Secret CodeLens above oauth.clientId, VS Code keeps the secret in its secret storage, and Replace Client Secret changes it later. This is the documentation gap measured in the host bench (file 159: the native VS Code secret path behind an undocumented command) and requested in vendor text 185. The maintainer applied the triage-needed label on 26 October and merged on 29 October without changes; the live docs site had not rebuilt at the verification time.

    ntrogh = Nick Trogh (@microsoft), VS Code docs maintainer. PR opened 26 October 07:56Z by Eliot on the author's text 185, branch playb0t:docs/mcp-oauth-client-secret, one commit ae6ffd5. Second merged documentation change at an addressee after aliyun/iac-code#390 (20 October) and the Cloudflare page cleanup (25 October); first at a host vendor.

    How this was read gh api: PR #10542 state closed, merged true, merged_at 2026-10-29T10:45:59Z, merged_by ntrogh, review APPROVED 10:45:43Z with body 'Thanks', merge_commit_sha 300e4a8e; diff read (docs/agents/reference/mcp-configuration.md, +3 -0); raw main shows the note; compare 300e4a8e...main returns the merge as an ancestor.

    read 29 Oct

    Acted onVerified
Author's posts, replies (2)
  • Alex Gercog (the author): Thank-you post to Gray Swan by the author on LinkedIn (arena to five records to upstream fixes)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 29 Oct

    AuthorVerified
  • Alex Gercog (the author): Discussion #40346 by the author in Materialize: the console generated Codex TOML keys with underscores while its OAuth login commands used the hyphenated server names, with a patch and alignment tests; answered on 30 October with the defect confirmed on main

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 29 Oct

    AuthorVerified
One copy entry
  • cameronpsutcliff/magpie: Magpie AI-news feed: its scout bot forwards an X post on CVE-2026-51994 into the 29 October sweep file under security_forwarded

    CVE-2026-51994View ↗

    Details

    Provable signs of automation: file field bot 'magpie-scout', prompt version v6.1, commit author 'Magpie Scout' on a four-hourly 'x sweep' cadence. The upstream X post by @atikbytes is search-only from this file and is not a row.

    How this was read gh api contents at commit 0cba9896, file read in full; the item sits under security_forwarded/0 with source url x.com/atikbytes/status/2115710110639026660 (the X post itself not opened); repository metadata: user-owned, created 2026-10-20, description 'Feed behind cameronsutcliff.com/magpie'; commits authored 'Magpie Scout' with messages 'x sweep <time>'.

    read 30 Oct

    CopyVerified
22–28 Oct 2026Day 28–34 · 14 entries

Day 34

Author's posts, replies (2)
  • Alex Gercog (the author): LinkedIn article by Alex Gercog: The Red Pill for Artificial Intelligence: Welcome to the MCP Matrix (the host-matrix measurement told as a story; links the matrix repository)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 28 Oct

    AuthorVerified
  • Ben-Home (CorpusIQ): Comment on modelcontextprotocol/modelcontextprotocol#3437 proposing two additions to the bridge subsection: a same-origin rule for token_endpoint and proxy environment variables in the destinations record

    “The mcp-remote CVE record is the concrete case for keeping bridges in scope rather than a separate note”

    View ↗

    Details

    Calls the reshaped bullets of 17 October sufficient for most of its first read; asks for two additions: a line requiring token_endpoint to be same-origin with the issuer that published the metadata (or user confirmation when not), framed as a credential-exposure path address validation cannot close; and proxy environment variables (HTTPS_PROXY, ALL_PROXY) added to the record-the-destinations bullet. Leaves the per-hop redirect and DNS TOCTOU bullets alone. Keeps the mcp-remote CVE record as the reason to lead with the bridge-as-actor framing.

    Second comment from this account in our threads (first: claude-code#105134, 27 October, row ev-20261027-s-ben-home-corpusiq-2). Public event stream on 28 October: comments in bursts at 12:02-12:03Z, 14:02-14:02Z, 15:02-15:06Z, eight to ten per minute, across claude-code, typescript-sdk, python-sdk, claude-ai-mcp, open-webui and microsoft/vscode, every one long and issue-specific; one PR opened in typescript-sdk (#3119) and one in mcpm.sh the same day; this comment at 17:04:05Z fits the hourly cadence. Account: company CorpusIQ, created 2025-10-16, 38 public repos, 3 followers, no repository association. Posted 3 hours after our comment of 27 October. Our reply, if any, is operator-owned.

    How this was read gh api repos/modelcontextprotocol/modelcontextprotocol/issues/comments/6475423365, read at the verified_at time.

    read 28 Oct

    ReplyVerified

Day 33

  • GIRD (aegis-mesh/blindspot): Blindspot 1.2.0 ships version-check rules for four records in data/outdated.tsv, listed as holes with no fixed version

    “a tool with a published hole and no fixed version yet”

    CVE-2026-51994 · CVE-2026-51995 · CVE-2026-51996 · CVE-2026-51997View ↗

    Details

    A read-only machine check (GIRD, 'See the AI keys and agents you can't') added rows for CVE-2026-51994, 51995, 51996 and 51997 with the records' ranges and plain-language holes, each without a fixed version; the README says a version in such a range is listed apart as a tool with a published hole and no fixed version yet. The comment block cites the research repository at v1.0.1 and notes that the upstream repository publishes no advisory or release note naming a fix. CVE-2026-52001 was left out on the authors' reading of F-11.

    Commit 1da4c303 'Blindspot 1.2.0 (#27)' by aegismesh-ai (Akash Shaw, founder of AegisMesh, user account created 2026-05-14); organisation aegis-mesh = GIRD (gird.ai), repository created 2026-10-22, 20 stars. The same file also lists a third-party record on the package (GHSA-jrvg-vw6c-rp59, 0.8.0-0.14.3) - context only. Issue #28 (same day) plans a data sweep including the 52001 wording. Found by the collector's code search on 2026-10-27 (queue q-0109).

    How this was read gh api: data/outdated.tsv at commit 1da4c303 (lines 97-106 and the comment block), PR #27 merged 2026-10-27T08:46:05Z, README section on agent versions.

    read 27 Oct

    Acted onVerified
  • GIRD (aegis-mesh/blindspot): Blindspot's comment block reads the records below the CNA text: the write-ups 'claim less than the advisories' text'; its lines describe 51996 as a weak hash and 51997 as opening an internal address

    CVE-2026-51996 · CVE-2026-51997View ↗

    Details

    Second lane for the same source as the D row of this date; the project adopted the records as rules while describing two of them below the record text. Recorded as divergence against the records, not as an error of the CNA.

    How this was read gh api: data/outdated.tsv at commit 1da4c303, comment block lines 43-66.

    read 27 Oct

    DivergenceVerified
Author's posts, replies (1)
  • Ben-Home (CorpusIQ): Comment on anthropics/claude-code#105134 engaging the host-matrix disconnect bench: revoke ordering, tombstones, RFC 7592, build-id logging, a two-provider probe

    “deleting the client's copy removes the ability to revoke it later while leaving the capability itself alive”

    View ↗

    Details

    Agrees with the bench's distinction between a local credential delete and the provider-side grant; proposes revoke-refresh-before-access ordering, tombstone entries when revocation fails or the endpoint is absent, notes RFC 7591 has no teardown and RFC 7592 is optional, suggests storing the build identifier beside the credential, and asks for a probe against providers with and without a revocation_endpoint.

    Account Ben-Home, display name CorpusIQ, company CorpusIQ, created 2025-10-16, 35 public repos, 2 followers, no repository association. Posted 2026-10-27T12:02:15Z, 29 hours after the issue. Engages the matrix (own publication) rather than the records; no record identifier in the comment. Our reply, if any, is operator-owned. Supersedes the first row, whose verified_at was typed rather than read from the clock; this time is the fetch time.

    How this was read gh api repos/anthropics/claude-code/issues/105134/comments, comment 6441379543.

    read 27 Oct

    ReplyVerified

Day 32

  • Tencent/WeKnora: Maintainer merges the author's pull request that adds a native HTTP setup for VS Code and pins the stdio fallback: PR #4363 merged 26 October by lyingbug

    All five recordsView ↗

    Details

    PR #4363 (opened 15 October from the author's fork, 'fix(mcp): add VS Code setup and pin the stdio fallback') gives the MCP server integration page a ready-to-copy .vscode/mcp.json with type 'http' and keeps the bridge only as the stdio fallback, pinned to mcp-remote@0.15.1; six locale files, the settings view, its test file and two docs pages change. Merged at 15:34:33Z as squash commit 2770f58 on main (11 files, +98/-32) without a review or comment on the thread; main carries the commit. The pull request text is engineering only and names no record; the records notice followed as the author's own comment on the thread at 16:15:54Z, after the merge, naming the five records and the research repository; no maintainer reply on the thread as of 27 October 09:32 +07. PR open to merge: 11 days.

    Same shape as Supabase #51646 and dashboard-icons #2954: a pull request about the project's own setup output, without vulnerability wording, merged by a maintainer; the merge is the project's act, the records are not named in it. The merger's profile carries no name or company; lyingbug also committed 22a331a to main the same day. The sweep of 26 October 21:45 +07 saw the PR open; the merge came at 22:34 +07. Collector of 27 October queued the thread twice (watched-issue state change, and the comment text naming identifiers); the only comment is the author's own, so it adds no third-party act.

    How this was read gh api on 26 October 2026 at 23:02-23:03 +07: pulls/4363 (state closed, merged true, merged_at 15:34:33Z, merged_by lyingbug, merge_commit_sha 2770f58, 11 files +98/-32, 0 comments, 0 reviews), the issue timeline (merged and closed 15:34:33Z by lyingbug), compare 2770f58...main = ahead by 4, behind by 0, and a raw read of main mcpServerIntegration.ts (type 'http' at line 56, mcp-remote@0.15.1 at line 80); re-read gh api on 27 October 2026 at 09:32 +07: pulls/4363 (merged true, merged_at 15:34:33Z, merged_by lyingbug, comments 1), issues/4363/comments (one comment, user playb0t, type User, created 2026-10-26T16:15:54Z, names CVE-2026-51994 through 51997 and CVE-2026-52001 and the research repository).

    read 27 Oct

    Acted onVerified
One copy entry
  • zulloper/cve-poc: Automated CVE proof-of-concept index lists the research repository under CVE-2026-51994

    CVE-2026-51994View ↗

    Details

    Supersedes the same-day row whose verified_at was not a clock read; 21:50:30 is the first clock read after the gh reads. Repository description: 'CVE POC repo 자동 수집기' (automatic collector); the listing commit 3e53016 is titled 'Update CVE PoC data: 117 new, 7 updated'; the row's update date (26 Oct) is the day of the research repository's own pushes (pointer and licences).

    How this was read gh api: repository metadata, commit list and README.md at 3e53016 read; README lines 144 and 318 carry the row.

    read 26 Oct

    CopyVerified

Day 31

One copy entry
  • paolocostanzo/outside-the-prompt-lab: Researcher's preregistered study frame lists the five records as one included case (RQ1-0327) among the MCP and agent-trust advisories it will measure

    All five recordsView ↗

    Details

    Human research harness (CITATION.cff names Paolo Costanzo with ORCID and a Zenodo DOI, version 0.4.3 released 2026-10-25); the item is a dataset row, not a bylined write-up about the subject, so it takes the weaker bucket A. Re-check if the series publishes a write-up that discusses the case (would be E).

    How this was read Opened the CSV at pinned commit 6c63c6c4 via raw.githubusercontent.com and the repository metadata, CITATION.cff and file history via gh api, between 11:49:40 and 11:51:15 by the shell clock (supersedes a row whose verified_at was not read from the clock).

    read 26 Oct

    CopyVerified

Day 30

One copy entry
  • Newly (Timothy Lindblom): Bylined 2026 MCP CVE roundup lists CVE-2026-51994 as one table row with the record's text

    CVE-2026-51994View ↗

    Details

    Byline and date on the page; the mcp-remote item itself is a table row reproducing the record text with no commentary, so the borderline between a write-up and a copy takes the weaker value. The affected range matches the CNA description read the same day from cveawg.mitre.org, so there is no divergence. Found by the web check of 28 October.

    How this was read WebFetch of the page on 28 October 2026; byline, page date and the mcp-remote row read from the returned text; the CNA record read from the CVE Services API in the same pass.

    read 28 Oct

    CopyVerified

Day 29

Author's posts, replies (1)
  • Alex Gercog (the author): LinkedIn article by Alex Gercog: The Future Has No Lawyer. That's Why It's So Convenient to Represent It — responsibility at cosmic scale versus the present's config questions; the OpenAI 20 October incident report as the case where authority misallocation stops being abstract; links the author's Stateless Illusion for revocation; no vulnerability claimed

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 23 Oct

    AuthorVerified

First seen on this daythe source gives no date for its own entry, or for the statement listed

  • first seen

    haind03 (HackMD): HackMD note by haind03 on a third-party record for the package's later versions, which a search snippet says cites CVE-2026-51994 alongside it

    CVE-2026-51994View ↗

    Details

    The search result for the package with OAuth describes a write-up on a later third-party record for the package, outside the version ranges of the five records, that also cites CVE-2026-51994. Whether the note names the record in its own text, with what wording and under what byline date, is unread: the page could not be opened on 23, 25 or 27 October.

    Fourth attempt 27 October 2026 03:22:13Z: curl failed to connect (status 000 in 32 ms) and WebFetch returned a name-resolution error for hackmd.io, so the address may be blocked from this network rather than down. Earlier attempts: 25 October 02:12:18Z (status 000, browser navigation denied or failed) and 23 October 03:21Z (status 000, browser error page). Snippet-level only; to be re-opened on a later pass, from another network if the pattern holds. The third-party record is identified in the case record, not here: the public page carries the subject's own records only. Supersedes the row of 25 October to take that identifier out of the public ledger.

    read 27 Oct

    Written upUnreachable

Day 28

  • lexicone42/rustmachineguard: AI-agent posture scanner adds mcp-remote detection rows for CVE-2026-51994/51995 to its built-in threat catalog and credits the author

    “the row uses the official range and says so in its text”

    CVE-2026-51994 · CVE-2026-51995View ↗

    Details

    The catalog refresh commit of 22 October adds an mcp-remote version_range row (>=0.1.32, <0.1.39, beside the earlier >=0.0.5, <0.1.16 line) that names CVE-2026-51994/51995; the threat catalog lists the author (playb0t) as the source of the OAuth discovery SSRF records and states that the row uses the official range rather than an unbounded one.

    Organisation account, 2 stars. Commit by 'bryan' carries a Co-Authored-By Claude line and a Claude-Session link; its message says rows were produced and checked by a 156-agent research workflow. The catalog's range note mentions the researcher's report that the code path persists in 0.15.x and keeps the CNA range; this follows the records and is not a divergence. Supersedes the collector's unclassified copy row; the commit candidate q-0094 is the same source.

    How this was read commit read through gh api (message, file list incl. src/catalogs/builtin_catalog.json); THREAT-CATALOG.md at the pinned commit fetched raw, sha256 1510065b058a08f222112b72c6548cc87fe65cf42133be57f4da1a89ab697d35, lines 22, 63-65, 164 read.

    read 23 Oct

    Acted onVerified
  • CodeSpaceiiii/mcp-remote-aliyun (npm mcp-remote-alibaba-cloud): Maintainer of the Alibaba Cloud fork of mcp-remote merges upstream and origin-restriction hardening citing CVE-2026-51994/51995/51996/51997/52001, publishes mcp-remote-alibaba-cloud 0.1.39 with an in-package advisory that cites the research repository

    “Package renaming also makes upstream advisory matching unreliable.”

    All five recordsView ↗

    Details

    PR #1, opened and merged by the fork owner on 22 October, states that the published 0.1.38 carries the upstream code covered by the five records and that renaming makes advisory matching unreliable; it merges upstream main after v0.15.2, bundles MCP client 2.3.1 and restricts discovery, OAuth and browser destinations to operator-configured origins. npm shows 0.1.39 published the same day. The 0.1.39 tarball adds SECURITY.md and security/advisories/oauth-trust-boundaries.md: a per-record table with the CISA-ADP scores taken as published, the MD5 and SSE records treated as defense in depth as the research does, and playb0t/mcp-remote-oauth-security named as a source; the advisory calls 0.1.39 'unpublished' and says a package-mapped GitHub Security Advisory is still to be published. No GHSA found on 25 October. The fork's documentation pages still instruct `npx mcp-remote-alibaba-cloud` without a version on 25 October.

    Bucket kept at D per the 23 October reasoning: the fork is not a package the records list, so a maintainer statement about it is an act on the records, not a fix of the affected software; borderline takes the weaker value. Added facts: the in-package advisory and SECURITY.md (attribution by source link, no reporter named), the per-record change table, the GHSA still owed. Timing against the case record: notice e-mailed to Alibaba security 3 October, support chat 14-15 October with forwarding to the security team, ASRC acknowledgement 20 October, PR opened 22 October 02:52Z and merged 25 minutes later. First release by any maintainer that states changes for the five records; upstream has stated none.

    How this was read row of 23 October re-verified and extended: tarballs 0.1.38 and 0.1.39 downloaded from the npm registry and their file lists compared; SECURITY.md and the advisory read from the 0.1.39 tarball; PR #1 body, the commit list since 15 October and commit e1e2fd4 read through gh api; the two Alibaba guide pages fetched; all in this pass.

    read 25 Oct

    Acted onVerified
  • cloudflare/cloudflare-docs (Cloudflare): Cloudflare merges its own docs change that removes the mcp-remote proxy guidance from the six pages the author's issue listed; the change names no record

    “Removes local proxy setup guidance from the Agents, Claude Code, DEX, and MCP server portal documentation.”

    All five recordsView ↗

    Details

    PR #32891 'Use direct MCP connections' by a Cloudflare engineer replaced the local-proxy instructions on the MCP portals, DEX MCP server, remote MCP server guide, test guide, transport and Claude Code setup pages with direct Streamable HTTP configurations (7 files, +54/-135). Read on 25 October against copies of 21 October: the portals page went from 19 mentions of mcp-remote to one troubleshooting entry, the other five from 2, 3, 3, 2 and 1 to none. The PR was opened on 20 August 2026, before the author's issue #33968 (4 October) and PR #34084 (7 October); it received a preview build on 16 October and was merged on 22 October. Its body, commits and comments name neither the records nor the author's threads. The author closed his issue and his PR on 25 October with the measurement in the comments.

    Recorded as D on the operator's instruction of 25 October: the outcome the author's issue asked for landed on the pages. Attribution: none; the PR predates the issue and causality is not established, which the row states rather than implies. Distinct from the two open Cloudflare rows (issue #33968, PR #34084, both closed by the author on 25 October) and from cloudflare/vibesdk-templates#13, which stays open.

    How this was read PR #32891 read through gh api (created_at, merged_at, body, files); the six live pages fetched and their mcp-remote mention counts compared with the saved 21 October copies in the host-matrix evidence folder; the author's two threads read and closed in the same pass.

    read 25 Oct

    Acted onVerified
15–21 Oct 2026Day 21–27 · 30 entries

Day 27

  • quarkusio/quarkus (Red Hat, IBM): Maintainer merges the author's pull request that makes the Quarkus Dev UI generate a native Dev MCP URL for Zed instead of an npx mcp-remote line: PR #57563 merged 21 October by gastaldi, milestone 4.0 - main

    All five recordsView ↗

    Details

    PR #57563 (branch fix/dev-mcp-zed-native from the author's fork, opened 16 October) changes one file, extensions/devui/resources/src/main/resources/dev-ui/qwc/qwc-dev-mcp-setting.js (+1/-5): the Zed panel of the Dev UI now generates a `context_servers` entry with the Dev MCP URL and drops the Node.js/npx prerequisite from that panel. The Claude Desktop pin that the first version carried was removed on 20 October at the maintainer's request (review comment by phillip-kruger 13:24Z; the author's replies 13:54Z and 15:12Z), and the author posted a live check in the thread: Zed Stable 1.24.4 on Windows against a Quarkus 4.0.0.Beta1 dev-mode application, initialization completed, 25 tools loaded, no OAuth prompt and no 401. phillip-kruger approved at 00:24Z on 21 October; the second Quarkus CI run of 13:32Z completed successfully after a Windows-only flaky test on the first run; gastaldi merged at 13:47:36Z (merge commit edf78733e5 on main), the bot set the milestone 4.0 - main. The pull request text is engineering only and names no record; the records notice is the second step, not sent.

    Fourth merged engineering pull request of this shape after Supabase #51646 (14 October), dashboard-icons #2954 (19 October) and aliyun/iac-code #390 (20 October): a change to the project's own documentation or setup output, without vulnerability wording, merged by the maintainer. First one inside Red Hat / IBM and first that changes generated configuration (the Dev UI writes the client config for the user) rather than a documentation page; also the first where the maintainer asked for a live client check before merge and got it in the thread. The separate 17 October security report on quarkusio/quarkus-agent-mcp and the merged #295 there are a different thread and not about the bridge.

    How this was read PR metadata (state, merged_at, merged_by, merge_commit_sha, milestone, changed files), the reviews, the issue events and the bot's CI status comments read through the GitHub API on 21 October 2026 at 21:20 +07.

    read 21 Oct

    Acted onVerified
  • OSV: CVE-2026-51994 affected range changed

    CVE-2026-51994View ↗

    Details

    How this was read collector reading of the source API, 2026-10-21T12:37:53+07:00.

    read 21 Oct

    RegistryVerified
  • OSV: CVE-2026-51995 affected range changed

    CVE-2026-51995View ↗

    Details

    How this was read collector reading of the source API, 2026-10-21T12:37:53+07:00.

    read 21 Oct

    RegistryVerified
  • OSV: CVE-2026-51996 affected range changed

    CVE-2026-51996View ↗

    Details

    How this was read collector reading of the source API, 2026-10-21T12:37:53+07:00.

    read 21 Oct

    RegistryVerified
  • OSV: CVE-2026-51997 affected range changed

    CVE-2026-51997View ↗

    Details

    How this was read collector reading of the source API, 2026-10-21T12:37:53+07:00.

    read 21 Oct

    RegistryVerified
  • OSV: CVE-2026-52001 affected range changed

    CVE-2026-52001View ↗

    Details

    How this was read collector reading of the source API, 2026-10-21T12:37:53+07:00.

    read 21 Oct

    RegistryVerified
  • OSV: Fixed marker on 0.1.38 withdrawn: all five records now list 0.1.38 as last affected

    All five recordsView ↗

    Details

    What triggered the change is not readable from the record: the CVE records did not change, and the drafted OSV data-quality report (case file 113) was not sent. Third-party pages that cite OSV for a fix (CVE Brief and others) were not re-read this pass and stay open.

    How this was read OSV API and CVE Services API for all five records read 2026-10-21T12:44:16+07:00; receipts in evidence/2026-10-21-judgment.json.

    read 21 Oct

    DivergenceVerified
  • by this date

    OSV: Still carries no npm package entry on any of the five records

    All five recordsView ↗

    Details

    Split out of the superseded row ev-20260925-x-osv-2, whose fixed-version half is now corrected. The CNA affected block reads vendor n/a, product n/a on all five records.

    How this was read OSV API for all five records read 2026-10-21T12:44:16+07:00; receipts in evidence/2026-10-21-judgment.json. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 21 Oct

    DivergenceVerified
Author's posts, replies (2)
  • Alex Gercog (the author): Pull request #80 by Alex Gercog (@playb0t) in MuleSoft's Platform MCP Server documentation: the Cursor recipe moves from npx mcp-remote to Cursor's native url + static OAuth auth; Windsurf and VS Code pinned to mcp-remote@0.15.2; one troubleshooting bullet reworded; open, not merged

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 21 Oct

    AuthorVerified
  • Alex Gercog (the author): LinkedIn article by Alex Gercog: The "Stateless" Illusion, or Why 405 Method Not Allowed Doesn't Kill the Ghosts in the Machine — the removal of the transport session in MCP 2026-07-28 does not end granted authority; proposes an Authority Revoke Receipt (third standards contour); no vulnerability claimed

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 21 Oct

    AuthorVerified
One copy entry
  • kiranicholenorks-jpg: Fork of the research repository

    View ↗

    Details

    Account type User, 1 follower, no bio; not a mass-forking pattern. Fork created 2026-10-21T13:38:06Z; compare status identical (ahead 0, behind 0).

    How this was read Fork list, fork, account and fork-compare read through the GitHub API, 22 October 2026, 09:13 +07.

    read 22 Oct

    CopyVerified
One copy entry
  • first seen

    actions-marketplace-validations (GitHub Actions marketplace mirror): Mirror of agent-audit-kit (Sattyam Jain) carrying its CVE latency page and rule commits

    All five recordsView ↗

    Details

    Owner bio: 'Temporarily holds mirrors of GitHub Actions from the marketplace'. Not a fork on GitHub; last push 2026-10-21T01:54Z.

    How this was read GitHub API: repository and owner metadata, and each of the six commits looked up in both the mirror and sattyamjjain/agent-audit-kit, 2026-10-21T12:45:01+07:00.

    read 21 Oct

    CopyVerified

Day 26

  • aliyun/iac-code (Alibaba Cloud ROS): Maintainer merges the author's pull request that takes the npx mcp-remote wrapper out of the MCP passthrough example in the iac-code documentation: PR #390 merged 20 October by guima-why

    All five recordsView ↗

    Details

    PR #390 (branch docs/mcp-stdio-example from the author's fork, opened 16 October) replaces the `npx mcp-remote` wrapper example in configuration.md and quick-start.md, in English and six locales (15 files, +76/-72), with a local stdio server example and a sentence that a remote HTTP server needs no wrapper. The collaborator guima-why authorised the repository's Aone E2E pipeline on the commit at 02:10:52Z and merged the pull request at 05:48:53Z (merge commit 17fc293e on main, authored as the author's commit); no review comment and no reply beyond the merge. The pull request text is engineering only and names no record; the records notice is the second step, not sent.

    Third merged engineering pull request of this shape after Supabase #51646 (14 October) and dashboard-icons #2954 (19 October): a change to the project's own documentation or setup output, without vulnerability wording, merged by the maintainer. First inside Alibaba Cloud; the separate support-chat report of 14 October about two help pages that still run the renamed bridge (mcp-remote-alibaba-cloud) is a different thread and stays open. The comment id in the link is the maintainer's /aone authorize comment as returned by the API on 20 October.

    How this was read PR metadata (merged_by, merged_at, merge_commit_sha, changed_files), the timeline, the comments and the merge commit on main read through the GitHub API on 20 October 2026 at 14:20 +07.

    read 20 Oct

    Acted onVerified

Day 25

  • homarr-labs/dashboard-icons: Maintainer merges the author's pull request that moves the MCP setup dialog's client tabs off the bridge to native HTTP: PR #2954 merged 19 October by ajnart, with his own fix on top

    “Thanks @playb0t, this is a nice cleanup, and the screenshots were really helpful.”

    All five recordsView ↗

    Details

    PR #2954 (branch fix/mcp-setup-native-http, opened 16 October from the author's fork) replaces the generated `npx mcp-remote` entries for VS Code, Claude Code, Claude Desktop, Windsurf and Zed with each client's native HTTP path to https://dashboardicons.com/api/mcp; the Custom MCP client tab keeps the bridge, pinned to mcp-remote@0.15.1. The maintainer (ajnart, Thomas Camlong) merged main into the branch, pushed 'fix(web): stop MCP copy button covering setup commands' (984b3a0), wrote that he checked every client tab at two viewports in light and dark and that the clipboard text matches, and merged at 19:27:52Z (merge commit c3d4416, 3 commits, +142/-55). The pull request text is engineering only and names no record; the records notice is the second step, not sent.

    Same shape as Supabase #51646 (14 October): a pull request about the project's own setup output, without vulnerability wording, merged by the maintainer with thanks; the merge is the project's act, the records are not named in it. A GitHub notification of 19:28:14Z reports a failed 'Web verification' run for the branch on the fork side; the upstream check on the same commit and the main branch runs after the merge are green; the fork-side run was not opened. The project's separate private report GHSA-qvm5-6p3v-p2xm (issue-update flow, filed 16 October) is unrelated to the records and stays in triage. The maintainer's own fix on top was prompted by the screenshots in the PR body.

    How this was read PR metadata, commit list, the maintainer's comment and the timeline read through the GitHub API on 20 October 2026 at 09:00 +07; check run 'verify' on 984b3a0 reports success; Main CI on main after the merge (9c165ef, 345e670) reports success.

    read 20 Oct

    Acted onVerified

Day 24

Author's posts, replies (1)
  • Alex Gercog (the author): Pull request #8954 by Alex Gercog (@playb0t) in Skyvern: replace mcp-remote in the Claude Desktop API-key setup and reuse the packaged adapter in the CLI; two commits, tested with local Skyvern through Desktop; open, not merged

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 18 Oct

    AuthorVerified

Day 23

  • northstar-agent-os (FNY666): Within an hour of the author's data-point comment, PR #105 adds a non-blocking warning for mcp-remote 0.1.39 through 0.15.1 and cites the 15 October research report in code and in the PR body

    “Evidence: https://github.com/playb0t/mcp-remote-oauth-security/blob/main/docs/research-2026-10-15/README.md”

    All five recordsView ↗

    Details

    At 13:07Z the repository owner pushed 'security: warn on unconfirmed later mcp-remote releases' (71d83e9) and at 13:18Z renamed the PR to 'security: block listed and warn on unverified mcp-remote'. The exact pins in the five CVE ranges keep the critical blocking finding; exact releases 0.1.39 through 0.15.1 now raise a medium MCP_UNCONFIRMED_MCP_REMOTE_REMEDIATION finding that the runtime shows as advice without changing the admission gate; later unknown releases stay unclassified. A code comment carries 'Evidence: https://github.com/playb0t/mcp-remote-oauth-security/blob/main/docs/research-2026-10-15/README.md' and the finding text says the report 'reports that OAuth discovery behavior remains in releases through v0.15.1' and 'is based on bounded public tests and does not establish' production exploitability. The PR body's Evidence section cites the five records, the v0.15.1 release with no stated remediation, the release lockfile pinning @modelcontextprotocol/client@2.0.0, the SDK advisory GHSA-6qxp-vccf-f47h (2.0.0-2.1.0 conditionally affected, 2.2.0 patched) and the 15 October report, and states the report's limits as the report states them. Tests added for the advisory interval and its non-blocking severity; CI run 39035628620 passed the admission tests. Open, not merged; no reply comment, the change itself is the response.

    Follows ev-20261017-d-northstar-agent-os-fny666 (the original PR). The author's comment asked for nothing and named the choice as theirs; the change came 54 minutes later and takes the weaker form (advice, not block), exactly the limit the report states. Second consumer after agent-audit-kit to cite the research repository from code; first to cite the 15 October follow-up. The bundled-SDK observation (client 2.0.0 inside the SDK advisory's range) was reached independently by the PR author from the lockfile and the SDK advisory.

    How this was read PR metadata, body, commit list, commit 71d83e9 files and patch read through the GitHub API on 17 October 2026 ~20:05 +07; timeline shows the rename at 13:18:36Z; no new comments under the PR.

    read 17 Oct

    Acted onVerified
Author's posts, replies (4)
  • Alex Gercog (the author): Reply by the author under #3437, after a review by the maintainer of agent-audit-kit: the proposal reshaped into three one-clause edits to existing lines of the SSRF section and a shorter subsection

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 17 Oct

    AuthorVerified
  • Alex Gercog (the author): Comment by the author under northstar-agent-os pull request #105: the 15 October run of 0.15.1 as one data point for the limit the pull request names; no change to its rule requested

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 17 Oct

    AuthorVerified
  • Alex Gercog (the author): Issue #46357 and pull request #46358 by the author in GitHub's documentation: the Atlassian MCP example for Copilot cloud agent connects to the remote server directly over HTTP instead of through a local npx mcp-remote process

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 17 Oct

    AuthorVerified
  • agent-audit-kit (Sattyam Jain): Maintainer of agent-audit-kit joins the author's specification issue #3437 with three additions to the proposed text

    “+1, and two things the new subsection could address”

    All five recordsView ↗

    Details

    Under the author's issue in modelcontextprotocol/modelcontextprotocol (opened 15 October: the SSRF section of the Security Best Practices page does not cover local stdio-to-HTTP bridges acting as OAuth clients), sattyamjjain commented '+1' at 07:28Z on 17 October with three line-referenced points against upstream commit 86f6e0c: the authorization specification's STDIO sentence can be read as exempting a bridge; the 'Enforce HTTPS' loopback allowance covers a server-supplied http://localhost URL if read literally; the subsection should cross-link 'stdio Transport Security in Proxy Scenarios'. The author answered at 08:21Z accepting all three and reshaping the proposal into one-clause edits of lines 415, 424 and 441 plus a shorter subsection. No maintainer of the specification has commented; no labels.

    Same source as the D rows of 27 and 30 September (detection rule) and the A rows for its intake bots; this is reception of the author's own specification issue, not a change in his project. The author's reply is not a row.

    How this was read comment and issue state read through the GitHub API on 17 October 2026 (comments 2, labels none, author_association NONE); his three line references re-read against the files at 86f6e0c the same afternoon.

    read 17 Oct

    ReplyVerified
One copy entry
  • Intake bots of Sattyam Jain's projects: mnemo: Dependabot bump of the agent-audit-kit action 0.6.10 to 0.6.20 names CVE-2026-52001 (PR #210, open)

    CVE-2026-52001View ↗

    Details

    Same shape as PR #197 of 3 October; filed under the existing source name. The act it echoes is agent-audit-kit's own, already in the ledger (8 October).

    How this was read gh api repos/sattyamjjain/mnemo/pulls/210 read in the judgment pass: author dependabot[bot], created 2026-10-17T15:03:00Z, state open, body carries the commit line 'fix(pins): cite CVE-2026-52001 on the mcp-remote pin'.

    read 18 Oct

    CopyVerified

First seen on this daythe source gives no date for its own entry, or for the statement listed

  • first seen

    northstar-agent-os (FNY666): Pull request adds an admission block for mcp-remote pins in the five CVE ranges and cites the author's specification issue #3437

    All five recordsView ↗

    Details

    The repository owner opened PR #105 'security: block CVE-listed mcp-remote versions at admission' on 17 October 05:02Z (branch security/mcp-remote-cve-admission-2026-10-17, 2 files, +93/-1): exact npm pins mcp-remote@0.1.16 through 0.1.38 raise a critical MCP_VULNERABLE_SERVER_PACKAGE finding that the runtime's tighten-only policy maps to 'blocked' before server startup; unpinned installs stay on the existing generic warning; regression tests cover the range starts 0.1.16/0.1.18/0.1.32, the last affected version and the outside versions 0.1.15, 0.1.39, 0.15.1. The body cites the five MITRE records by their cvelistV5 JSON, the MCP Security Best Practices SSRF section and public issue #3437 ('reports the local stdio-to-HTTP bridge case and a reproduction claim; it has no maintainer comments at the time of this PR'), and states that 0.15.1 is outside the recorded ranges while making no claim about its remediation status. Open, not merged, no reviews or comments at the time of reading; the author is the repository owner.

    Second project after agent-audit-kit to encode the records into a rule; first to cite the specification issue. Small project (1 star). The pin-only match leaves 0.15.1 unflagged, which the PR body names as a deliberate limit, not a claim of remediation. The author's bench of 15 October (0.15.1 still follows the paths of two records) is public in the research repository and could inform their decision; no contact made. Surfaced by the operator in chat.

    How this was read PR, its body, files and the issue #3437 timeline read through the GitHub API on 17 October 2026 ~18:10 +07; repository metadata read the same minute (created 2026-09-05, 1 star, 0 forks, MIT, Python; owner account from 2021, no name, 0 followers).

    read 17 Oct

    Acted onVerified
Three copy entries

Day 22

One copy entry
  • first seen

    Release Alert: Generated CVE list for geelen/mcp-remote names all five records

    All five recordsView ↗

    Details

    No byline and no page date; the page carries a 'Last Release' entry for the repository dated 14 October 2026. Same layout for every repository on the site. No text addressed to an AI reader.

    How this was read Page opened with WebFetch on 16 October 2026 after a web search surfaced it; clock reading taken in the same turn.

    read 16 Oct

    CopyVerified

Day 21

Author's posts, replies (2)
  • Alex Gercog (the author): Follow-up by the author: the 9 October procedure repeated on the published 0.15.1 (released 14 October): the same F-01 / F-02 request paths, a token request with an Authorization header to the server-named authorization server in the full trace, ten helper functions byte-identical to 0.14.3, the bundled SDK still client 2.0.0; twelve runs across five versions kept (commit fbd53bf)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 15 Oct

    AuthorVerified
  • Alex Gercog (the author): Issue by the author in the MCP specification repository (#3437): the Security Best Practices SSRF section does not cover a local stdio-to-HTTP bridge acting as the OAuth client on the user's machine; a subsection proposed

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 15 Oct

    AuthorVerified
Two copy entries
8–14 Oct 2026Day 14–20 · 25 entries

Day 20

  • supabase/supabase: Maintainer merges the author's pull request that moves the Devin preset off the bridge to the client's native HTTP path: PR #51646 merged 14 October by Rodriguespn after a live test of the hosted flow

    “Thank you for addressing my comments @playb0t. Preview looks good. Approving this. Thanks again for your contribution!”

    View ↗

    Details

    An engineering fix, not a CVE fix: the PR carried no record identifier. The Devin preset in the MCP URL builder (packages/ui-patterns/src/McpUrlBuilder) launched `npx -y mcp-remote <url>` unpinned although the Devin CLI connects to remote MCP servers over HTTP natively; the PR replaces the launch with `devin mcp add` / `devin mcp login`, drops the dead bridge type and keeps the round-trip test. Opened 05:20Z from the fork; review 07:13Z (seven asks, reviewer completed a real Supabase OAuth with Devin CLI 3000.11.3); fixes pushed 08:22Z; approved 11:42Z; merged 12:19Z as 0f618d8, four files, +46/-38. PR open to merge: 7 h.

    Second project in two days (after UltraRAG #538) where a pull request about the client's own behaviour, without vulnerability wording, got a same-day maintainer response; the private reports to tier-1 projects stayed in triage over the same days. The records notice for this project is the second step, drafted in case folder 92, to be sent after the article is live. The live site deploy was not checked.

    How this was read gh api on 14 October 2026 at 19:53 +07: pulls/51646 (state closed, merged true, merged_at 12:19:05Z, merged_by Rodriguespn, merge_commit_sha 0f618d8), the issue timeline (head force-pushed 11:59Z by Rodriguespn, merged and closed 12:19Z), compare 0f618d8...master = identical, and a raw read of master clients.data.ts (devin mcp add / devin mcp login, no mcp-remote string).

    read 14 Oct

    Acted onVerified
Two copy entries
  • first seen

    TrueNix/website: New repository carrying the record identifiers

    All five recordsView ↗

    Details

    How this was read pinned file opened by the collector; it names CVE-2026-51994, CVE-2026-51995, CVE-2026-51996.

    read 14 Oct

    CopyVerified
  • first seen

    OpenCVE: OpenCVE's enrichment repository (opencve/opencve-kb) carries the five records with inferred semver ranges

    View ↗

    Details

    Organisation repository, machine-generated JSON per record (enrichment marked 'inferred'). Third place for a source already counted under OpenCVE.

    How this was read File read at commit 3dac61e8 through the GitHub API, 15 October.

    read 15 Oct

    CopyVerified

Day 19

  • OpenBMB/UltraRAG: Maintainer fixes the remote MCP launch failure reported in issue #537 and credits the author by name: PR #538 merged 13 October, 'Thanks to @playb0t (Alex Gercog) for reporting the issue'

    “Thanks to @playb0t (Alex Gercog) for reporting the issue.”

    View ↗

    Details

    A functional fix, not a CVE fix: the issue of 12 October reported that the HTTP MCP build and run failed before any transport started in the recommended CPU image; no record identifier was claimed in it. The PR replaces the one-element-tuple launch configuration with a mapping, adds Node.js 22 with npm/npx and the compiled frontend to all three Docker images, publishes latest tags, and adds HTTP/HTTPS regression tests and a CPU-image smoke check. Author xhd0728 (Haidong Xin), opened 08:45Z, merged 08:55Z, one commit 0b37ce7, 10 files, +227/-35. Reaction time from the issue (12 Oct 06:10Z) to merge: 26 h 45 min.

    The fixed launch configuration (src/ultrarag/client.py, new remote_server_launch_config) is command npx, args ['-y', 'mcp-remote', url], unpinned; with Node and npx now in all three images, every remote HTTP MCP pipeline starts the bridge at whatever version npm serves (0.14.3 on 13 October). No CVE claim rests on this row; the CVE notice to this project (file 65 §7) was never sent. The later timeline event (10:13Z, commit b91848f) is the same change on main.

    How this was read gh api on 13 October 2026 at 17:53 +07: the account's notifications, the PR (state, merge time, body, author, files, commits, review comment), the issue timeline (assigned and labeled 08:07Z, cross-referenced 08:45Z, closed 08:55Z by xhd0728) and the issue state (closed, 0 comments).

    read 13 Oct

    Acted onVerified
  • adudley78/mcp-audit: Scanner registry adds an mcp-remote entry listing the five records; the offline advisory check SC-004 flags a pinned version below the recorded fix

    “offline CVE advisory check (SC-004) against the bundled registry (known_vulnerabilities)”

    All five recordsView ↗

    Details

    Commit 5c45049 of 13 October (pull request #152, 'sync CVE lists from OSV, calibrate SC-004, add weekly check') adds mcp-remote to registry/known-servers.json with the five record identifiers, each with a description and a fixed_in value; earlier revisions of the file (862b0ea of 6 October, 7c75103 of 11 October) carry no mcp-remote entry. The project's README describes SC-004 as an offline CVE advisory check against this bundled registry.

    The pull-request body says the entries are merged by a sync script from OSV ranges; the commit is by the project's maintainer. The entry also lists two records that are not this research's.

    How this was read File read at commits 862b0ea, 7c75103, 5c45049 and 2d0020b9 through the GitHub API; pull requests #143 and #152 and the README read the same way; 15 October.

    read 15 Oct

    Acted onVerified
  • adudley78/mcp-audit: Registry states 'first unaffected release 0.1.39' and fixed_in 0.1.39 for all five records

    All five recordsView ↗

    Details

    The practical effect for the scanner's users: SC-004 drops a record for any pin at or above 0.1.39, so the versions people run today (0.14.3 and 0.15.1 carry most downloads) raise no finding.

    How this was read File read at commit 2d0020b9 through the GitHub API; pull request #152 body; upstream releases read 15 October; 15 October.

    read 15 Oct

    DivergenceVerified

Day 18

Two copy entries
  • aghdetngf/cybervault-cve-intel: Generated advisory pages for all five records, each with a Nuclei template and a probe script; scores equal CISA's (9.1, 7.5, 9.8, 8.8, 7.5)

    All five recordsView ↗

    Details

    Repository created 8 October 2026, 100 commits since 12 October 00:00Z, five commits for these records within ten seconds; pages carry the author field 'cybervault-security-intel' and link a dossier at cybervault-cve.pages.dev. The remediation section is a template ('Update vulnerable components to the latest patched release immediately', apt/dnf commands for 'software-component') and names no mcp-remote version; the description text is the CNA's. Borderline between a copy and a fix divergence; the weaker value taken, the template claim noted here.

    How this was read gh api on 13 October 2026: repository metadata, the five commits (dates, author, files), the commit count since 12 October, and the CVE-2026-51994 page at 8973775 decoded and read (severity line, description, Nuclei template, probe script, remediation section).

    read 13 Oct

    CopyVerified
  • by this date

    Ares-X/VulWiki: Weekly maintenance review of a Chinese vulnerability knowledge base lists the CVE-2026-51994 file path among a scanned source's files; the knowledge base has no page on the record

    CVE-2026-51994View ↗

    Details

    The review folder (PR #27, merged 2026-10-12T15:39Z by AresX) holds a hand-written README on reviewing public sources and generated audit files; supplementary.json is a list of file paths of the form 2026/CVE-NNNN.json, one of them ours. Code search in the repository finds the identifier only in that list.

    How this was read gh api on 13 October 2026: repository metadata and last three commits, the README and supplementary.json of docs/reviews/20261012-weekly at 9407b3b decoded and read, code search for CVE-2026-51994 in the repository (one hit, the list). The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 13 Oct

    CopyVerified
One copy entry

Day 17

One copy entry
  • by this date

    itvedas29/itvedas: Daily CVE data file synced by a bot carries the CVE-2026-52001 entry with the CNA description and the 7.5 score; no page per record, no byline

    CVE-2026-52001View ↗

    Details

    Repository commits are authored 'CVE Sync Bot' ('chore: sync CVE intelligence 2026-10-12') and 'ITVedas Bot' ('Autopilot update'); the blob is a per-day list of records; its remediation sentence is the generic 'Apply vendor security updates and follow NVD/vendor mitigation guidance', naming no fix.

    How this was read gh api on 13 October 2026: repository metadata and last three commits read (bot authors, daily sync), the blob at c69de6b decoded and the CVE-2026-52001 entry read (name, cvss 7.5 V31, description, remediation line); blob commit dated 2026-10-11T19:33:36Z. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 13 Oct

    CopyVerified

Day 16

Author's posts, replies (1)
  • Alex Gercog (the author): Runtime-consumer screen of GitHub by the author: 457 repositories screened, 438 kept, 20 read at pinned commits (14 products); private notices to seven maintainers the same day, six through GitHub private vulnerability reporting and one by email; two range-update requests filed with MITRE

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 10 Oct

    AuthorVerified
Six copy entries

Day 15

  • jvlatacc/vigil (obvious-autobuild bot): An agent-written pull request pins mcp-remote at 0.1.49, reading 0.1.39+ as the "apparent remediation level" from the records' "through 0.1.38" wording

    All five recordsView ↗

    Details

    How this was read PR read through the GitHub API (title, author, created/merged timestamps, body paragraph quoted); repository: 0 stars, created 2026-08-27, user-owned.

    read 10 Oct

    DivergenceVerified
Author's posts, replies (1)
  • Alex Gercog (the author): Research dossier by the author: the published 0.14.3 CLI run in full against loopback canaries, the discovery path in all 58 stable releases from 0.1.32 through 0.14.3, and the package's code signatures found under 12 other npm names and in 8 other repositories (PR #1 merged)

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 9 Oct

    AuthorVerified
One copy entry
  • by this date

    jockerjml: Fork of the research repository (jockerjml/mcp-remote-oauth-security), starred the same day

    View ↗

    Details

    Corrects the provenance note of the superseded row: the collector did queue this fork on 10 October 2026 (queue item q-0032, first seen 20:12 local); the judgment pass of the same evening closed it at 21:39 with the disposition 'mass-forking account; counted as a copy, no row', which contradicts the skill's bucket rule (a fork is an A row whatever account made it) and the treatment of the other two forks (adeyholar, 30 September; kiranicholenorks-jpg, 21 October), both of which carry A rows. Row added on 25 October after a manual read of the fork list. Provable signs: a forks-only account with a collecting cadence; no sign of a person-typed action beyond the fork and the star.

    How this was read gh api forks list, compare endpoint and user profile read in this pass; clock read with `date -u` in the same pass immediately after the row was first written. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 25 Oct

    CopyVerified

Day 14

  • agent-audit-kit (Sattyam Jain): Rule extended to CVE-2026-52001 on the author's issue #921; PR #924 merged, tag v0.6.18 cut the same day

    “52001 is inside the existing pin range and was missing from the citations. Added in #924, no range change.”

    CVE-2026-52001View ↗

    Details

    The maintainer answered issue #921 at 12:20Z ("52001 is inside the existing pin range and was missing from the citations. Added in #924, no range change") and merged PR #924 at 12:28:45Z (merge commit 6145719b); the issue closed at 12:28:46Z. Release PR #925 (chore(release): 0.6.18) merged at 12:39:32Z and names the citation as one of three items; the tag v0.6.18 exists and its pins scanner names CVE-2026-52001 in the description of AAK-MCP-REMOTE-CVE-2026-51994-001 (0.1.18-0.1.38 per NVD, pin 0.1.16-0.1.38 unchanged) and in the pin's comment. CHANGELOG.cves.md carries a 2026-10-08 (v0.6.18) entry crediting the issue to the researcher named on the records. At the time of reading the GitHub release object and the PyPI upload for 0.6.18 were not yet visible (releases/latest still v0.6.17).

    Re-issue of the row of the same minute with links in the ledger's object shape (the first carried bare strings, which the renderer refuses). Prompted by the author's own issue (filed 8 Oct 04:54Z from the playb0t account); both PR bodies state Claude Code generated them. The changelog entry paraphrases advisory F-11 v1.0.1 as hardening and quotes its CVSS line; the official CISA-ADP score of 7.5 stands in the records and is not contested here. Supersedes the 'leaves CVE-2026-52001 out' reading of ev-20261002-d-agent-audit-kit-sattyam-jain-2 for the source state, not for the v0.6.11 release fact.

    How this was read gh api reads of issue 921, pulls 924 and 925, their files, the pins scanner at ref v0.6.18 (two lines naming CVE-2026-52001), the tags list and releases/latest.

    read 8 Oct

    Acted onVerified
Author's posts, replies (4)
  • Alex Gercog (the author): Thread on Bluesky by the author, addressed to Simon Willison

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 8 Oct

    AuthorVerified
  • Alex Gercog (the author): Article by the author, second edition on LinkedIn

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 8 Oct

    AuthorVerified
  • 0xamlab: typescript-sdk issue #2946: the reader asks for the one-line reference text from the author

    “yes, the one-liner would help. The reference is much stronger with the discovery-side framing from the person who found it.”

    CVE-2026-51995View ↗

    Details

    A second comment (8 Oct 13:11Z) on the author's issue agrees with the author's framing of the two records and asks for the offered one-line reference text for GHSA-6qxp-vccf-f47h. No maintainer has commented; the issue stays open with the v1 and v2 labels.

    Same reader as the S row of 7 October; not a maintainer by public data. The author's reply with the one-liner is drafted in the case outreach log and waits for the operator's hand.

    How this was read gh api read of the issue and its three comments.

    read 8 Oct

    ReplyVerified
  • Compound Labs: Bluesky: a company account replies to the author's mcp-remote post with an issuer-allowlist recommendation

    “Discovered OAuth endpoints should stay inside an operator-approved issuer allowlist.”

    View ↗

    Details

    A reply (8 Oct 16:33Z) from the account @thecompound.tech, display name Compound Labs, under the author's post of 8 October states that discovered OAuth endpoints should stay inside an operator-approved issuer allowlist. It names no record, no package version and no fix; it is a general defensive recommendation on the post's subject.

    Company account, not a personal byline; whether a person typed the reply cannot be established from the post. The parent is the author's post addressed to @simonwillison.net (8 Oct 05:22Z).

    How this was read Reply and its parent read through the Bluesky public API (getPostThread); read 9 October 2026, 10:58 +07.

    read 9 Oct

    ReplyVerified
1–7 Oct 2026Day 7–13 · 43 entries

Day 13

  • pranava0x0/vibe-coding-security: Tracker's CVE-2026-52001 row updated to CISA's 7.5 High (sweep PR 121, merged 7 Oct 15:40Z)

    CVE-2026-52001View ↗

    Details

    The daily sweep replaced the F-11 row 'No CVSS supplied' with 'CISA-ADP / 3.1: 7.5 High' and the vector, dated 2026-10-06; the entry's status stays high / unconfirmed. The sweep's learnings note records the change as drift caught by its evidence gate.

    PR opened by the repository owner's account; title 'sweep 2026-10-07: 4 new, 6 updated' and the file set are the repository's scheduled sweep shape.

    How this was read PR diff read via gh on 2026-10-08: removed line '| CVE-2026-52001 | F-11 | No CVSS supplied |', added line '| CVE-2026-52001 | F-11 | CISA-ADP / 3.1: 7.5 High | ... | 2026-10-06 |'; merge commit 155f0455.

    read 8 Oct

    Acted onVerified
  • ENISA EUVD: EUVD-2026-86021 score changed

    CVE-2026-52001View ↗

    Details

    How this was read collector reading of the source API, 2026-10-07T21:05:51+07:00.

    read 7 Oct

    RegistryVerified
Author's posts, replies (1)
  • 0xamlab: typescript-sdk issue #2946: a reader compares CVE-2026-51995 with GHSA-6qxp and supports the cross-reference

    “Confirmed via the published records: these are related but distinct.”

    CVE-2026-51995View ↗

    Details

    A comment (7 Oct 17:01Z) on the author's issue states, from the published records, that GHSA-6qxp-vccf-f47h (CVE-2026-104850) and CVE-2026-51995 are related but distinct, and supports adding the cross-reference. The commenter is not a maintainer by public data; no maintainer has replied.

    How this was read issue comments read via gh on 2026-10-08.

    read 8 Oct

    ReplyVerified
Six copy entries (one not verified)
  • first seen

    emmanuelgjr/genai_incidents: New repository carrying the record identifiers

    All five recordsView ↗

    Details

    How this was read pinned file opened by the collector; it names CVE-2026-51994, CVE-2026-51995, CVE-2026-51996.

    read 7 Oct

    CopyVerified
  • first seen

    localden/mcp-repo-data-tracker: New repository carrying the record identifiers

    CVE-2026-51995View ↗

    Details

    How this was read pinned file opened by the collector; it names CVE-2026-51995.

    read 7 Oct

    CopyVerified
  • first seen

    Shenlong vulnerability database (cve.imfht.com): Chinese-language CVE page carries CVE-2026-51994 and links the research repository; AI-generated material labelled

    CVE-2026-51994View ↗

    Details

    How this was read page opened on 2026-10-08 through the fetch tool; first observed by the 7 October packet (evidence/imfht.txt, 18:25Z).

    read 8 Oct

    CopyVerified
  • first seen

    Trendshift: Repository listing for playb0t/mcp-remote-oauth-security

    View ↗

    Details

    How this was read page opened on 2026-10-08 through the fetch tool; first observed by the 7 October packet (evidence/trendshift.txt, 18:25Z).

    read 8 Oct

    CopyVerified
  • first seen

    InfoSecCenter: CVE page carries CVE-2026-51994 with the research repository and F-01 in its references

    CVE-2026-51994View ↗

    Details

    30 October 2026 11:37:42Z and 11:37:43Z: the record page and the site root both returned HTTP 500 (receipt in evidence/2026-10-30-section05-recheck.json); the same status was reported from the CRAFTHOUSE side earlier that day. The page was last read on 8 October 2026.

    read 30 Oct

    CopyUnreachable

Day 12

  • CVE Program (MITRE): CVE-2026-52001 record updated

    CVE-2026-52001View ↗

    Details

    How this was read collector reading of the source API, 2026-10-07T21:05:51+07:00.

    read 7 Oct

    RegistryVerified
  • NVD (NIST): CVE-2026-52001 scoring changed

    CVE-2026-52001View ↗

    Details

    How this was read collector reading of the source API, 2026-10-07T21:05:51+07:00.

    read 7 Oct

    RegistryVerified
  • by this date

    GitHub Advisory Database: GHSA-4gh6-j99c-x6g2 (CVE-2026-52001) carries CVSS 3.1 7.5 High; still unreviewed, no package mapping (API read 8 Oct)

    CVE-2026-52001View ↗

    Details

    How this was read advisories API read via gh at 2026-10-08T05:13:19Z. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 8 Oct

    RegistryVerified
Author's posts, replies (3)
  • Alex Gercog (the author): PSA post by the author on r/cybersecurity

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 6 Oct

    AuthorVerified
  • Reddit: r/cybersecurity: the author's PSA post on the five records (u/AI_TRIMIND, 02:13 UTC)

    All five recordsView ↗

    Details

    The author's own post, captured the same day by a third-party RSS archive (rumca-js/RSS-Link-Database-2026). Reception (score, comments) is unmeasured: the post page was not reachable from the tool.

    Seen in the RSS archive's 2026-10-06 r/cybersecurity entries file; the reddit page itself refused the fetch.

    read 7 Oct

    ReplySearch-only
  • Reddit: r/cybersecurity: a reader of the author's PSA post reports finding several mcp-remote installations in the listed range by following the comment's check

    All five recordsView ↗

    Details

    First reported case of a reader locating affected installations through the published check. The author relayed the comment on 7 October; the comment page was not reachable from the tool, so the wording and the count are the author's account.

    Source: the author's note of 7 October (Desktop file on protocol pivoting and mcp-remote). Reddit refuses the fetch tool; re-read on a route that reaches it.

    read 7 Oct

    ReplySearch-only

Day 11

No verified entries recorded

Day 10

Two copy entries
  • pranava0x0/vibe-coding-security: Daily sweep links the mcp-remote advisory from two new pieces (Loom for AWS, rmcp roundup)

    All five recordsView ↗

    Details

    Sweep commit 'sweep 2026-10-04: 4 new, 10 updated (#118)'.

    How this was read commit patch read via gh on 2026-10-08: added lines in advisories/2026-10-loom-for-aws-*.md and the rmcp entry link 2026-09-mcp-remote-oauth-discovery-ssrf-cve-batch.md.

    read 8 Oct

    CopyVerified
  • by this date

    xerj-org/corpus-first-epss: Mirror of FIRST's EPSS bulk scores carries the record identifiers (commit of 4 Oct 22:24Z)

    CVE-2026-51994View ↗

    Details

    How this was read commit history of the pinned file read via gh on 2026-10-08: one commit 1c3552e 'Mirror FIRST EPSS current bulk scores 2026-10-04'. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 8 Oct

    CopyVerified

Day 9

  • pranava0x0/vibe-coding-security: Advisory corrected and a CVE-mapping check added

    All five recordsView ↗

    Details

    The tracker rewrote its mcp-remote advisory against the records, attributed the four scores to CISA-ADP, stated the OSV fixed-version conflict, and added an automated check with saved registry copies that fails its build when a finding table disagrees with the CVE records.

    Opened and merged from the maintainer's own account (type User); the PR's review table credits one comment to an automated Codex review.

    How this was read PR body, file list and merge state read through the GitHub API; last read 3 October 2026, 12:38 +07.

    read 3 Oct

    Acted onVerified
  • pranava0x0/vibe-coding-security: Mapping of CVE-2026-51995 corrected to F-02

    CVE-2026-51995View ↗

    Details

    Merged without two wording changes the researcher proposed on 3 October (the advisory title and one phrase on the evidence page); those are editorial and not divergences from the records.

    How this was read PR read through the GitHub API (merged_at 2026-10-03T05:34:10Z); the advisory file read on the main branch, F-02 row carries CVE-2026-51995; last read 3 October 2026, 12:38 +07.

    read 3 Oct

    DivergenceVerified
One copy entry (one not verified)
  • Intake bots of Sattyam Jain's projects: mnemo: Dependabot bump of the agent-audit-kit action 0.3.92 to 0.6.10 names CVE-2026-51994 (PR #197, closed unmerged)

    CVE-2026-51994View ↗

    Details

    Opened via a fetch tool in the judgment pass without a clock receipt; weaker value kept. Third repository of the same owner, filed under the existing source name.

    read 7 Oct

    CopySearch-only

Day 8

  • agent-audit-kit (Sattyam Jain): Rule extended to CVE-2026-51996

    “Covered by AAK-MCP-REMOTE-CVE-2026-51994-001: same 0.1.16 to 0.1.38 range, now listing it.”

    CVE-2026-51996View ↗

    Details

    Issue 834 was dispositioned in PR 843: CVE-2026-51996 is listed on the existing mcp-remote pin rule, same 0.1.16 to 0.1.38 range. Merged for release 0.6.11.

    Merged from the maintainer's account (type User). The tag 0.6.11 was not checked.

    How this was read PR body and merge commit 5c7e7098 read through the GitHub API (merged 2026-10-02T11:23:30Z); last read 3 October 2026, 12:38 +07.

    read 3 Oct

    Acted onVerified
  • agent-airlock (Sattyam Jain): CVE-2026-51996 triaged, recorded as out of scope

    “Out-of-scope row added, no module.”

    CVE-2026-51996View ↗

    Details

    Issue 249 was dispositioned in PR 265: agent-airlock recorded CVE-2026-51996 as out of scope for its tool-argument guards and added a catalog row with no detection module.

    Merged from the maintainer's account (type User). The bot ticket for this record is already on the page.

    How this was read PR body and merge commit 6328976a read through the GitHub API (merged 2026-10-02T10:53:22Z); last read 3 October 2026, 12:38 +07.

    read 3 Oct

    Acted onVerified
  • agent-audit-kit (Sattyam Jain): Release v0.6.11 ships the rule covering four records; v0.6.17 (6 Oct) is current and leaves CVE-2026-52001 out

    CVE-2026-51994 · CVE-2026-51995 · CVE-2026-51996 · CVE-2026-51997View ↗

    Details

    Rule AAK-MCP-REMOTE-CVE-2026-51994-001 in the tagged source cites CVE-2026-51994, 51995, 51996 and 51997 with the pin 0.1.16 through 0.1.38 and 'upstream names no fix'; releases v0.6.12 through v0.6.17 (3 to 6 October) do not change it. CVE-2026-52001 is absent from the rule, the CVE changelog and the issue list as of 8 October 04:50Z.

    How this was read releases API and the v0.6.17 tree read via gh on 2026-10-08: agent_audit_kit/rules/builtin.py cve_references and scanners/mcp_cve_pins_2026_07.py pin; code search and issue search for 52001 empty.

    read 8 Oct

    Acted onVerified

Day 7

  • by this date

    OpenCVE: OpenCVE's generated enrichment for CVE-2026-51996 recommends upgrading to 'the latest patched release (e.g., 0.1.39 or newer)'

    CVE-2026-51996View ↗

    Details

    Generated enrichment text (the page labels it OpenCVE AI analysis and inferred enrichment), not a vendor statement. The CNA description and the CISA scores on the page are taken as they stand. Only CVE-2026-51996 was opened this pass; whether the other four pages carry the same line is not checked. Fourth place for a source already counted under OpenCVE.

    How this was read page opened by WebFetch on 23 October; Recommended Actions and Remediation sections read; enrichment updated 2026-10-01T21:30:13Z and AI analysis generated 1 October 21:18 UTC per the page; fetched between the clock reads 10:12:48 and 10:15:01 +07:00, the later one stated. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 23 Oct

    DivergenceVerified
  • SentinelOne Vulnerability Database: SentinelOne's AI-generated page for CVE-2026-51994 recommends upgrading to 'a version later than 0.1.38 that validates resource_metadata targets'

    CVE-2026-51994View ↗

    Details

    The page carries the line 'This content was generated using AI'. Score shown 9.1, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, matching the record; affected versions listed 0.1.32 through 0.1.38. Found by the deep-research run of 27 October.

    How this was read page opened by curl at 2026-10-27T06:52:28Z; the remediation sentence, the line 'This content was generated using AI', the page date 'October 1, 2026' and the 9.1 score read from the page text.

    read 27 Oct

    DivergenceVerified
One copy entry
  • by this date

    Sunojakash/sunojakash.github.io: Bot-refreshed CVE feed on a personal GitHub Pages site carries CVE-2026-51996

    CVE-2026-51996View ↗

    Details

    Commits are authored by 'cve-bot' (CVE refresh) and 'news-bot' (security news refresh) several times a day; the file names OpenCVE API v2 as its source. A rolling list: the entry leaves the file when newer CVEs push it out.

    How this was read File read through the GitHub API at the pinned commit (sha256 a3a3b849406768be5f53e17d4cf0dfa5924725ee416bc08a0fe0540043a30b2d); the file's own last_updated is 2026-10-01T22:49:49Z; repository commits read the same minute. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 2 Oct

    CopyVerified

First seen on this daythe source gives no date for its own entry, or for the statement listed

  • first seen

    INCIBE-CERT (Spain): Early-warning entries for the five records

    All five recordsView ↗

    Details

    How this was read Five pages opened; last read 1 October 2026, 16:57 +07.

    read 1 Oct

    RegistryVerified
  • first seen

    Debian security tracker: All five records marked NOT-FOR-US, Debian's label for software it does not ship

    All five recordsView ↗

    Details

    How this was read Five pages opened; last read 1 October 2026, 16:57 +07.

    read 1 Oct

    RegistryVerified
  • first seen

    Alpine security tracker: Entries for the five records, no package matched

    All five recordsView ↗

    Details

    How this was read Five pages opened; last read 1 October 2026, 18:45 +07.

    read 1 Oct

    RegistryVerified
  • first seen

    Rapid7: Vulnerability database entries for the five records

    All five recordsView ↗

    Details

    How this was read Five pages opened; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    RegistryVerified
  • first seen

    Aqua Security (AVD): Entries for the five records

    All five recordsView ↗

    Details

    How this was read Five pages opened; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    RegistryVerified
  • first seen

    Positive Technologies (dbugs): Entries PT-2026-97822 to PT-2026-97826 for the five records

    All five recordsView ↗

    Details

    The database's long address, dbugs.ptsecurity.com, did not load over a trusted connection; the entries were read at its short address. Vulners also lists the first entry under 'ptsecurity' (seen in a browser, not verified here).

    How this was read Five entry pages opened at the database's short address dbu.gs; last read 2 October 2026, 00:12 +07.

    read 2 Oct

    RegistryVerified
  • first seen

    Mend.io: CVSS v4 scores of unstated origin

    CVE-2026-51994 · CVE-2026-51995 · CVE-2026-51996 · CVE-2026-51997View ↗

    Details

    How this was read Four pages opened; last read 1 October 2026, 17:50 +07.

    read 1 Oct

    DivergenceVerified
  • first seen

    OffSeq Threat Radar: A severity label on the unscored record

    CVE-2026-52001View ↗

    Details

    How this was read Page opened; last read 1 October 2026, 17:51 +07.

    read 1 Oct

    DivergenceVerified
  • first seen

    HOL Guard: Describes the records as vulnerabilities 'in CISA ADP Vulnrichment'

    All five recordsView ↗

    Details

    How this was read Five pages opened; last read 1 October 2026, 17:51 +07.

    read 1 Oct

    DivergenceVerified
  • first seen

    BaseFortify: Puts the researcher's handle in the vendor column

    CVE-2026-51994View ↗

    Details

    How this was read Page opened; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    DivergenceVerified
  • first seen

    Positive Technologies (dbugs): Names PyPI as the vendor on one entry

    CVE-2026-51997View ↗

    Details

    How this was read Entry page opened; last read 2 October 2026, 00:12 +07.

    read 2 Oct

    DivergenceVerified
Six copy entries
24–30 Sep 2026Day 0–6 · 77 entries

Day 6

  • agent-audit-kit (Sattyam Jain): Rule extended to CVE-2026-51995 and CVE-2026-51997

    “The advisory NVD cites (playb0t/mcp-remote-oauth-security, F-02)”

    CVE-2026-51995 · CVE-2026-51997View ↗

    Details

    CVE-2026-51995 was added to the rule's references and the rule's lower bound moved from 0.1.32 to 0.1.16 for CVE-2026-51997. The closing notes cite the F-02 and F-08 advisories of the research repository. The change is on the main branch and not yet in a tagged release.

    The pull request says it was generated with Claude Code; it was merged from the maintainer's account.

    How this was read Issues and pull request read through the GitHub API; the rule file read on the main branch; last read 1 October 2026, 17:49 +07.

    read 1 Oct

    Acted onVerified
  • SingCERT (Singapore): Weekly security bulletin lists all five

    All five recordsView ↗

    Details

    How this was read Bulletin PDF opened and its text read page by page; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    RegistryVerified
Author's posts, replies (1)
Three copy entries
  • adeyholar (mass-forking account): Fork of the research repository

    View ↗

    Details

    How this was read Fork and account read through the GitHub API; last read 1 October 2026, 17:37 +07.

    read 1 Oct

    CopyVerified
  • Intake bots of Sattyam Jain's projects: Bot ticket for CVE-2026-51996 (in agent-audit-kit)

    CVE-2026-51996View ↗

    Details

    How this was read Issue read through the GitHub API; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    CopyVerified
  • CVE Brief: Daily digest of 30 September carries CVE-2026-51996

    CVE-2026-51996View ↗

    Details

    How this was read Digest page read directly; receipt cvebrief-digest-0930.

    read 2 Oct

    CopyVerified

First seen on this daythe source gives no date for its own entry, or for the statement listed

  • first seen

    Tenable: Vulnerability pages for the five records (CVE-2026-52001 seen 30 Sep, the other four 1 Oct)

    All five recordsView ↗

    Details

    How this was read Five pages opened and their page data read; last read 1 October 2026, 17:35 +07.

    read 1 Oct

    RegistryVerified
  • first seen

    Feedly: Tells readers a patch is available

    All five recordsView ↗

    Details

    How this was read Five pages opened; the advisories read through the GitHub API; last read 1 October 2026, 17:51 +07.

    read 1 Oct

    DivergenceVerified
  • first seen

    CVE Brief: Says a fix is available

    CVE-2026-51994 · CVE-2026-51996 · CVE-2026-51997View ↗

    Details

    How this was read Three pages opened; last read 1 October 2026, 17:54 +07.

    read 1 Oct

    DivergenceVerified
  • first seen

    Tenable: Scores that neither the records nor NVD carry

    All five recordsView ↗

    Details

    How this was read Five pages opened and their page data read; last read 1 October 2026, 17:52 +07.

    read 1 Oct

    DivergenceVerified
One copy entry
  • first seen

    Feedly: Pages for the five records

    All five recordsView ↗

    Details

    How this was read Five pages opened; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    CopyVerified

Day 5

  • Upwind (Roy Kalfon): Threat-feed card on CVE-2026-51996

    “By Roy Kalfon | 29 September 2026”

    CVE-2026-51996View ↗

    Details

    A bylined card in Upwind's AI Threat Feed restates the record and links it at cve.org. It does not link the research repository.

    The card has no address of its own and moves down the feed; on 1 October it sat on page 2.

    How this was read Feed pages opened and the card read; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    Written upVerified
  • CISA: ADP Vulnrichment: CVE-2026-51996 scored 9.8, Critical

    CVE-2026-51996View ↗

    Details

    SSVC: exploitation none, automatable yes, technical impact total. Four of the five records now carry a CISA score; CVE-2026-52001 carries none.

    How this was read CISA's container in the CVE record; last read 1 October 2026, 17:51 +07.

    read 1 Oct

    RegistryVerified
  • by this date

    Mend.io: Vulnerability database pages for four records

    CVE-2026-51994 · CVE-2026-51995 · CVE-2026-51996 · CVE-2026-51997View ↗

    Details

    How this was read Four pages opened; the fifth returned 404; last read 1 October 2026, 20:18 +07. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 1 Oct

    RegistryVerified
  • Upwind (Roy Kalfon): Advises updating to a version inside the affected range

    CVE-2026-51996View ↗

    Details

    How this was read Feed page opened and the card read; last read 1 October 2026, 17:50 +07.

    read 1 Oct

    DivergenceVerified
  • Intake bots of Sattyam Jain's projects: agent-airlock triage ticket tags CVE-2026-51996 as CWE-94

    CVE-2026-51996View ↗

    Details

    How this was read Issue read through the GitHub API; the record and NVD read the same minute; receipts airlock-issue-249 and record-51996-cwe.

    read 2 Oct

    DivergenceVerified
  • by this date

    HOL Guard: Lists CWE-94 beside CWE-328 for CVE-2026-51996

    CVE-2026-51996View ↗

    Details

    Fix availability on the same page: 'Not reported'.

    How this was read Page read directly (sha256 de3ba3b8...); the page's material update is 29 September; receipts hol-guard-51996 and record-51996-cwe. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 2 Oct

    DivergenceVerified
Author's posts, replies (2)
  • Alex Gercog (the author): Thread on X by the author

    View ↗

    Details

    How this was read The author's own publication; the linked page is the primary source.

    read 29 Sep

    AuthorVerified
  • @HoustonIntrove1: Reply under the author's thread on X

    “mcp-remote let the server pick the client's next request.”

    View ↗

    Details

    A reply posted five minutes after the thread restates its point. X counts four replies under the thread; this is the one opened for this record.

    How this was read Reply and thread read through X's public embed endpoint; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    ReplyVerified
Two copy entries

Day 4

  • CISA: Weekly bulletin SB26-271 lists all five

    All five recordsView ↗

    Details

    How this was read Bulletin page opened and each record located under its heading; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    RegistryVerified

Day 3

  • agent-audit-kit (Sattyam Jain): Detection rule added for CVE-2026-51994

    “The advisory it cites reconfirmed the flaw against 0.1.38 and names no fixed release.”

    CVE-2026-51994View ↗

    Details

    The scanner closed its intake ticket with a new rule, AAK-MCP-REMOTE-CVE-2026-51994-001, that flags mcp-remote 0.1.32 to 0.1.38 in MCP configs, package.json and lockfiles. The rule is in release 0.6.10, published the same day. The closing note says upstream has published no advisory and that no later release was tested.

    The pull request says it was generated with Claude Code; it was merged from the maintainer's account.

    How this was read Issue, pull requests and release read through the GitHub API; the rule located in the release's rule file; last read 1 October 2026, 17:55 +07.

    read 1 Oct

    Acted onVerified
  • by this date

    QiAnXin CERT: Listed in QiAnXin's feed, according to a crawler report

    All five recordsView ↗

    Details

    How this was read The crawler's report file read through the GitHub API, 1 October 2026, 18:36 +07; the feed itself not opened. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 1 Oct

    RegistrySearch-only
Six copy entries
  • CVE Brief: Pages for three records

    CVE-2026-51994 · CVE-2026-51996 · CVE-2026-51997View ↗

    Details

    How this was read Three pages opened; two returned 404; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    CopyVerified
  • mr-newbe (security and AI update): Daily digest item naming the mcp-remote record scored 9.1

    CVE-2026-51994View ↗

    Details

    How this was read Page opened; last read 1 October 2026, 19:40 +07.

    read 1 Oct

    CopyVerified
  • YSheldon/0dayWatchDog: Crawler and collector reports

    All five recordsView ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51994, CVE-2026-51995, CVE-2026-51996, CVE-2026-51997, CVE-2026-52001; last read 1 October 2026, 19:06 +07.

    read 1 Oct

    CopyVerified
  • wooluo/vuln_crawler: Multi-source vulnerability crawler reports

    All five recordsView ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51994, CVE-2026-51995, CVE-2026-51996, CVE-2026-51997, CVE-2026-52001; last read 1 October 2026, 19:06 +07.

    read 1 Oct

    CopyVerified
  • Intake bots of Sattyam Jain's projects: Bot tickets for CVE-2026-51995 and CVE-2026-51997 (in agent-audit-kit)

    CVE-2026-51995 · CVE-2026-51997View ↗

    Details

    How this was read Issues read through the GitHub API; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    CopyVerified
  • CVE Brief: Daily digest of 27 September carries CVE-2026-51994 and CVE-2026-51997

    CVE-2026-51994 · CVE-2026-51997View ↗

    Details

    How this was read Digest page read directly; receipt cvebrief-digest-0927.

    read 2 Oct

    CopyVerified

Day 2

Five copy entries
  • mayankfct/cve-hub: Daily CVE data files

    CVE-2026-51994 · CVE-2026-51997View ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51994, CVE-2026-51997; last read 1 October 2026, 19:06 +07.

    read 1 Oct

    CopyVerified
  • parag-samant/Vulnerability-advisory-automation-: Vulnerability advisory automation

    CVE-2026-51994View ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51994; last read 1 October 2026, 19:06 +07.

    read 1 Oct

    CopyVerified
  • Intake bots of Sattyam Jain's projects: Bot ticket for CVE-2026-51994 (in agent-audit-kit)

    CVE-2026-51994View ↗

    Details

    How this was read Issue read through the GitHub API; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    CopyVerified
  • by this date

    flying-coyote/nvd-csv: Daily CSV conversion of the CVE List lists two of the records as updated on 25 September

    CVE-2026-51994 · CVE-2026-51997View ↗

    Details

    Repository description: 'CVEProject/cvelistV5 JSON converted to CSV, daily'. The last three commits are by github-actions[bot] with the message 'chore: daily CVE refresh <date> [auto]'. The run_utc column of the two rows reads 2026-09-26T12:01:40+00:00.

    How this was read pinned file opened through the GitHub API (blob 23f458f2, 224,811 bytes) and the two rows read; repository description and the last three commits read. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 16 Oct

    CopyVerified
  • by this date

    Vulners: Vulners carries all five records with the official CVSS where shown and its own 'Vulners AI Score' of 5.8 to 6.8 (Medium risk) on each

    All five recordsView ↗

    Details

    Pages sit behind a Cloudflare challenge for tools (403), readable only in a browser; this reading replaces the 'unreachable' row of 1 October. The AI score is labelled as the vendor's own and is not recorded as a divergence; the CVSS block was not in view on the 51995 and 52001 pages (EPSS shown in its place), not read as absent. Date basis: the earliest 'Current' timestamp shown (25-26 September).

    How this was read browser (Claude in Chrome), the five record pages opened and the score blocks read from screenshots. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 27 Oct

    CopyVerified

Day 1

  • CISA: ADP Vulnrichment: CVE-2026-51994 scored 9.1, Critical; CVE-2026-51997 scored 8.8, High

    CVE-2026-51994 · CVE-2026-51997View ↗

    Details

    SSVC for CVE-2026-51994: exploitation none, automatable yes, technical impact total. For CVE-2026-51997: exploitation none, automatable no, technical impact total.

    How this was read CISA's container in the two CVE records; last read 1 October 2026, 17:50 +07.

    read 1 Oct

    RegistryVerified
  • by this date

    OSV: A record for each of the five, the first by 25 September

    All five recordsView ↗

    Details

    How this was read OSV API read for each record; the dated public copy opened; last read 1 October 2026, 20:02 +07. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 1 Oct

    RegistryVerified
  • by this date

    CIRCL Vulnerability-Lookup: CVE-2026-51994 by 25 September; all five seen on 1 October

    All five recordsView ↗

    Details

    How this was read CIRCL API read for each record; last read 1 October 2026, 17:51 +07. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 1 Oct

    RegistryVerified
  • by this date

    ENISA EUVD: Five entries, EUVD-2026-86017 to EUVD-2026-86021

    All five recordsView ↗

    Details

    How this was read EUVD API read for each entry; the mirror's file opened; last read 1 October 2026, 19:06 +07. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 1 Oct

    RegistryVerified
  • by this date

    NVD (NIST): CVE-2026-51994 held as Deferred: no CPE configuration, no NVD-own score, not in KEV; the CVSS 9.1, SSVC and CWE-918 on the record are the CISA-ADP values

    CVE-2026-51994View ↗

    Details

    The HTML page returns a title-only shell to fetchers; the API is the readable surface. The other four records were not re-read through the API this pass.

    How this was read NVD 2.0 JSON API (services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-51994) read 15 October 2026, 22:16 +07; receipt nvd-51994-api in evidence/2026-10-15-horizon-sweep.json. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 15 Oct

    RegistryVerified
  • by this date

    Sonatype Guide: Sonatype Guide shows its own scores on four of the five records: 9.6 for CVE-2026-52001, 8.8 for CVE-2026-51994, 0.0 for CVE-2026-51996 and CVE-2026-51997

    CVE-2026-51994 · CVE-2026-51996 · CVE-2026-51997 · CVE-2026-52001View ↗

    Details

    Vendor database, no named author; a 'Sonatype Research' heading with an empty body. Pages show 'Published Sep 25, 2026'. The reference list on the CVE-2026-51994 page includes the research repository's F-01 and F-08 advisory files. Found by the deep-research run of 27 October (research_notes/Mcp remote reception and industry/).

    How this was read CVE-2026-52001 and CVE-2026-51994 pages opened by curl at 2026-10-27T06:52:25Z and 06:52:27Z; the 9.6 and 8.8 values and both vectors read from the page text. The 0.0 values for CVE-2026-51996 and CVE-2026-51997 were read by the research run of the same day (notes file english-writeups.md, ~04:59Z) and not re-opened. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 27 Oct

    DivergenceVerified
  • by this date

    cvefeed.io: CVEFeed's page for CVE-2026-51994 lists 'Update mcp-remote to a patched version' as a solution

    CVE-2026-51994View ↗

    Details

    The page shows last modified 2026-09-25T19:17:26Z. The solution text is unlabelled; no author shown. cvefeed.io already stands in lane A as a copy. Found by the deep-research run of 27 October.

    How this was read page opened by curl at 2026-10-27T06:52:29Z; both solution sentences and the 9.1 score read from the page text. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 27 Oct

    DivergenceVerified
Fifteen copy entries
  • STACKFLAG: Service-account post on Bluesky about CVE-2026-51994

    CVE-2026-51994View ↗

    Details

    How this was read Post read through the Bluesky public API; last read 1 October 2026, 17:36 +07.

    read 1 Oct

    CopyVerified
  • by this date

    CVETodo: Pages for the five records

    All five recordsView ↗

    Details

    How this was read Five pages opened; last read 1 October 2026, 20:01 +07. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 1 Oct

    CopyVerified
  • by this date

    vuln.today: Card for CVE-2026-51994

    CVE-2026-51994View ↗

    Details

    The page labels its own analysis, and a 6.5 score of its own, 'vuln.today AI'.

    How this was read Page opened; last read 1 October 2026, 20:01 +07. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 1 Oct

    CopyVerified
  • MindPattern: Wire item that names the research repository

    CVE-2026-51994 · CVE-2026-51996 · CVE-2026-52001View ↗

    Details

    How this was read Page opened; last read 1 October 2026, 20:01 +07.

    read 1 Oct

    CopyVerified
  • pranava0x0/vibe-coding-security: Advisory file covering the records

    All five recordsView ↗

    Details

    The pull request is titled 'sweep 2026-09-25' and its text carries an AI-tool marker.

    How this was read Page opened; commit and pull request read through the GitHub API; last read 1 October 2026, 17:55 +07.

    read 1 Oct

    CopyVerified
  • Agent-Threat-Rule/agent-threat-rules: Five rule-proposal files generated from NVD

    CVE-2026-51994View ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51994; last read 1 October 2026, 19:06 +07.

    read 1 Oct

    CopyVerified
  • by this date

    RogoLabs/consensus-engine: Tracker of CVSS scoring divergence between NVD and GitHub Advisory

    CVE-2026-51994View ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51994; last read 1 October 2026, 19:06 +07. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 1 Oct

    CopyVerified
  • aboutcode-org/aboutcode-mirror-euvd: Mirror of the European Union Vulnerability Database

    CVE-2026-51994View ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51994; last read 1 October 2026, 19:06 +07.

    read 1 Oct

    CopyVerified
  • password123456/nvd-cve-database: CVE database files

    All five recordsView ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51994, CVE-2026-51995, CVE-2026-51996, CVE-2026-51997, CVE-2026-52001; last read 1 October 2026, 19:06 +07.

    read 1 Oct

    CopyVerified
  • timothee-chauvin/eyeballvul_data_sources: Data sources used to build eyeballvul

    CVE-2026-51994View ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51994; last read 1 October 2026, 19:06 +07.

    read 1 Oct

    CopyVerified
  • westonsteimel/national-vulnerability-database: JSON data from the NVD vulnerabilities API

    CVE-2026-51994View ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51994; last read 1 October 2026, 19:06 +07.

    read 1 Oct

    CopyVerified
  • xhls008/nvd_yesterday: Daily list of the previous day's new CVEs

    CVE-2026-51995View ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51995; last read 1 October 2026, 19:06 +07.

    read 1 Oct

    CopyVerified
  • yarencheng/cve-devops-playground: CVE pages

    CVE-2026-51994View ↗

    Details

    How this was read File found by GitHub code search and opened at its pinned address; it names CVE-2026-51994; last read 1 October 2026, 19:06 +07.

    read 1 Oct

    CopyVerified
  • by this date

    Anchore (CVE datasets): Three CVE datasets Anchore keeps for its data curation

    CVE-2026-51994View ↗

    Details

    How this was read Files found by GitHub code search and opened at their pinned addresses; last read 1 October 2026, 19:06 +07. The source shows this date as a last-modified or first-sighting time; the entry may be older.

    read 1 Oct

    CopyVerified
  • TrueNix/website: al-ice.ai editorial 'Five mcp-remote CVEs Say "Arbitrary Code Execution." The Research They Cite Does Not.' (source repository TrueNix/website)

    All five recordsView ↗

    Details

    Supersedes the collector's row for the source repository: the live page is the better address, the content is now classified. The post's reading of the CNA wording is the source's own; the records stand as published. The repository file was last committed 2026-10-20 in a multi-post commit; the article carries no 'updated' note. Found by the deep-research run of 27 October.

    How this was read live page opened by curl at 2026-10-27T06:52:46Z; the byline, the post date 2026-09-25, the quoted sentence and the 'not a reproduction' sentence read from the page text.

    read 27 Oct

    CopyVerified

Day 0

  • CVE Program (MITRE): Five records published

    All five recordsView ↗

    Details

    Published with MITRE as the assigning authority. Each record links an advisory file in the research repository. The structured affected field names no product (vendor n/a, product n/a) and the records carry no credit line.

    How this was read CVE Services API read for each record; last read 1 October 2026, 17:51 +07.

    read 1 Oct

    RegistryVerified
  • CISA: ADP Vulnrichment: CVE-2026-51995 scored 7.5, High

    CVE-2026-51995View ↗

    Details

    CISA added a score and an SSVC decision to the record: exploitation none, automatable yes, technical impact partial.

    How this was read CISA's container in the CVE record; last read 1 October 2026, 17:50 +07.

    read 1 Oct

    RegistryVerified
  • NVD (NIST): Five records listed

    All five recordsView ↗

    Details

    How this was read NVD API read for each record; last read 1 October 2026, 17:52 +07.

    read 1 Oct

    RegistryVerified
  • GitHub Advisory Database: Five advisories imported, unreviewed

    All five recordsView ↗

    Details

    How this was read GitHub advisories API read for each record; last read 1 October 2026, 17:51 +07.

    read 1 Oct

    RegistryVerified
Sixteen copy entries

Divergences

Where a third party states something the records do not support, or shows a score or label they do not carry.
SinceWhoWhat they stateWhat the record showsState
On whether a fix exists
cvefeed.ioSolution section of the CVE-2026-51994 page: 'Update mcp-remote to a version that addresses the SSRF vulnerability.' and 'Update mcp-remote to a patched version.'No fixed release has been stated by the maintainer of mcp-remote for any of the five records; releases through 0.15.2 of 20 October 2026 state no fix, and the records carry no fixed version.open
Upwind (Roy Kalfon)'Update to 0.1.38 or disabling external access to the service to mitigate.'The record lists 0.1.16 through 0.1.38 as affected, so 0.1.38 is inside the range. No fixed version is established.open
CVE BriefFix available: Yes (OSV.dev). Seen on its page for CVE-2026-51997 on 30 September and on its pages for CVE-2026-51994 and CVE-2026-51996 on 1 October.The fix OSV points to is the 0.1.38 release, the last version the records list as affected.open
FeedlyA patch is available, per the GitHub advisory. The wording varies across the five pages.The GitHub advisories carry no package and no patched version, and no maintainer has stated a fix.open
OpenCVERecommended Actions on the CVE-2026-51996 page: upgrade MCP-Remote to the latest patched release, e.g. 0.1.39 or newer; the page header lists the action as Immediate Patch.No fixed release has been stated by the maintainer of mcp-remote for any of the five records; the records list affected versions through 0.1.38, and 0.1.39 is the version number after that bound. Releases through 0.15.2 of 20 October 2026 state no fix. The same page's Remediation section reads 'No solution or workaround provided in the CVE record.'open
SentinelOne Vulnerability DatabaseRemediation on the CVE-2026-51994 page: upgrade mcp-remote to a version later than 0.1.38 that validates resource_metadata targets, per the project security advisories.No fixed release has been stated by the maintainer of mcp-remote for any of the five records; releases through 0.15.2 of 20 October 2026 state no fix, and the records carry no fixed version.open
adudley78/mcp-auditEach of the five entries carries fixed_in: 0.1.39 and the words 'first unaffected release 0.1.39'.No fixed release has been stated by the maintainer of mcp-remote for any of the five records; the records list affected versions through 0.1.38, and 0.1.39 is the version number after that bound. The project's pull request #152 says fixed_in is computed by its sync script from range bounds, with last_affected ranges treated as bounded. Releases through 0.15.1 of 14 October 2026 state no fix.open
OSVUntil 21 October: introduced 0.1.32 (0.1.16, 0.1.18 by record), fixed 0.1.38, source DESCRIPTION; the GIT range ended at commit 02619aff marked fixed.Read 21 October 12:44 +07: on all five records the GIT range ends with last_affected 02619aff (the 0.1.38 release) and the extracted DESCRIPTION range reads last_affected 0.1.38; where OSV lists versions, v0.1.38 is now included. OSV modified all five at 2026-10-21T02:58Z. The CVE records themselves are unchanged (dateUpdated 24 September to 6 October).corrected
Scores, labels and mappings the records do not carry
Sonatype GuideCVE-2026-52001 page: 9.6 Critical, CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, source given as National Vulnerability Database. CVE-2026-51994 page: 8.8 High, CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. CVE-2026-51996 and CVE-2026-51997 pages: CVSS score 0.0, rated None, vector Not available, Published: Unavailable.The CISA-ADP scores in the records, as published and as carried by EUVD on 27 October 2026: CVE-2026-52001 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), CVE-2026-51994 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), CVE-2026-51996 9.8, CVE-2026-51997 8.8. The affected ranges on the Sonatype pages match the records.open
HOL GuardcweIds CWE-94, CWE-328The record's only weakness is CISA's CWE-328; MITRE gives none, and NVD lists CWE-328 only.open
Intake bots of Sattyam Jain's projectsCWE: CWE-94The record's only weakness is CISA's CWE-328; MITRE gives none, and NVD lists CWE-328 only.open
TenableCVSS v3 7.5 for CVE-2026-52001 (seen 30 September), and a CVSS v2 score on each of the five pages (9.4, 7.8, 10, 10 and 5; seen 1 October). The pages list Mitre and NVD as their source.At the 30 September / 1 October checks, CVE-2026-52001 had no official score; CISA had scored the other four in CVSS v3.1. Update added 8 October 2026: CISA added CVSS v3.1 7.5 High on 6 October, so Tenable's previously observed 7.5 now agrees with that assessment. The earlier CVSS v2 provenance discrepancy remains recorded; this update does not recheck Tenable's current pages.v3 score aligned; v2 not rechecked
BaseFortifyVendor: playb0t; product: mcp-remote.playb0t is the handle of the research author, not the vendor of the package.open
HOL GuardEach of the four scored records is described as a vulnerability 'in CISA ADP Vulnrichment'. The page for CVE-2026-52001 is a stub that says the source record is being verified.CISA ADP Vulnrichment is the programme through which CISA adds SSVC decisions, CVSS scores and weakness classes to CVE records; it is not a product. CVE-2026-52001 has been a published record since 24 September.open
Mend.ioA CVSS v4 base score on each of its four pages (9.3, 8.7, 9.3 and 8.7).The records carry CISA's scores in CVSS v3.1 only; they hold no v4 score.open
OffSeq Threat RadarSeverity: medium, for CVE-2026-52001.At the 1 October check, the record carried no score from MITRE or CISA. Update added 8 October 2026: CISA added CVSS v3.1 7.5 High on 6 October. OffSeq's medium label above is the historical observation; its current page has not been rechecked.historical; current label not rechecked
Positive Technologies (dbugs)The entry for CVE-2026-51997 is headed 'Pypi · Mcp-Remote'.The record names geelen mcp-remote, and the package is published on npm.open
pranava0x0/vibe-coding-securityCVE-2026-51995 belongs to finding F-10, and F-02 has no CVE listed.The CVE record references the F-02 advisory; the merged page now says the same.corrected
jvlatacc/vigil (obvious-autobuild bot)An agent-written pull request pins mcp-remote at 0.1.49, reading 0.1.39+ as the "apparent remediation level" from the records' "through 0.1.38" wordingPR #63 (opened 2026-10-09 21:50Z by obvious-autobuild[bot], merged 22:06Z) names all five records by id and class, keeps the pin at 0.1.49 "with a recorded caveat": the records are "reported against releases through 0.1.38, with 0.1.39+ the apparent remediation level", citing incomplete upstream fixed-metadata and Snyk listing no known vulnerabilities for later releases; it names retiring the bridge for an in-process streamable-HTTP client as the durable follow-up. No fixed release exists; the inference comes from the written range alone, which is what the range-update requests filed with MITRE on 10 October address.open
OSVEach record has one affected entry with a GIT range on punkpeye/mcp-remote and no package field.The package is published on npm as mcp-remote; with no package entry, OSV-fed scanners matching npm name and version do not fire from the records (row package-match of 1 October).open
GIRD (aegis-mesh/blindspot)The researcher's write-ups 'claim less than the advisories' text'; for GHSA-mvq8 (51996) and GHSA-v65w (51997) the lines say 'a weak hash, MD5, keeps the saved tokens of each server apart' and 'a hostile server could open an internal address in your browser', each with the aside '(its text says code execution)'.The CNA descriptions of CVE-2026-51996 and CVE-2026-51997 state that a remote attacker can execute arbitrary code; the CISA-ADP scores are 9.8 and 8.8. The official wording and scores stand as published.open

As recorded in the ledger of 18 November 2026. The record is the reference in every row; the wording and the scores of the official records are taken as they stand and are never listed here.

Checked, no mention found

Places where the records could be mentioned and, at the last check, were not, or could not be read. An entry here records silence so far.

The source answered: no mention of the records

  • Academic indexesNo paper, preprint, thesis or standards draft cites the records or the repository in domain-restricted searches on 27 October; Semantic Scholar and arXiv APIs rate-limitedqueries and results listed in research_notes/Mcp remote reception and industry/databases-scanners-academic.md, read 2026-10-27T04:50Z to 05:10Z
  • Alibaba Cloud (OpenAPI MCP Server and CloudControl MCP Server guides)Both Alibaba Cloud MCP guides still tell users to run mcp-remote-alibaba-cloud with no version pinned, and no package-mapped GitHub Security Advisory exists for the fork. Alibaba's security team was notified on 3 October, support forwarded the report to the product teams on 15 October, and the Alibaba Security Response Center acknowledged it on 20 October; the guide pages are unchanged on 1 November1 November: both guide pages fetched with curl, HTTP 200; the OpenAPI guide names mcp-remote-alibaba-cloud 3 times with no @version and shows 'Updated: Aug 20, 2026'; the CloudControl guide names it 4 times with no @version; the same counts as 15, 19 and 21 October (case file 138). gh api advisories?ecosystem=npm&affects=mcp-remote-alibaba-cloud returned no advisory. Dates of the notice, forwarding and acknowledgement from case files 138 and 180
  • Arch Linux security trackerThe Arch Linux security tracker lists the mcp-remote package at 0.8.3-1 with no issues; none of the five records appearsWebFetch of the package page in this pass; the page answered with the package version and the 'No issues' line
  • CISA KEVNone of the 5 records is in the Known Exploited Vulnerabilities catalog (catalog of 17 November, 1,782 entries).collector reading of the source API, 2026-11-18T10:59:01+07:00
  • Continue (@continuedev/cli, acquired by Cursor)@continuedev/cli 1.5.47, the latest release, carries no deprecation notice on npm, and its HTTP 401 fallback still launches mcp-remote with no version pinned. The author reported it privately to Continue on 10 October; the repository is read-only and the report is unchanged since filing. On 16 October the author reported it to Cursor through its disclosure channel; it was closed the same day as out of scope18 October: registry.npmjs.org/@continuedev%2fcli (latest 1.5.47 of 2026-06-18, no deprecated field); gh api contents MCPService.ts on main, line 445 ["-y", "mcp-remote", serverConfig.url]; README of continuedev/continue line 19 'no longer actively maintained and is read-only for all users'; continuedev/continue-home description 'Static archive of continue.dev (acquired by Cursor)'; the author's advisory GHSA-8wr2-vqq5-mqq6 state triage, updated_at equal to created_at 2026-10-10T12:11:06Z; the closure from the operator's screenshot of 16 October (case file 126)
  • Daily web checkThree web searches on 18 November for the record identifiers, the research repository and the package's OAuth flaws return no new write-up or project changeWebSearch x3 (standard) on 2026-11-18; five unlisted hits fetched with curl and grepped for the five ids, one third-party record id, mcp-remote, playb0t and the repository name
  • FortiGuard LabsFortiGuard IPS entry 58455 is the 2025 record's signature (CVE-2025-6514, versions 0.0.5 through 0.1.15, removed in version 35.182 of 11 March 2026); it names none of the five recordspage opened in the in-app browser and its text read (signature name, CVE ID, affected versions, version history); clock read right after the page read
  • GitHub Advisory DatabaseMapping pull requests #10204–#10208 (npm package mcp-remote for the five records) open with no review: 0 reviews and 0 requested reviewers on each; last activity 10 October (#10204, #10205) and 7 October (#10206–#10208). The GHSA entries stay unreviewed, so no package mapping and no Dependabot alert.GitHub API reads of pulls 10204–10208 and their reviews, 15 October 2026, 22:16 +07; receipt github-advisory-prs in evidence/2026-10-15-horizon-sweep.json
  • GitHub Advisory Database (TypeScript SDK advisory GHSA-6prh-2h8m-c8cw)CVE-2026-111769 of 20 October names stdio clients as unaffected and does not name mcp-remoteAdvisory read through the GitHub advisories API 21 October; mcp-remote 0.15.1 and 0.15.2 tarballs downloaded from the npm registry the same day and compared file by file
  • GitHub Advisory Database, npm audit, Dependabot, deps.dev, OSV, Snyk, GitLabThirty-six days after publication, these seven sources still report mcp-remote 0.1.38, 0.14.3 and 0.15.2 as clean: the five GitHub advisories are unreviewed with no package mapping, so npm audit and Dependabot are silent; deps.dev and OSV list nothing; Snyk and GitLab list only CVE-2025-6514. Third-party tools listed in this record do flag the package: agent-audit-kit, mcp-audit, RustMachineGuard and Blindspot.gh api advisories/<ghsa> for the five ids and pulls 10204-10208; POST registry.npmjs.org/-/npm/v1/security/advisories/bulk; api.deps.dev v3 version records; api.osv.dev v1 query; Snyk and GitLab package pages fetched and searched for CVE ids; 30 October 2026, 18:41 +07; receipt in evidence/2026-10-30-section05-recheck.json
  • GitHub DiscussionsNo discussion names the record identifiers or the repository.GitHub search queried; the one loose hit opened; last read 1 October 2026, 17:55 +07
  • GitHub issues and pull requestsA search of public GitHub for every identifier, the five GitHub advisory ids and the research repository finds third-party issues and pull requests that cite one in eight projects only: agent-audit-kit, agent-airlock, mnemo, vibe-coding-security, vigil, northstar-agent-os, mcp-remote-aliyun and Blindspot, all listed in this record.gh search issues with the exact phrase of each identifier, pull requests included, the author's own excluded; each of the 23 hits opened through the API and read for an identifier, 22 carry one; 30 October 2026, 18:39-18:40 +07; receipt in evidence/2026-10-30-section05-recheck.json
  • Hacker News (Algolia search)No story or comment names the records or the repositoryAlgolia API read 21 October, first page of 37 hits
  • Mastodon, Lobsters, YouTubeNo post, story or video names the records on Hacker News, Lobsters, Mastodon, YouTube, podcasts, dev.to, Medium, Substack, Beehiiv, Hashnode, HackerNoon, LinkedIn or X (web index) on 27 Octoberqueries and results listed in research_notes/Mcp remote reception and industry/social-reception.md, read 2026-10-27T04:55Z to 06:22Z
  • National CERTsNo entry for the records at JPCERT/JVN, CERT-FR, BSI/CERT-Bund, NCSC-UK, CERT-EU, ACSC, CCCS, CERT-In, KISA/KrCERT, CNVD/CNNVD, CERT.PL, ACN, USOM, CCN-CERT, CSIRT CL or CERT.br in domain-restricted searches on 27 Octoberqueries and results listed in research_notes/Mcp remote reception and industry/databases-scanners-academic.md, cjk-sources.md and european-sources.md, read 2026-10-27T04:52Z to 05:04Z
  • Non-English sites and social postsChinese, Japanese, Korean, Russian, German and Spanish sweeps on 27 October find no page naming the records beyond INCIBE-CERT and the Chinese Telegram feed already recordedqueries and results listed in research_notes/Mcp remote reception and industry/cjk-sources.md and european-sources.md, read 2026-10-27T04:52Z to 05:04Z
  • OSV and deps.dev, by packageAsked about the npm package itself, OSV returns no vulnerability for version 0.1.38 or 0.1.16, and only the 2025 record CVE-2025-6514 for the package as a whole; deps.dev attaches no advisory to 0.1.38. The five records are not tied to the package in either.OSV package query and deps.dev version record read; last read 1 October 2026, 18:36 +07
  • Practical DevSecOps (Varun Kumar)MCP Security Statistics 2026 report — names mcp-remote only for CVE-2025-6514Page fetched and read 21 October
  • Protocol pivoting coverage (Mohiuddin update, Unite.AI, TechTimes)The October 2026 protocol-pivoting update and its press coverage name five organisations' MCP servers and CVE-2026-14540; none of them mentions mcp-remote or the five recordsUpdate page and Unite.AI article opened through the fetch tool during the 7 October judgment pass, after the collector run of 21:05:51+07:00; CVE-2026-14540 read at cveawg.mitre.org (Google CNA, CVSS 4.0 8.0 High, published 2026-07-31)
  • Red Hat, Ubuntu, SUSE, Arch, Amazon Linux, Oracle LinuxNo CVE page for any of the five records at Red Hat, Ubuntu, SUSE, Amazon Linux or Oracle Linux (404 or 'Not Found') on 27 October; Arch lists the package at 0.8.3-1 without the recordslookups listed in research_notes/Mcp remote reception and industry/databases-scanners-academic.md, read 2026-10-27T04:55Z to 05:04Z
  • Scanner and exploit contentNo Nessus plugin, no template in ProjectDiscovery's nuclei-templates and no entry in Exploit-DB. The two public proof-of-concept indexes now list records, each pointing only at the research repository: nomi-sec/PoC-in-GitHub (CVE-2026-51994) and trickest/cve (CVE-2026-51994, -51995 and -52001, with 'No PoCs found on GitHub currently'); both are listed in this record.Tenable CVE page data for the five ids, the nuclei-templates paths and a code search of that repository, the Exploit-DB file list, and both index repositories read through the GitHub API; 30 October 2026, 18:37-18:38 +07; receipt in evidence/2026-10-30-section05-recheck.json
  • Security pressNo bylined article names the records: domain-restricted sweeps of eleven security outlets and sixteen vendor blogs and newsletters on 27 Octoberqueries and results listed in research_notes/Mcp remote reception and industry/english-writeups.md and industry-advisories-incidents.md, read 2026-10-27T04:48Z to 06:38Z
  • SnykThe package page lists one advisory, for the 2025 record CVE-2025-6514 (SNYK-JS-MCPREMOTE-10734125), and none of the five.Package page opened and searched for CVE and SNYK identifiers, 15 October 2026, 22:16 +07; receipt snyk-package in evidence/2026-10-15-horizon-sweep.json
  • The Vulnerable MCP Project (vineethsai)Database lists one mcp-remote entry, CVE-2025-6514; none of the five recordsPage fetched and read 21 October
  • Upstream fixUpstream released 0.16.6 on 11 November 2026 (https required for the device grant, and credential-bearing requests kept from following a redirect to another origin); measured on 14 November, all seven original findings remain present, the note names none of the five records, and no fixed release is stated by the maintainergh api read of the release v0.16.6, the comparison v0.16.5...v0.16.6 (one commit, eleven files) and src/lib/endpoint-policy.ts at the tag; the 0.16.6 and 0.1.38 archives downloaded from the npm registry by the brain and matched to the published acquisition files by sha256 and integrity; the published folder docs/research-2026-11-14 downloaded as the repository archive at commit 3510446 and recomputed by the brain: manifest 265 of 265, 175 JSON files parsed, no machine paths or credential-shaped strings, verdict counts recounted from the per-case records (11 scenarios 9 pass and 2 fail on 0.16.6; cache series 13/2/3, 0/2/1, 1/2/0), 19 component conditions, the paired F-11 rows for 0.1.38 and 0.16.6 and the three F-08 full-CLI cases read from the records, the 0.16.5 reference of 7 pass and 4 fail read in the 7 November v2 package (case files 260 and 262)
  • Vendor research blogsNo research post names the records: JFrog, Qualys, CrowdStrike, Unit 42, Microsoft, Black Duck, Checkmarx, Debricked, Cyble, SecurityScorecard, Socket, Trail of Bits, Invariant, Koi, Straiker, Pillar, Cycode, Obsidian checked on 27 Octoberqueries and results listed in research_notes/Mcp remote reception and industry/databases-scanners-academic.md and industry-advisories-incidents.md, read 2026-10-27T04:50Z to 06:38Z
  • Waseem Anjum (dev.to)MCP Security in 2026: The OAuth SDK CVEs, Tested — names mcp-remote only for CVE-2025-6514Page fetched and read 21 October
  • WizNo vulnerability-database page for any of the five records (page not found) on 27 October; Recorded Future, DevGuard and Chainguard likewiselookups listed in research_notes/Mcp remote reception and industry/databases-scanners-academic.md, read 2026-10-27T04:55Z to 05:10Z

Searched, not opened

  • NewslettersNo newsletter item naming the records found in a web search on 26 October; the search returned only registry, scanner and press pages already in the ledger.Search only, 26 October 2026 (three web searches on the record identifiers, the research repository name and mcp-remote OAuth newsletter coverage); sources not opened one by one
  • Published forks of the packageNone of ten npm packages published as forks of mcp-remote mentions the records or any advisory.Search only, 1 October 2026; the sources were not opened one by one
  • RedditNo post names the record identifiers in r/netsec, r/mcp, r/cybersecurity, r/ClaudeAI or r/AI_Agents (archive search of posts; comments not searched).Search only, 1 October 2026; the sources were not opened one by one

Not reached

  • BDU FSTECBDU FSTEC (bdu.fstec.ru) not reachable: TLS handshake fails from the browser and from curl; HTTP redirects to HTTPS
  • Closed databasesVulners (its pages were seen in a browser, not verified), CVE Details, VulDB and Socket answer automated requests with a challenge page; VulnCheck asks for a sign-in; China's CNVD and Russia's BDU did not answer. What they carry is not established here.One request to each; last read 1 October 2026, 18:36 +07
  • SocketThe alerts page for mcp-remote 0.15.1 refused the request (HTTP 403); whether Socket lists the five records is not established.Fetch attempted 15 October 2026, 22:16 +07, HTTP 403; receipt socket-alerts-0151 in evidence/2026-10-15-horizon-sweep.json

The same classes, fixed elsewhere

Independent advisories in the official MCP SDKs for the kinds of flaw this research reported. They do not cite it, so they are not entries in the record above.

Others found and fixed related flaws, on the same trust boundaries, in the official MCP SDKs. None of these advisories cites this research; they are independent findings, reported to those projects by other people. The dates are the advisories' publication dates, set beside the research's own dates so a reader can compare them; a related advisory is not the same finding. The research dates come from its public timeline. The research timeline.

DateWhereAdvisoryWhat it saysFixed in
F-01 · CVE-2026-51994: The client fetches a URL the server named during OAuth discovery
This research17 Feb 2026 reported privately to the maintainer; 31 Jul 2026 published; 24 Sep 2026 CVE record
MCP Rust SDK (rmcp)GHSA-c9xm-49cp-xcr9rmcp OAuth client fetches server-controlled resource_metadata URLsrmcp 2.0.0
MCP Ruby SDKGHSA-4m5j-jjfc-97gxOAuth discovery security check allows SSRF to private hosts over HTTPSmcp 1.2.0
MCP Python SDKGHSA-rwrf-2pqf-9j8jClient fetched server-chosen $ref URLs while validating tool results against output schemasAdjacent: a server-chosen URL outside the OAuth flow.mcp 1.30.0, 2.2.0
F-02 · CVE-2026-51995: The client trusts the authorization server the MCP server names (related advisories bind credentials to the expected issuer)
This research17 Feb 2026 reported privately to the maintainer; 3 May 2026 localhost proof; 31 Jul 2026 published; 24 Sep 2026 CVE record
MCP Python SDKGHSA-qx49-fqc8-xw99OAuth client could send credentials to an authorization server chosen by the MCP serverRelated, not the same finding: the fix binds credentials to the expected issuer.mcp 1.30.0, 2.2.0
MCP TypeScript SDKGHSA-6qxp-vccf-f47hCVE-2026-104850OAuth client could send credentials to an authorization server chosen by the MCP serverRelated, not the same finding: the fix binds credentials to the expected issuer.@modelcontextprotocol/sdk 1.31.0, @modelcontextprotocol/client 2.2.0
F-10: Redirects to another origin: the research's finding is about checking each new destination
This research3 May 2026 added to the private report; 31 Jul 2026 publishedF-10 has no CVE in this batch.
MCP Rust SDK (rmcp)GHSA-9g45-5xwm-f3wcCVE-2026-64684Custom HTTP headers leak to cross-origin redirect targetsSame redirect boundary, different mechanism: headers and bodies carried across origins.rmcp 2.1.0
MCP Python SDKGHSA-5h93-6whr-6q8jHTTP client transports followed cross-origin redirects carrying custom headers and bodiesSame redirect boundary, different mechanism: headers and bodies carried across origins.mcp 1.30.0, 2.2.0
MCP TypeScript SDKGHSA-6prh-2h8m-c8cwHTTP client transports and OAuth requests followed cross-origin redirects and re-sent custom headers and request bodiesSame redirect boundary, different mechanism: headers and bodies carried across origins.@modelcontextprotocol/sdk 1.32.0, @modelcontextprotocol/client 2.3.0

Every advisory row: Repository security advisory read through the GitHub API; last read 3 October 2026, 12:40 +07.

mcp-remote builds the SDK into its own release. The published 0.14.3 package (21 September 2026, the latest) carries @modelcontextprotocol/client 2.0.0: six module markers in its bundle, package integrity matched npm. 0.1.38 pins @modelcontextprotocol/sdk 1.25.3 in its lockfile. Both sit inside the affected ranges of both TypeScript SDK advisories above (read 3 October 2026).

How to read this page

What an entry needs. A date, a source and a status. Verified means the source was opened and the page, file or record itself names one of the records, the research repository or the author. Search-only and searched, not opened mean it was found, or ruled out, through a search engine or another site's listing, and the source itself was not opened. Unreachable and not reached mean the page refused the request or could not be read.

What the date is. The date the source gives for its own act: a publication time, a commit, a release date, a first-seen line on its own page. A database page that shows only the record's own publication date sits on the day it was first seen, and says so. A divergence sits on the date the source gives for the statement itself; where the source dates only its page, it sits on the day the statement was first seen. By this date marks a source that shows only a last-modified time, or a log of when something was noticed elsewhere. Dates are UTC; the times of reads are UTC+07.

Copies and work are counted apart. A copy reproduces a record or the research repository: a mirror, a feed, a page a site generates for every CVE, a bot ticket, a machine-written summary, an unsigned digest item, a fork. Work is something a named author or project did with the records: a bylined write-up, a change in a project. Much of it is produced with AI tools; where a source says so, the entry says so.

What the numbers count. The headline and the tiles count sources: a site and the repositories of the same organisation count once in a lane, however many entries they have there. A source that appears in two lanes is counted in each. Only verified entries count. The numbers beside the lanes and in the docket count entries.

What counts as a fix. Only the statement of the maintainer of the affected software, in a release note, commit, advisory or issue, that a change addresses one of the records. A database label that says a patch is available is listed under divergences.

What counts as verification. A party other than the author states that it tested and reports the result. Restating the advisory does not count.

What a divergence is. A third party states something the records do not support, or shows a score or label the records do not carry without naming its source. A statement that a patch exists is listed; general advice to update to a patched version is not. The wording and the scores of the official records are taken as they stand and are never listed here.

How it is kept. On each run, listed in the run log, a collector reads the registries, the package index and code search and writes what a machine can establish: a record changed state, a new repository carries the identifiers. Anything that needs a judgment waits for a reviewer who opens the page. Rows are never edited; a correction is a new row that replaces the old one.

Which sources count as registries and databases. The CVE Program, NVD, GitHub's advisory database, OSV, ENISA's EUVD, CIRCL, CISA, national CERTs, the security trackers of Linux distributions, and the vulnerability databases of scanner vendors that security teams query directly: here Tenable, Rapid7, Mend.io, Aqua and Positive Technologies. Any other site that generates a page for every CVE is counted as a copy. Where that line falls is a judgment made for this record. Two of the sixteen list the records without tying them to a package of their own: Debian marks them NOT-FOR-US, and Alpine's tracker shows no matching package.

Counted in two lanes. Aqua Security is counted among the registries for its database pages and among the copies for its NVD data repository. The intake bots of Sattyam Jain's two projects are counted among the copies as one source, and one of those projects, agent-audit-kit, under acted on, for the detection rule merged there. Adam Dudley's mcp-audit is counted under acted on, for the registry entry its advisory check reads, and under divergences, for the fixed version that entry states. pranava0x0/vibe-coding-security is counted among the copies, for its advisory file and its daily sweep, and under acted on, for the corrections and the mapping check made there.

Terms. CNA: the organisation that assigned the identifier. ADP Vulnrichment: the programme through which CISA adds scores and decisions to CVE records. SSVC: CISA's decision points for a record (exploitation, automatable, technical impact). EPSS: FIRST's estimate of the probability of exploitation in the next 30 days. Deferred: the status NVD currently gives the five records; it has added no analysis of its own to them.

One source in two lanes. GIRD (aegis-mesh/blindspot) stands in two lanes: D for shipping version-check rules for four records (27 October 2026), X for describing two of them below the CNA text in the same file.

Run log

When the sources were last read.
Run startedModeRows addedQueued for reviewCould not reach
diff00—
diff23—
diff11—
diff00—
diff14—
diff02—
diff11nvd CVE-2026-51994, nvd CVE-2026-51997
diff00nvd CVE-2026-51995, nvd CVE-2026-51996
diff00nvd CVE-2026-52001
diff21—
diff01—
diff02—
The research repository · dated snapshot

Reach of this research

Traffic to mcp-remote-oauth-security, the published research package behind these five CVE records.

14-day reporting window: to (UTC).

Repository clones
342
Unique cloners (GitHub)
125
Repository views
133
Unique visitors (GitHub)
44

Source: GitHub's authenticated repository traffic API, checked in Asia/Bangkok. This is a dated snapshot, separate from the automatically checked public counters above.

Clones are repository copies, not npm package downloads or proof that someone reviewed the findings. Automated activity may be included; GitHub's unique counts are not verified individual people.

How GitHub reports repository traffic · Open the research package

Research continuation, . The published 0.14.3 CLI was run in full against loopback canaries; selected discovery helpers were executed across 58 stable releases; selected code and namespace signatures from the package were found under 12 other npm package names (8 with reference-function matches, 4 with namespace matches only) and in 8 other Git repositories. Code presence establishes no deployment and changes no published CVE range. Research dossier · Download snapshot and code footprint

Research continuation, . A screen of GitHub for products that launch the bridge at run time covered 457 repositories, kept 438 and read 20 at pinned commits: 14 products, 6 samples or documentation. The same day, private notices went to the maintainers of seven products, six through GitHub private vulnerability reporting and one by email; the product names follow once the notice window closes. Two requests to extend the affected ranges of CVE-2026-51994 and CVE-2026-51995 through 0.14.3 were filed with MITRE and are pending.

Research continuation, . Follow-up by the author: the 9 October procedure repeated on the published 0.15.1 (released 14 October): the same F-01 / F-02 request paths, a token request with an Authorization header to the server-named authorization server in the full trace, ten helper functions byte-identical to 0.14.3, the bundled SDK still client 2.0.0; twelve runs across five versions kept (commit fbd53bf). 0.15.1 follow-up, 15 October 2026

From the author · not part of the ledger

The problem, the five records, and what I am building against it

I found the five flaws on this page, and I build software in the same field, offered under a commercial licence. This section says what that software does about this class of flaw today, what is commissioned and not built yet, and what it does not do. Nothing in the ledger above depends on it.

The author

playb0t on GitHub

Alex Gercog

published as playb0t

Co-⁠Founder & CTO, AI TRIMIND. AI systems engineer and security researcher.

The record

  • Found and reported the flaws behind the five CVE records on this page. Each record cites the research package as a reference.cve.org/CVERecord?id=CVE-2026-51994 (and -51995, -51996, -51997, -52001)
  • CISA scored all five: 9.8 and 9.1 Critical, 8.8, 7.5 and 7.5 High. The fifth score was added on 6 October 2026.the records' CISA-ADP entries
  • The initial private report was submitted on 17 February 2026; F-08 through F-11 were added on 3 May. The public research package was released on 31 July, after the original 90-day window.github.com/playb0t/mcp-remote-oauth-security (TIMELINE.md)
  • The research package, now at v1.0.2, keeps a public corrections file: two findings were reclassified and every proposed severity number was withdrawn in favour of the official assessment.the same repository (CORRECTIONS.md)
  • Published MCP Host Matrix, versioned evidence of how five native MCP hosts and the mcp-remote bridge behave across six directions. Selected disconnect actions did not revoke in 12 of 12 base windows; prior authority survived a build replacement in 8 of 8 cells. Evidence snapshot: 25 October 2026.github.com/playb0t/mcp-host-matrix
  • Earlier work: a SHA-256 integrity check for coding-agent hooks, merged into RTK on 3 March 2026.github.com/rtk-ai/rtk/pull/119
  • Builds coord-hub, described below.

Contact Email w0rldlogic.0point@proton.me · GitHub github.com/playb0t · X @playb_0t · LinkedIn linkedin.com/in/alex-gercog

The problem

mcp-remote performs OAuth discovery on behalf of an MCP client. The research examines several trust boundaries: where discovery can send a request from the user's machine, how local authentication state is separated, and which origin may receive a credential. These are distinct mechanisms. F-01 and F-02 were demonstrated with localhost canaries; F-08 rests on source review; F-04 and F-11 are hardening findings with corrected claims. The official CVE descriptions and CISA scores above are reported as published.

Where disclosure stops working

The latest release of @continuedev/cli, 1.5.47, is still on npm with no deprecation notice. When a server answers 401, it launches mcp-remote with no version pinned, and no release of mcp-remote is stated fixed. I reported this to Continue privately on 10 October. Cursor had acquired Continue, and Continue's repository is now read-only; the report has not moved since the day it was filed. On 16 October I reported it to Cursor through its disclosure channel. It was closed the same day as out of scope.

No one in this chain broke a rule. The flaw sits upstream, in mcp-remote, whose maintainer has stated no fix. The company that owns the package places it outside its scope. The repository that could take a fix accepts no changes. The only party still carrying the risk is the person who installed the CLI, and nothing on npm tells them. A disclosure process in which every step is correct and the risk still ends with the user is broken. Scope lists cover what a company ships today; people keep running what it shipped before. When a company buys a package, the duty to answer for it has to come with the publishing rights.

coord-hub

What I am building

I build coord-hub, a coordination layer for AI agents that belong to different owners. Agents join a shared room only after a person vouches for them, and they hand each other tasks, messages and files. An outward call is carried by a gateway, a separate process that forwards only what a one-time grant names. It is at version 0.1.0, its repository is private, and it is in active development.

An agent's own connection to a remote MCP server still does not pass that gateway, so for an agent that connects on its own the hub as it stands would not have stopped the five flaws on this page. Since 16 October 2026 a remote MCP server a person admits at the hub is discovered and authorized by the gateway itself, under the outbound policy this research asks for; the tokens stay with the gateway.

Works today · in the build's tree, under test

  • For a granted DNS name other than localhost, the gateway resolves once and checks every returned address before fetching a credential. It accepts public addresses by default; the operator can additionally allow private ranges. Other names resolving to loopback, link-local, known cloud-metadata or special-use ranges, or this machine's own interfaces are refused as a whole. Connections to DNS names are pinned to checked addresses. The localhost and explicitly granted IP-literal exceptions are listed under Limits today.

    basis: tests gateway-address DA1–DA12; source read: src/gateway/core.mjs

  • The hub's own outbound calls follow no redirect: a 3xx is recorded as the destination's answer, and nothing is sent where it points. On a call it forwards for an agent, the gateway carries one request for one grant and hands a 3xx back as the answer.

    basis: tests egress-redirect ER1–ER5, gateway GW3; source read: src/gateway/gateway.mjs

  • Where the operator has bound a credential to a destination, the agent needs none of its own on a call the gateway forwards. The gateway retrieves the value by reference from the configured provider and writes it into the configured request header. The egress event records the reference, status, byte count and response digest, without the credential value, request headers or response body. A destination can still echo a credential back to the agent, as noted under Limits today.

    basis: tests secretless-credentials SC1–SC9; source read: src/gateway/gateway.mjs, src/egress-witness.mjs

  • A grant is single-use and bound to one request and its destination, and the destination must be on a list of hosts the operator set. A person approves the request, except where it acts on material that traces wholly to a directive from the operator or from a person holding the member role, or on a build a person named for release.

    basis: tests policy, effect-acceptance, gateway GW3, GW5; source read: src/policy.mjs, src/router.mjs

  • For a remote MCP server a person admitted at the hub, the gateway performs the OAuth discovery itself, in the MCP specification's order: the server's 401, the protected-resource metadata, the authorization server's metadata. Every address a remote document hands over is judged by the same rule, even as a literal or localhost; https only, no redirect followed, a byte cap and a time cap. A later discovery that changes where the browser goes, where a code would be exchanged or who issues is held until a person approves it again. The gateway completes the authorization with PKCE and writes the tokens to its own file; the hub never holds them.

    basis: tests remote-mcp-discovery RC0–RC17, RA1–RA7, remote-mcp-authorization RB0–RB20; source read: src/gateway/remote-mcp.mjs, src/remote-mcp.mjs

  • When an agent asks to join, the hub reads what its submitted files declare for mcp-remote (manifests, npm, pnpm and yarn lockfiles, npx and npm exec launches, npm install lines) against the five records and a list of renamed copies, and shows each finding to the person who vouches. A finding is evidence: it blocks nothing and changes no admission outcome.

    basis: tests door-dependency, standalone-scanner; source read: src/verify/dependency-check.mjs

In build · commissioned 4 October 2026, not in the tree yet

  • The shipped MCP bridge and the reference agents will refuse a redirect on their own calls to the hub. Today they do not.

Limits today

  • Confining an agent to the gateway's network exists only as a reference scheme for Linux run as root. Nothing confines an agent on Windows, on macOS or without root, and the Linux scheme's first live run is not yet on record. Where an agent is not confined, it can act around the hub, and the hub does not see it.

  • A destination granted as a literal address is dialled as granted, and the name localhost is dialled to loopback. Private network ranges are allowed when the operator sets a switch. The hub's own outbound calls are checked by host name only, not by resolved address.

  • Where no credential is bound, the gateway carries the agent's own headers as sent, a credential of the agent's own included. A destination that echoes request headers hands a written value back to the agent that asked.

  • The file secret provider is a file on the gateway's machine, and a stolen gateway disk is the credentials. With the HTTP provider, a stolen gateway environment is still the credentials. The shipped MCP bridge keeps each participant's signing key unencrypted in a file on the participant's machine. Both files are owner-only on Linux and macOS; Windows does not apply that mode.

  • The hub's own log, tokens and private key are encrypted at rest only when the operator turns that on. Whoever runs the hub's machine holds the door, the log and the disk.

  • The hub verifies nothing about who owns a resource at a destination, and it checks a person's release word only for its form and its author.

  • No live identity provider, directory engine, event collector, timestamp authority, transparency log, metrics scraper, browser authenticator or destination reporter has been reached; each was exercised against a fixture that speaks its specification. The hub is one process on one machine.

  • Two admitted agents can coordinate through messages the hub does not read. A harmful result assembled from steps that each gate nothing is not seen.

  • The check at the door reads what an agent declares, not the process that runs: an agent that omits or misstates a dependency is not caught, and a renamed copy is found only by a name and version listed in the data.

  • The remote MCP connector judges destinations, not whether an admitted server or its authorization server is honest. The gateway's token file is owner-only where the platform has file modes, not on Windows, and a restart in the middle of an authorization costs that sign-in.

Read from the build's tree on 4 October 2026, commit 76c1fba (the six test files named above, run that day on Windows under Node.js 24 with two more on the same subject: 72 tests, all passed), and on 21 October 2026, HEAD ffd795b (the four test files named in the two items above, run that day under Node.js 24: 82 tests, all passed). "Source read" means the statement rests on reading the code and none of those test files names it. The repository is private, so the basis lines name where each statement rests, not a link a reader can open.

The product's limits file, where every limit is listed in full, and its white paper are available on request through any of the contacts above.