{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-elijahtynesreliefweb-mcp-server","slug":"npm-elijahtynesreliefweb-mcp-server","name":"@elijahtynes/reliefweb-mcp-server","type":"mcp","url":"https://www.npmjs.com/package/@elijahtynes/reliefweb-mcp-server","page_url":"https://unfragile.ai/npm-elijahtynesreliefweb-mcp-server","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-elijahtynesreliefweb-mcp-server__cap_0","uri":"capability://tool.use.integration.reliefweb.humanitarian.data.retrieval.via.mcp.protocol","name":"reliefweb humanitarian data retrieval via mcp protocol","description":"Exposes ReliefWeb's humanitarian information API (disasters, crises, organizations, reports) through the Model Context Protocol, allowing Claude and other MCP-compatible clients to query structured humanitarian datasets without direct API calls. Implements MCP resource and tool handlers that translate client requests into ReliefWeb API queries, parse JSON responses, and return formatted data back through the MCP transport layer.","intents":["Query current humanitarian crises and disaster information programmatically from Claude","Retrieve organization profiles and contact information for NGOs and relief agencies","Search humanitarian reports and situation updates without leaving the LLM interface","Build humanitarian information workflows that integrate ReliefWeb data into agent reasoning"],"best_for":["Humanitarian organizations building AI-assisted crisis response tools","Developers creating Claude-based agents that need real-time humanitarian context","Teams building multi-source humanitarian data aggregation systems","Non-profits automating information gathering for grant applications or impact reports"],"limitations":["Dependent on ReliefWeb API availability and rate limits — no built-in caching or fallback mechanisms","MCP protocol overhead adds latency compared to direct REST API calls","No authentication abstraction — inherits ReliefWeb's public API access model (may have query limits)","Limited to ReliefWeb's data schema — cannot augment or transform data beyond API response structure"],"requires":["Node.js 16+ (MCP server runtime)","MCP-compatible client (Claude Desktop, Cline, or custom MCP host)","Network access to ReliefWeb API endpoints (api.reliefweb.int)","No API key required for public ReliefWeb data access"],"input_types":["natural language queries (via MCP tool invocation)","structured filter parameters (disaster type, country, organization type)","pagination parameters (limit, offset)"],"output_types":["JSON-structured humanitarian data (disasters, reports, organizations)","formatted text summaries for LLM consumption","raw API response objects"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-elijahtynesreliefweb-mcp-server__cap_1","uri":"capability://tool.use.integration.mcp.tool.registration.and.schema.binding.for.reliefweb.endpoints","name":"mcp tool registration and schema binding for reliefweb endpoints","description":"Registers ReliefWeb API endpoints as callable MCP tools with JSON schema definitions, enabling clients to discover available queries (disasters, reports, organizations) and their parameters through the MCP tool discovery mechanism. Implements schema validation and parameter mapping between MCP tool invocations and ReliefWeb API query parameters, handling type coercion and optional argument defaults.","intents":["Discover what humanitarian data queries are available without reading documentation","Invoke ReliefWeb searches with type-safe parameters through Claude's tool-calling interface","Understand required vs optional parameters for each humanitarian data endpoint","Build dynamic agent workflows that adapt based on available ReliefWeb query capabilities"],"best_for":["LLM application developers building agents with humanitarian data dependencies","Teams implementing tool discovery and dynamic capability negotiation","Claude users wanting to explore ReliefWeb data through natural language without API documentation"],"limitations":["Schema definitions are static — changes to ReliefWeb API require code updates to MCP server","No runtime schema validation beyond JSON schema — complex business logic constraints not expressible","Tool discovery is synchronous — large numbers of tools may impact MCP handshake latency","Parameter mapping is one-directional (MCP → ReliefWeb) — no reverse mapping for response schema hints"],"requires":["MCP client with tool discovery support (Claude Desktop 0.4+, Cline)","JSON schema understanding in the client implementation","ReliefWeb API documentation to define tool schemas accurately"],"input_types":["MCP tool call requests with JSON parameters","tool discovery requests (MCP ListTools)"],"output_types":["JSON schema definitions for each tool","tool metadata (name, description, parameters)","MCP CallToolResult with humanitarian data"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-elijahtynesreliefweb-mcp-server__cap_2","uri":"capability://memory.knowledge.mcp.resource.exposure.for.humanitarian.data.snapshots","name":"mcp resource exposure for humanitarian data snapshots","description":"Exposes ReliefWeb data as MCP resources (read-only, URI-addressable data objects) that clients can reference and retrieve without invoking tools. Implements resource URI schemes (e.g., reliefweb://disasters/[id]) that map to ReliefWeb API endpoints, allowing clients to fetch specific humanitarian records by reference and enabling context-aware data loading in multi-turn conversations.","intents":["Reference specific humanitarian crises or reports by URI in multi-turn conversations","Load detailed information about a specific disaster without re-querying","Build conversation context that includes linked humanitarian data","Enable Claude to cite specific ReliefWeb records with persistent references"],"best_for":["Building humanitarian chatbots that need to maintain context across multiple turns","Creating audit trails where specific ReliefWeb records are referenced","Teams implementing resource-based data access patterns in MCP","Applications requiring persistent references to humanitarian data"],"limitations":["Resources are read-only — no mutation or update capabilities","URI scheme design must be carefully coordinated with ReliefWeb's data model","No built-in caching — each resource fetch triggers an API call to ReliefWeb","Resource discovery is manual — clients must know URIs in advance or discover them through tools"],"requires":["MCP client with resource support (Claude Desktop 0.4+)","Consistent URI scheme design for ReliefWeb entities","ReliefWeb API endpoints that support direct record lookup by ID"],"input_types":["MCP resource URI requests (reliefweb://disasters/[id])","resource list requests (MCP ListResources)"],"output_types":["JSON humanitarian data records","formatted text summaries","resource metadata (URI, MIME type, description)"],"categories":["memory-knowledge","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-elijahtynesreliefweb-mcp-server__cap_3","uri":"capability://tool.use.integration.mcp.server.lifecycle.management.and.transport.handling","name":"mcp server lifecycle management and transport handling","description":"Implements the MCP server-side protocol stack, handling client connections, message routing, request/response serialization, and error handling over stdio or HTTP transport. Manages server initialization (capabilities negotiation), tool/resource registration, and graceful shutdown, following the MCP specification for bidirectional communication between Claude and the ReliefWeb bridge.","intents":["Start a ReliefWeb MCP server that Claude Desktop can connect to","Handle multiple concurrent client requests without blocking","Properly serialize and deserialize MCP protocol messages","Manage server lifecycle (startup, shutdown, error recovery)"],"best_for":["Developers deploying MCP servers for local Claude Desktop integration","Teams building MCP infrastructure and needing reference implementations","Anyone running humanitarian data queries through Claude locally"],"limitations":["Stdio transport limits throughput — not suitable for high-volume concurrent requests","No built-in authentication — assumes trusted local client (Claude Desktop)","Error handling is basic — complex failure scenarios may not propagate cleanly to client","No request queuing or backpressure handling — rapid requests may overwhelm ReliefWeb API"],"requires":["Node.js 16+ runtime","Claude Desktop 0.4+ (for stdio transport)","stdio or HTTP transport availability on the host system"],"input_types":["MCP protocol messages (JSON-RPC 2.0 over stdio)","client capability declarations","tool invocation requests"],"output_types":["MCP protocol responses (JSON-RPC 2.0)","server capability declarations","tool results and errors"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-elijahtynesreliefweb-mcp-server__cap_4","uri":"capability://data.processing.analysis.reliefweb.api.response.parsing.and.normalization","name":"reliefweb api response parsing and normalization","description":"Parses JSON responses from ReliefWeb API endpoints and normalizes them into consistent data structures suitable for LLM consumption. Handles API response variations (pagination, nested objects, optional fields), extracts relevant fields, and formats data for readability in Claude's interface (e.g., converting timestamps, abbreviating long descriptions, structuring lists).","intents":["Convert raw ReliefWeb API JSON into human-readable summaries for Claude","Extract key fields (crisis name, affected countries, organization contacts) from API responses","Handle pagination transparently when ReliefWeb returns large result sets","Normalize inconsistent API response formats across different endpoints"],"best_for":["Ensuring Claude receives well-formatted humanitarian data without noise","Building consistent interfaces across multiple ReliefWeb endpoints","Teams that need to adapt to ReliefWeb API schema changes"],"limitations":["Normalization logic is hardcoded — changes to ReliefWeb API schema require code updates","No schema versioning — cannot handle multiple API versions simultaneously","Truncation/summarization may lose important details for some use cases","No custom field mapping — users cannot select which fields to include in responses"],"requires":["ReliefWeb API documentation to understand response structure","JSON parsing library (built into Node.js)"],"input_types":["JSON responses from ReliefWeb API","pagination metadata (limit, offset, total)"],"output_types":["normalized JSON objects","formatted text summaries","structured lists of humanitarian records"],"categories":["data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":24,"verified":false,"data_access_risk":"moderate","permissions":["Node.js 16+ (MCP server runtime)","MCP-compatible client (Claude Desktop, Cline, or custom MCP host)","Network access to ReliefWeb API endpoints (api.reliefweb.int)","No API key required for public ReliefWeb data access","MCP client with tool discovery support (Claude Desktop 0.4+, Cline)","JSON schema understanding in the client implementation","ReliefWeb API documentation to define tool schemas accurately","MCP client with resource support (Claude Desktop 0.4+)","Consistent URI scheme design for ReliefWeb entities","ReliefWeb API endpoints that support direct record lookup by ID"],"failure_modes":["Dependent on ReliefWeb API availability and rate limits — no built-in caching or fallback mechanisms","MCP protocol overhead adds latency compared to direct REST API calls","No authentication abstraction — inherits ReliefWeb's public API access model (may have query limits)","Limited to ReliefWeb's data schema — cannot augment or transform data beyond API response structure","Schema definitions are static — changes to ReliefWeb API require code updates to MCP server","No runtime schema validation beyond JSON schema — complex business logic constraints not expressible","Tool discovery is synchronous — large numbers of tools may impact MCP handshake latency","Parameter mapping is one-directional (MCP → ReliefWeb) — no reverse mapping for response schema hints","Resources are read-only — no mutation or update capabilities","URI scheme design must be carefully coordinated with ReliefWeb's data model","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.2,"ecosystem":0.3,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.903Z","last_scraped_at":"2026-05-03T14:23:46.318Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-elijahtynesreliefweb-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=npm-elijahtynesreliefweb-mcp-server"}},"signature":"nHfk6xrnAyyVLATvv9TlWTVYG8IH4HpvF6gQjHjA7+pOFJ+HnSeiX5IjLrUOuhv69rDpxYLdAEI56cy7aNmeCQ==","signedAt":"2026-06-20T04:54:56.293Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-elijahtynesreliefweb-mcp-server","artifact":"https://unfragile.ai/npm-elijahtynesreliefweb-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=npm-elijahtynesreliefweb-mcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}