io.github.geoacpfilho/paygate-monetize-monetization-x402

version 0.3.1

scanned 2026-10-16
source github.com/geoacpfilho/paygate-mcp
commit 67333b060e7a
transport streamable-http
files read 15
methodology 0.2.0
ruleset 0.1.1

No tag matching version 0.3.1 was found in this repository, so the scan read the default branch instead. The findings below describe that code, not necessarily the released version.

Code Safetyweight 30

Auth Postureweight 20

92measured on 65% of this axis

Dependency Healthweight 20

Maintenanceweight 15

70measured on 45% of this axis

Transparencyweight 15

The evidence

Every deduction below names the artefact that produced it. Nothing on this page was executed: the source was read, never run, and no running server was contacted.

Code Safety

scripts/pay-test.mjs:35mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
```
async function rpc(payload) {
  const resp = await fetch(endpoint, {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
```
src/api/paygate-tools.ts:271mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
```
        target_server_url.includes('oraculo-b2r') && c.env.ORACULO_B2R
          ? await c.env.ORACULO_B2R.fetch(request)
          : await fetch(request);

      const raw = await probe.text();
```
src/api/paygate-tools.ts:379mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
```
    let served = '';
    try {
      const resp = await fetch(verifyUrl, { method: 'GET' });
      if (!resp.ok) {
        return toolFailure(
```
src/api/proxy.ts:73mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
```
    return c.env.ORACULO_B2R.fetch(request);
  }
  return fetch(request);
}
```
src/api/register.ts:64mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
```
    let importedToolsCount = 0;
    try {
      const resp = await fetch(target_server_url, {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
```
src/services/payment-verifier.ts:25mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
```
  if (facilitatorUrl) {
    try {
      const resp = await fetch(facilitatorUrl, {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
```

src/services/payment-verifier.ts:70mcp-js-ssrf-nonliteral-url (medium/low)

