Dynamic Feed
Wire live CVEs, package versions, prices, and third-party service status into your agent so security and dependency answers stay current during ship prep.
Overview
ai.dynamicfeed/dynamic-feed is a MCP server for the Ship phase that serves live prices, software versions, CVEs, and service status over Streamable HTTP and SSE so agents stop relying on stale training data.
What is this MCP server?
- Remote MCP over Streamable HTTP (dynamicfeed.ai/mcp) and SSE (dynamicfeed.ai/sse)
- Surfaces fresh data models lack: live prices, software versions, CVEs, and service status
- Hosted v0.6.0 server—no local daemon required beyond MCP client config
- Fits agents that must verify external reality instead of trusting cutoff knowledge
- Single catalog entry for multiple live fact categories in one Dynamic Feed endpoint
- Server version 0.6.0 per server.json
- Two remote transports: streamable-http at /mcp and SSE at /sse
- Four advertised fresh-data categories: live prices, software versions, CVEs, service status
What problem does it solve?
Coding agents confidently cite old package versions, miss new CVEs, and guess outage status because their knowledge froze months ago.
Who is it for?
Indie devs hardening dependencies, checking CVE exposure, or validating vendor uptime during release week with Claude Code or Cursor.
Skip if: Builders who need deep proprietary market datasets, offline-only workflows, or self-hosted MCP without third-party remotes.
What do I get? / Deliverables
Once Dynamic Feed is in mcp.json, your agent can fetch current versions, vulnerabilities, prices, and status pages while you review or deploy.
- Agent queries against hosted live price, version, CVE, and status datasets
- Reduced stale-answer risk during security and dependency reviews
- Dual-transport remote config (Streamable HTTP and SSE) from one catalog slug
Recommended MCP Servers
Journey fit
Stale training data hurts most when you are about to release or harden a stack—CVE and version checks are Ship-phase security work—even though live prices and status feeds also help earlier validation and later operations. CVE and software-version freshness directly support vulnerability review and dependency pinning, which is the security subphase shelf before launch.
How it compares
Hosted live-facts MCP remote, not a local linter skill or a full SIEM platform.
Common Questions / FAQ
Who is ai.dynamicfeed/dynamic-feed for?
Solo builders and agent users who need fresh CVE, version, price, or status data inside Claude Code, Cursor, or other MCP clients.
When should I use ai.dynamicfeed/dynamic-feed?
Use it during Ship security reviews, dependency upgrades, or Operate checks whenever answers must reflect what changed today, not the model cutoff.
How do I add ai.dynamicfeed/dynamic-feed to my agent?
Add the remotes entry from server.json—https://dynamicfeed.ai/mcp (streamable-http) or https://dynamicfeed.ai/sse (sse)—to your agent host mcp.json.