generated: '2026-08-13'
method: searched
source: >-
  npm registry search + registry.npmjs.org metadata, pypi.org, rubygems.org, packagist.org,
  crates.io and github.com search, 2026-08-13
note: >-
  Noosh ships NO first-party client library in any public registry. Searched npm (registry search for
  "noosh"), PyPI (noosh, noosh-api, pynoosh — all 404), RubyGems (noosh — 404), Packagist (no Noosh
  result), crates.io and GitHub (there is no github.com/noosh organisation — the org endpoint returns
  404). The only published artifacts that wrap the Noosh API are third-party code generators, recorded
  below with official: false so they are never counted as a Noosh SDK. No SDKs pointer is emitted in
  apis.yml, because the sdk_count check must not fire on someone else's generated wrapper.
official_package_count: 0
packages:
  - language: javascript
    registry: npm
    name: '@datafire/noosh'
    url: https://www.npmjs.com/package/@datafire/noosh
    install: npm install @datafire/noosh
    official: false
    publisher: DataFire
    version: 4.0.0
    published: '2020-12-21'
    source_spec: https://api.noosh.com/api/swagger.json
    note: >-
      Auto-generated by the DataFire project from the APIs.guru mirror of the Noosh Swagger document.
      Last published 2020-12-21 — nearly six years stale, and generated from an older 54-path snapshot
      while the live spec now publishes 86 paths / 107 operations. Not maintained by Noosh.
  - language: python
    registry: github
    name: ag2-mcp-servers/noosh-api-application
    url: https://github.com/ag2-mcp-servers/noosh-api-application
    install: null
    official: false
    publisher: ag2.ai (mcp.ag2.ai generator)
    version: null
    published: '2025-06-29'
    note: >-
      Machine-generated MCP server wrapping the Noosh API, produced by mcp.ag2.ai. Not published to any
      package registry (version null — no registry metadata endpoint exists for it), zero stars, last
      pushed 2025-07-16. Recorded as a lead only; it is not a Noosh product and does not make Noosh an
      MCP provider.
registries_checked:
  - {registry: npm, query: noosh, first_party_hits: 0}
  - {registry: pypi, packages_probed: [noosh, noosh-api, pynoosh], status: [404, 404, 404]}
  - {registry: rubygems, package: noosh, status: 404}
  - {registry: packagist, query: noosh, first_party_hits: 0}
  - {registry: crates.io, query: noosh, first_party_hits: 0}
  - {registry: github, org: noosh, status: 404}