An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.

      // Buscar recibo da transação na rede Base
      const rpcUrl = `https://base-mainnet.g.alchemy.com/v2/${alchemyApiKey}`;
      const resp = await fetch(rpcUrl, {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },

src/services/payment-verifier.ts:286mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
```
  const signatureBase64 = btoa(String.fromCharCode(...new Uint8Array(signature)));

  return fetch(url, {
    method,
    headers: {
```
src/x402/facilitator.ts:161mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
```
  }

  const resp = await fetch(url, {
    method: 'POST',
    headers,
```
src/x402/facilitator.ts:209mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
```
    }

    const resp = await fetch(url, { headers });
    const text = await resp.text();
    let networks: string[] = [];
```

Auth Posture

authentication_model
auth enforcement present at a call site in the source (inbound token verification) and documented in the README; "refused without credentials" (`03` §4) established by reading the code rather than by connecting
transport_security
declared endpoint(s) are HTTPS: https://paygate-mcp.rendercriativo.workers.dev/mcp; scored 80, not 100: `03` §4 reserves 100 for HTTPS *with HSTS*, and an HSTS header can only be seen by connecting, which `04` §9 does not do. This is an unverifiable band, not an observed absence.
secret_handling
detect-secrets matched 4 credential-shaped string(s), every one from a keyword or entropy heuristic (Secret Keyword). Those flag placeholders, variable names and content hashes as readily as credentials, so they do not establish the committed credential `03` §4's 0 asserts, and this sub-check is not scored; Secret Keyword at src/api/paygate-tools.ts:36; Secret Keyword at src/api/paygate-tools.ts:312; Secret Keyword at src/api/paygate-tools.ts:342; Secret Keyword at src/api/register.ts:39
authorization_granularity
6 tool registrations and no conditional access logic found — `03` §4 calls this case 'needs human review' and assigns it no score band, so it is not scored here

Dependency Health

package-lock.jsonnanoid 3.3.16 — GHSA-2v37-7h3g-55p8
direct, CVSS 8.2, fixed in 3.3.18
https://osv.dev/vulnerability/GHSA-2v37-7h3g-55p8
package-lock.jsonsharp 0.34.5 — GHSA-rgj7-g3m4-5g8c
transitive, CVSS 8.9, fixed in 0.35.4
https://osv.dev/vulnerability/GHSA-rgj7-g3m4-5g8c
package-lock.jsonsharp 0.34.5 — GHSA-wq5f-xc86-pv6w
transitive, CVSS 8.9, fixed in 0.35.5
https://osv.dev/vulnerability/GHSA-wq5f-xc86-pv6w
package-lock.jsonsource-map-js 1.2.1 — GHSA-68fv-2mgg-jv7q
transitive, CVSS 8.7, fixed in 1.2.2
https://osv.dev/vulnerability/GHSA-68fv-2mgg-jv7q
package-lock.jsonundici 7.28.0 — GHSA-rfgv-xxqx-mfg5
transitive, CVSS 7.5, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-rfgv-xxqx-mfg5
package-lock.jsonundici 7.28.0 — GHSA-4cwx-7wf7-3272
transitive, CVSS 7.4, fixed in 7.29.0
https://osv.dev/vulnerability/GHSA-4cwx-7wf7-3272
package-lock.jsonundici 7.28.0 — GHSA-w293-vg96-wgc3
transitive, CVSS 7.4, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-w293-vg96-wgc3
package-lock.jsonsharp 0.34.5 — GHSA-f88m-g3jw-g9cj
transitive, CVSS 7.0, fixed in 0.35.0
https://osv.dev/vulnerability/GHSA-f88m-g3jw-g9cj
package-lock.jsonhono 4.12.31 — GHSA-gqvv-2mrq-wpjv
direct, CVSS 6.5, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-gqvv-2mrq-wpjv
package-lock.jsonhono 4.12.31 — GHSA-crvj-82cr-hjcx
direct, CVSS 5.9, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-crvj-82cr-hjcx
package-lock.jsonvitest 4.1.10 — GHSA-82fw-gwwq-j7x9
direct, CVSS 5.9, fixed in 4.1.11
https://osv.dev/vulnerability/GHSA-82fw-gwwq-j7x9
package-lock.jsonhono 4.12.31 — GHSA-54fx-42gc-7vw4
direct, CVSS 5.3, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-54fx-42gc-7vw4
package-lock.jsonhono 4.12.31 — GHSA-8j4g-w8fx-2239
direct, CVSS 5.3, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-8j4g-w8fx-2239
package-lock.jsonhono 4.12.31 — GHSA-g6gw-c38x-mqfc
direct, CVSS 5.3, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-g6gw-c38x-mqfc
package-lock.jsonhono 4.12.31 — GHSA-f23p-vx2j-j53r
direct, CVSS 4.8, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-f23p-vx2j-j53r
package-lock.jsonhono 4.12.31 — GHSA-hxh3-vqpv-xpqv
direct, CVSS 4.7, fixed in 4.13.7
https://osv.dev/vulnerability/GHSA-hxh3-vqpv-xpqv
package-lock.jsonundici 7.28.0 — GHSA-2jfj-6hjv-fm6j
transitive, CVSS 6.5, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-2jfj-6hjv-fm6j
package-lock.jsonpostcss 8.5.21 — GHSA-fxqj-rqcc-2cmp
transitive, CVSS 6.3, fixed in 8.5.23
https://osv.dev/vulnerability/GHSA-fxqj-rqcc-2cmp
package-lock.json@vitest/mocker 4.1.10 — GHSA-82fw-gwwq-j7x9
transitive, CVSS 5.9, fixed in 4.1.11
https://osv.dev/vulnerability/GHSA-82fw-gwwq-j7x9
package-lock.jsonundici 7.28.0 — GHSA-3wwx-pv8p-q78v
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-3wwx-pv8p-q78v
package-lock.jsonundici 7.28.0 — GHSA-3xpg-4rpp-hhhm
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-3xpg-4rpp-hhhm
package-lock.jsonundici 7.28.0 — GHSA-jr45-8vmc-qm54
transitive, CVSS 5.9, fixed in 7.29.0
https://osv.dev/vulnerability/GHSA-jr45-8vmc-qm54
package-lock.jsonundici 7.28.0 — GHSA-pmjh-fq2x-6v4x
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-pmjh-fq2x-6v4x
package-lock.jsonundici 7.28.0 — GHSA-rx4f-c7p8-82vq
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-rx4f-c7p8-82vq
package-lock.jsonesbuild 0.18.20 — GHSA-67mh-4wv8-2f99
transitive, CVSS 5.3, fixed in 0.25.0
https://osv.dev/vulnerability/GHSA-67mh-4wv8-2f99
package-lock.jsonundici 7.28.0 — GHSA-8xcm-r25x-g524
transitive, CVSS 4.8, fixed in 7.29.0
https://osv.dev/vulnerability/GHSA-8xcm-r25x-g524
package-lock.jsonundici 7.28.0 — GHSA-v3r7-h72x-cjcm
transitive, CVSS 4.8, fixed in 7.29.0
https://osv.dev/vulnerability/GHSA-v3r7-h72x-cjcm
package-lock.jsonundici 7.28.0 — GHSA-m8rv-5g2x-5cg5
transitive, CVSS 4.2, fixed in 7.29.0
https://osv.dev/vulnerability/GHSA-m8rv-5g2x-5cg5
package-lock.jsonhono 4.12.31 — GHSA-79qm-7rj5-m7r9
direct, CVSS 3.7, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-79qm-7rj5-m7r9
package-lock.jsonundici 7.28.0 — GHSA-2gqq-gqf2-x968
transitive, CVSS 3.7, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-2gqq-gqf2-x968
package-lock.jsonundici 7.28.0 — GHSA-8436-99hf-9mmv
transitive, CVSS 3.7, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-8436-99hf-9mmv
package-lock.jsonundici 7.28.0 — GHSA-r53p-7pc4-xj5r
transitive, CVSS 3.7, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-r53p-7pc4-xj5r

Maintenance

recency
last commit 63 day(s) before 2026-10-16
issue_responsiveness
this repository has no issues `03` §5's window covers. An unanswered issue scores 0 under §5, but a repository with no issues filed has not failed to answer one.
release_cadence
this repository publishes neither releases nor version tags
bus_factor
sole maintainer
repository_signals
`03` §5 scores this by quartile WITHIN the server's category, which needs a distribution across every scanned server and so cannot be computed while scanning one. It is a post-pass over the crawl and that pass does not exist yet.

Transparency

license
LICENSE present with no SPDX-License-Identifier tag; identified as 'MIT' from its text
readme_quality
README.md: configuration documented (+25), states what the server does in the first 200 words (+20)
declared_scopes
neither the README nor the MCP manifest documents what the server accesses or what side effects it has
changelog
no CHANGELOG in the fetched source. `03` §7's partial credit for tagged releases carrying release notes is not applied here — that needs the forge API, which this check does not call
security_contact
no SECURITY.md and no disclosure contact in the README, so a finder has no route to report a vulnerability privately

Contest a finding

Every number here comes from a rule reading published source, and rules get things wrong. If something on this page is incorrect — or correct but mitigated by a check the rule cannot see — open an issue and we answer it in writing. A finding we got wrong is removed and the rule is fixed; one that stands is answered on the record.

Anyone can file: the maintainer, a researcher who disagrees with the classification, or a user who tested the server and could not reproduce it. Name this server and the rule or advisory ID shown beside the finding above. We aim to reply within five business days and to resolve within ten.

Open an appeal on GitHub