clearlydefined_harvest_status

Pack: clearlydefined · Endpoint: https://gateway.pipeworx.io/clearlydefined/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/clearlydefined_harvest_status for the schema, then POST the same URL with its arguments for the data.

List which harvesting tools (ScanCode, Licensee, REUSE, FOSSology, clearlydefined) have analysed one exact component version, and at which tool versions. Use it to judge how much evidence sits behind a definition, or to explain why a definition looks thin. Keyless.

Example call

Arguments

{
  "type": "npm",
  "provider": "npmjs",
  "name": "express",
  "revision": "4.18.2"
}

curl

curl -X POST https://gateway.pipeworx.io/clearlydefined/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"clearlydefined_harvest_status","arguments":{"type":"npm","provider":"npmjs","name":"express","revision":"4.18.2"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('clearlydefined_harvest_status', {
  "type": "npm",
  "provider": "npmjs",
  "name": "express",
  "revision": "4.18.2"
});

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "clearlydefined": {
      "url": "https://gateway.pipeworx.io/clearlydefined/mcp"
    }
  }
}

See Getting Started for client-specific install steps.