dependencies
Pack: deno-land · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/dependencies for the schema, then POST the same URL with its arguments for the data.
NOT AVAILABLE: the dependency graph came from apiland.deno.dev, which was shut down on 2026-07-20; the registry CDN that replaced it publishes no dependency data. Returns empty_reason: "upstream_removed" with the module’s source repository, so you can read its deps at source. Use version for the file listing and repo pointer.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
name | string | yes | |
version | string | yes |
Example call
Arguments
{
"name": "fresh",
"version": "1.4.0"
}
curl
curl -X POST https://gateway.pipeworx.io/deno-land/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"dependencies","arguments":{"name":"fresh","version":"1.4.0"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('dependencies', {
"name": "fresh",
"version": "1.4.0"
});
Response shape
Always returns: dependencies
| Field | Type | Description |
|---|---|---|
dependencies | unknown |
Full JSON Schema
{
"type": "object",
"properties": {
"dependencies": {
"oneOf": [
{
"type": "object",
"description": "Dependency map from version metadata"
},
{
"type": "null",
"description": "No dependencies found"
}
]
}
},
"required": [
"dependencies"
]
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the deno-land pack
{
"mcpServers": {
"deno-land": {
"url": "https://gateway.pipeworx.io/deno-land/mcp"
}
}
}
See Getting Started for client-specific install steps.