# VulnFeed Dependency Vulnerability Monitor

> VulnFeed Dependency Vulnerability Monitor is a paid API for AI agents from vulnfeed-api.novadyne.ai, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Registers a software project's package dependencies for continuous vulnerability monitoring with EPSS (Exploit Prediction Scoring System) scoring

## Facts

- Endpoint: POST https://vulnfeed-api.novadyne.ai/vulnscan/monitor
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vulnfeed-dependency-vulnerability-monitor-d41b53d2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_z3ZqgISgKF0JEbIO91r2o

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability vulnfeed-dependency-vulnerability-monitor-d41b53d2 -d '<json body>'
```

Example prompt: Set up vulnerability monitoring for my project 'payment-service' — scan these packages for known CVEs and EPSS exploit scores: express@4.18.2, lodash@4.17.21, axios@1.4.0.

## When to prefer this

Use this endpoint when you need to register a specific set of software package dependencies for ongoing vulnerability monitoring with EPSS scoring, especially in automated DevSecOps pipelines or CI/CD workflows. Prefer this over one-shot scanners when you want continuous tracking via a project ID. The micropayment model (x402) makes it suitable for pay-per-use agent workflows without subscription overhead.

## Known failure modes

- Missing required 'packages' array returns validation error
- Missing required 'project_name' returns validation error
- Payment failure (x402) if insufficient USDC balance — returns 402 Payment Required
- Empty packages array may result in no vulnerabilities to report
- Duplicate project_name may create a new project_id or conflict depending on server logic
- Network timeout for large package lists

## How this service works

Dependency vulnerability scanner with EPSS scoring. MCP server + x402 micropayments.

## Output

Returns a boolean ok status, the project name, and a unique project_id that identifies the newly registered monitoring entry for this set of dependencies.

## Example request

```json
{
 "packages": [
  "express@4.18.2",
  "lodash@4.17.21",
  "axios@1.4.0"
 ],
 "project_name": "test-webapp"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "packages",
  "project_name"
 ],
 "properties": {
  "packages": {
   "type": "array"
  },
  "project_name": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ok": {
   "type": "boolean"
  },
  "name": {
   "type": "string"
  },
  "project_id": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vulnfeed-dependency-vulnerability-monitor-d41b53d2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vulnfeed-api.novadyne.ai](https://www.zero.xyz/host/vulnfeed-api.novadyne.ai/llms.txt)