Hosted MCP server/Database

disaster-wire MCP server

Hosted at sukriramli-disaster-wire-mcp.hf.space·Streamable HTTP

disaster-wire is an autonomous global disaster intelligence feed: machine-readable disaster telemetry for agents, LLMs, and RAG pipelines. The live MCP endpoint at https://sukriramli-disaster-wire-mcp.hf.space/gradio_api/mcp answers MCP initialize over Streamable HTTP. The README's older remote-SSE path, /gradio_api/mcp/sse, returned 404 when checked on 2026-11-16, so use the Streamable HTTP path.

sukriramli-disaster-wire-mcp.hf.space Streamable HTTP Not verified Source checked Nov 12, 2026 Server responded when checked Reviewed 2026-11-16
About

Where it fits

Teams building agents or RAG pipelines that need a disaster telemetry feed.

  • Fetch the disaster telemetry feed.
  • Feed disaster data into an LLM workflow.
  • Use telemetry in a RAG pipeline.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds disaster-wire as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http disaster-wire https://sukriramli-disaster-wire-mcp.hf.space/gradio_api/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://sukriramli-disaster-wire-mcp.hf.space/gradio_api/mcp
Host
sukriramli-disaster-wire-mcp.hf.space · /gradio_api/mcp
Transport
Streamable HTTP
Authentication
Not verified
Server name
disaster-wire
Listing type
Community or directory listing

The installer uses the server name disaster-wire. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that disaster-wire appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Fetch the disaster telemetry feed. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Confirm the provider's credential model before relying on scopes or key permissions. Remove the server and revoke any token when you no longer need it.

Server responded when checked

We reached sukriramli-disaster-wire-mcp.hf.space when we checked. That only means the address answered; it does not prove the MCP connection, sign-in, or tools work. The provider page was available when we checked.

Provider page available on Nov 12, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

disaster-wire repositoryhttps://github.com/mysukriramli/disaster-wire