accueil / serveurs / Données & BDD / com.daedalmap/wildfires
com.daedalmap/wildfires
serveur MCP (Model Context Protocol) · com.daedalmap/wildfires 0.4.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.daedalmap/wildfires est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.daedalmap/wildfires » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 5 outils
- get_catalog≈ 683 tokens
Choose data or geometry to list published pack IDs or family and scope IDs. The response includes a complete catalog download URL. Use get_pack for data or get_geography for geometry. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.
Paramètres, retour & exemple (1)
Paramètrescatalog· string · requis · data | geometry
Required directory selector.
Exemple d'appel{"name": "get_catalog", "arguments": {"catalog": "data"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "packs": [], "detail": "lite", "reason": "texte", "scopes": [], "catalog": "data", "families": [], "guidance": {}, "warnings": [], "next_step": {}, "pack_count": 1, "provenance": {}}} - get_data≈ 1296 tokens
Retrieve rows from one selected published data pack using exact metrics, loc_id-based region filters, time/metric filters, sorting, and a row limit. Disaster event rows include stable event_id values for get_event drill-down. A parent administrative loc_id selects matching descendant rows at the pack's published grain. Call get_pack first; geometry families use their focused next-step tools.
Paramètres, retour & exemple (7)
Paramètressort· ? · optionnel
Sort by a sortable field from get_pack; direction defaults to asc.limit· integer · optionnel
Maximum number of rows to return for the requested source or pack.output· object · optionnel
Optional response controls. v1 supports rows only.filters· object · requismetrics· array · requis
Exact metric ids from get_pack. Use event_count for aggregate counts only when get_pack publishes it.pack_id· string · requis
Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.request_id· string · optionnel
Optional caller-supplied request id for tracing and idempotency.
Exemple d'appel{"name": "get_data", "arguments": {"filters": {}, "metrics": [], "pack_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"rows": [], "sort": [], "error": {}, "limit": 1, "reason": "texte", "pack_id": "texte", "guidance": {}, "warnings": [], "next_step": {}, "row_count": 1, "source_id": "texte", "truncated": true}} - get_event≈ 832 tokens
Retrieve one exact disaster event and explicitly requested relationships, affected places, native observations, or geometry. Use get_data to obtain the stable event_id first.
Paramètres, retour & exemple (8)
Paramètreslimit· integer · optionnel
Per-section ceiling for relationships, affected places, observations, or geometry frames.include· array · optionnel
Optional companion layers. Omit for the lightweight event summary. Geometry is never returned implicitly.pack_id· string · requis
Required disaster pack_id that returned this event_id from get_data. The tool never searches other packs.event_id· string · requis
Exact stable event_id returned by a disaster-pack get_data row.source_id· string · requis
Required source_id from the same get_data result. Must identify one published event source in pack_id.request_id· string · optionnel
Optional caller-supplied request id for tracing.geometry_mode· string · optionnel · current | timeline
current returns the representative/current shape; timeline returns bounded progression frames where supported.relationship_depth· integer · optionnel
Bounded cross-hazard traversal depth when relationships is included.
Exemple d'appel{"name": "get_event", "arguments": {"pack_id": "texte", "event_id": "texte", "source_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "event": {}, "reason": "texte", "pack_id": "texte", "event_id": "texte", "geometry": {}, "guidance": {}, "included": [], "warnings": [], "available": {}, "next_step": {}, "source_id": "texte"}} - get_pack≈ 459 tokens
Inspect one exact data pack ID for its metrics, time coverage, and query metadata before get_data.
Paramètres, retour & exemple (1)
Paramètrespack_id· string · requis
Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
Exemple d'appel{"name": "get_pack", "arguments": {"pack_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "detail": "lite", "reason": "texte", "catalog": "data", "pack_id": "texte", "sources": [], "guidance": {}, "warnings": [], "full_call": {}, "next_step": {}, "provenance": {}, "request_id": "texte"}} - get_tool_help≈ 542 tokens
Describe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.
Paramètres, retour & exemple (3)
Paramètrestopic· string · optionnel · overview | data | disasters | custom_data | geometry
Workflow overview. Do not combine with tool_name.question· string · optionnel
Optional question used only with a topic overview.tool_name· string · optionnel
Exact tool name from tools/list. Do not combine with topic.
Exemple d'appel{"name": "get_tool_help", "arguments": {"topic": "overview", "question": "texte", "tool_name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "error": {}, "title": "texte", "access": {}, "reason": "texte", "purpose": "texte", "examples": [], "guidance": {}, "warnings": [], "next_step": {}, "tool_name": "texte", "provenance": {}}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».