mcpField
D
Dynamic Feed

Dynamic Feed

Remote
dynamicfeed.aiOther0Updated 9w ago

About Dynamic Feed

Dynamic Feed is a local stdio MCP server that brings live data from Dynamic Feed to MCP clients, including weather, vulnerabilities, disasters, and flights. It proxies requests over outbound HTTPS and exposes the upstream server's current tools, making it suitable for clients or networks that cannot use remote streaming.

Key features

  1. 01Local stdio connection for MCP clients
  2. 02Live data across multiple domains
  3. 03Dynamically reflects upstream tools
  4. 04Outbound HTTPS proxying
  5. 05No API key required for tools

Use cases

  1. 01Access live weather and flight information
  2. 02Check software versions and exploited vulnerabilities
  3. 03Use MCP behind firewalls blocking remote SSE

MCP support

The server communicates with local MCP clients over stdio and proxies to Dynamic Feed over HTTPS. Alternatively, clients can connect to `https://dynamicfeed.ai/mcp`, which supports Streamable HTTP and legacy SSE.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://dynamicfeed.ai/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://dynamicfeed.ai/mcp
SSEhttps://dynamicfeed.ai/sse

Tools

94
ParameterTypeRequiredDescription
querystringNo
providerstringNo
max_input_priceanyNo
min_contextanyNo
needs_visionbooleanNo
limitintegerNo

Details

From the project README

Part of Fluxdyne — The Trust & Audit Protocol for Enterprise AI. Get the API → https://fluxdyne.com

dynamicfeed-mcp

Local stdio MCP server for Dynamic Feed: the fresh, live data AI models don't have on their own: weather, software versions, CVEs & actively-exploited vulns, sanctions, global disasters, earthquakes/wildfires/drought, satellites & space weather, flights, AI models and more. 91 tools across 19 verticals, all commercially-licensed & keyless.

This bridge speaks MCP over stdio to your local client and proxies to the remote Dynamic Feed endpoint over ordinary outbound HTTPS, so it works through corporate firewalls/VPNs that block remote SSE streams, and it always exposes whatever tools the live server has (nothing hard-coded to drift).

Prefer a remote URL? You don't even need this package. Point any MCP client at https://dynamicfeed.ai/mcp (it auto-detects modern Streamable HTTP and legacy SSE). This runner is for clients that only accept a local command, or networks that block remote streaming.

Use it

Claude Desktop / Cursor / Windsurf: add to your MCP config:

{
  "mcpServers": {
    "dynamic-feed": {
      "command": "npx",
      "args": ["-y", "dynamicfeed-mcp"]
    }
  }
}

That's it, no API key required (the MCP tools are keyless). Restart your client and the Dynamic Feed tools appear.

Options (env vars)

VariableDefaultPurpose
DYNAMICFEED_MCP_URLhttps://dynamicfeed.ai/mcpOverride the upstream endpoint
DYNAMICFEED_API_KEY(none)Optional X-API-Key (tools are keyless, so rarely needed)

Example tools

sports_pulse · current_weather · exploited_vulnerabilities · software_version · global_disasters · earthquakes · wildfires · satellite_position · space_weather · security_advisories · air_quality · live_flights · china_data … and more.

MIT · dynamicfeed.ai

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.