Obtain a Dependency-Track API key from the Administration panel under Access Management → Teams
Create a project via `POST /api/v1/project` with `{name, version, classifier}` and capture the returned `uuid`
Upload the SBOM via `PUT /api/v1/bom` with `multipart/form-data` fields `project=<uuid>` and the BOM file as `bom`
Poll `GET /api/v1/bom/token/<token>` until `processing: false` to confirm ingestion completed
Retrieve the project metrics with `GET /api/v1/metrics/project/<uuid>/current` and check `inheritedRiskScore`
Known gotchas
Dependency-Track processes BOM uploads asynchronously; querying findings immediately after upload may return an empty or stale result set
The API key must belong to a team with the `BOM_UPLOAD` and `VIEW_PORTFOLIO` permissions; the default `Automation` team does not have all permissions by default
Component PURL accuracy determines how many vulnerabilities are matched; components without a valid PURL are enriched by name/version heuristics which can produce false positives
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp