io.github.savhascelik/meta-api-mcp-server

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

• server.js:143mcp-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 (isUrl) {
                  // Uzak URL'den yükle
                  const response = await axios.get(configSource, { timeout: CONFIG_TIMEOUT });
                  if (response.status !== 200) {
                      throw new Error(`Failed to fetch config list from URL ${configSource}. Status: ${response.status}`);

• server.js:180mcp-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.

                      // URL ise, direkt yükle
                      if (subIsUrl) {
                          const response = await axios.get(subConfigSource, { timeout: CONFIG_TIMEOUT });
                          if (response.status === 200) {
                              const data = response.data;

• server.js:220mcp-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.

              // --- Uzak URL'den Yükleme ---
              console.error(`Source is a URL. Fetching...`);
              const response = await axios.get(configSource, { timeout: CONFIG_TIMEOUT });
              if (response.status === 200) {
                  const data = response.data;

• server.js:382mcp-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.

          // Axios Çağrısı
          console.error(`-> Calling HTTP Target: ${endpointConfig.targetMethod} ${targetUrl}`);
          const apiResponse = await axios({
              method: endpointConfig.targetMethod.toUpperCase(),
              url: targetUrl,

Auth Posture

• authentication_model

  stdio transport: the client launches the server as a subprocess, so the OS process boundary is the auth boundary — `03` §4 does not penalise absent auth here

• transport_security

  declared transport: stdio — launched as a subprocess by the client, so the security boundary is the client process, not a network port (`03` §4)

• secret_handling

  detect-secrets matched 1 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 README.md:79

• authorization_granularity

  no tool registration was recognised anywhere in the source. An MCP server registers tools by definition, so this is a gap in our detection rather than a server with none, and `03` §4's threshold cannot be applied to it. A tool-list handler IS present, so the tools are built in a shape this counter could not enumerate.

Maintenance

• recency

  last commit 402 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

  no author reached `03` §5's 5-commit bar in the last 12 months (0 contributor(s) with fewer) — scored at §5's weakest described band, which the section defines for a quiet 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

  package.json declares 'MIT' but no LICENSE file ships with the source

• readme_quality

  README.md: installation instructions (+25), configuration documented (+25), exposed tools or resources enumerated (+30), 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