MCP Server · npm ecosystem

Your agent's knowledge
has a cutoff.
Your dependencies don't.

Breaking changes, security fixes, deprecations — every entry sourced. Nothing hallucinated.

Install

One endpoint. Every client.

DepFeed is a hosted Streamable-HTTP MCP server — no local process, no npm install, nothing to keep running. Point your client at the endpoint, pass your API key, done.

Add via CLI

claude mcp add --transport http depfeed \
  https://depfeed-production.up.railway.app/ \
  --header "X-API-Key: YOUR_KEY"

Verify with claude mcp list — then ask Claude: "what changed in next since 14.2.0?"

claude_desktop_config.json

Claude Desktop speaks stdio — bridge to the HTTP endpoint with mcp-remote:

{
  "mcpServers": {
    "depfeed": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://depfeed-production.up.railway.app/",
        "--header",
        "X-API-Key: YOUR_KEY"
      ]
    }
  }
}

Settings → Developer → Edit Config, then restart Claude Desktop.

.cursor/mcp.json

{
  "mcpServers": {
    "depfeed": {
      "url": "https://depfeed-production.up.railway.app/",
      "headers": { "X-API-Key": "YOUR_KEY" }
    }
  }
}

Project-level .cursor/mcp.json or global ~/.cursor/mcp.json — then enable it under Settings → MCP.

.vscode/mcp.json

{
  "servers": {
    "depfeed": {
      "type": "http",
      "url": "https://depfeed-production.up.railway.app/",
      "headers": { "X-API-Key": "YOUR_KEY" }
    }
  }
}

Used by GitHub Copilot's agent mode (VS Code 1.99+).

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "depfeed": {
      "serverUrl": "https://depfeed-production.up.railway.app/",
      "headers": { "X-API-Key": "YOUR_KEY" }
    }
  }
}

Windsurf → Settings → Cascade → MCP Servers → refresh.

Raw endpoint — any MCP client, or plain curl

Streamable HTTP transport at the root path. Auth is a single header:

# Endpoint
https://depfeed-production.up.railway.app/

# Auth header
X-API-Key: YOUR_KEY

# Smoke test: list the tools via JSON-RPC
curl -s https://depfeed-production.up.railway.app/ \
  -H "X-API-Key: YOUR_KEY" -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Machine-readable overview for agents: /llms.txt

Tool playground

Ten tools. Real request bodies.
Real responses.

This is exactly what your agent sends and receives — the responses below were captured from the production server and are replayed here, not re-fetched live. Pick a tool, hit Send.

tools/
POST / Request · JSON-RPC
Response
// Hit "Send request" to see the live-captured response
Why DepFeed

Not docs for agents.
What changed — and what to do about it.

Web search is slow, expensive, and returns blog posts. Docs servers tell agents how an API works today. DepFeed answers the upgrade question: what broke between the version I know and the version that ships?

Every entry has a source URL

The core invariant, enforced in the schema itself: no ChangeEntry without a source_url. Every claim links to the release notes it came from — verifiable by human or agent.

Honest about its limits

An uncovered package returns a structured NotCovered response with covered alternatives — never an error, and never a guess. Your agent knows what it doesn't know.

Built for context windows

Compact, categorized JSON with a max_tokens budget per call — least important entries drop first, marked with truncated. No 40-KB blog posts in your context.

Batch a whole lockfile diff

One call for every dependency that changed in a package.json diff. Each package resolves independently — one uncovered entry never blocks the rest.

Compatibility, not just changelogs

A package can look fine alone and still conflict with a peer. check_compatibility verifies recorded peerDependencies/engines ranges pairwise — and says unknown instead of pretending.

Delta feeds with cursors

"What's new since I last checked" across the whole coverage set — including a security-only digest for CI and compliance automation. Store the cursor, call again tomorrow.

50 packages

curated npm coverage today — the ecosystem's most-depended-on frameworks and libraries. Growing with demand; Team subscribers steer what's next.

Pricing

Flat plans. No surprise invoices.

Agent traffic is bursty — metered billing punishes exactly that. DepFeed is a flat subscription: predictable for you, sustainable for us.

Free
$0
200 requests / month
  • Full top-50 package coverage
  • All per-package tools
  • Source URL on every entry
  • Delta feeds (get_updates_since)
Start free
Team
$29/ month
25,000 requests / month
  • Everything in Pro
  • Multiple API keys for the whole team
  • Webhook delivery for new changes
  • Prioritized coverage requests
Get Team

Sign in or create a free account to generate an API key — upgrade to Pro or Team anytime from your dashboard.

Reading this as an agent?

Skip the marketing. The machine-readable project overview lives at /llms.txt, and tools/list on the endpoint returns full JSON schemas for all eight tools.

Two rules worth internalizing: trust NotCovered responses instead of falling back to pretraining knowledge, and never treat a compatibility unknown as a green light.

# the whole pitch, agent-sized
curl -s https://depfeed-production.up.railway.app/llms.txt

# → DepFeed: change intelligence for coding agents.
#   Ask "what changed in <pkg> since <version>?"
#   and get sourced, categorized, honest answers.