accueil / serveurs / Géo & Temps / com.daedalmap/boundaries
com.daedalmap/boundaries
serveur MCP (Model Context Protocol) · com.daedalmap/boundaries 1.3.2
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/boundaries est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.daedalmap/boundaries » 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 7 outils
- compare_geographies≈ 1074 tokens
Compare two known loc_ids using selected reference-graph identity and direct relationship evidence. Verified Admin ancestry can prove containment; a typed graph edge can prove only the relation it declares. An explicit negative edge returns no_overlap; a missing edge returns unknown. This tool never reads polygons or computes shape intersections. Use an external identifier bridge before this call when the input is not a loc_id. No payment required.
Paramètres, retour & exemple (9)
Paramètresas_of· string · optionnel
ISO date or year applied to both identities.items· array · optionnel
Bounded geography pairs to compare in one call.batch_id· string · optionnel
Optional caller-supplied batch id for tracing.left_as_of· string · optionnel
Optional ISO date or year for the left identity; overrides as_of.request_id· string · optionnel
Optional caller-supplied request id for tracing.left_loc_id· string · optionnel
First DaedalMap loc_id.right_as_of· string · optionnel
Optional ISO date or year for the right identity; overrides as_of.right_loc_id· string · optionnel
Second DaedalMap loc_id.include_successors· boolean · optionnel
Include direct successors and present-day descendants for maintained historical identities. Default true.
Exemple d'appel{"name": "compare_geographies", "arguments": {"as_of": "texte", "items": [], "batch_id": "texte", "left_as_of": "texte", "request_id": "texte", "left_loc_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "error": {}, "reason": "texte", "results": [], "batch_id": "texte", "guidance": {}, "warnings": [], "next_step": {}, "item_count": 1, "request_id": "texte", "failed_count": 1, "clarification": {}}} - 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_geography≈ 513 tokens
Inspect one published geometry family across scopes or one scope across families. Returns coverage and known editions from catalog metadata only. Optional year selects the latest admitted edition no later than that year when the selected catalog has an edition index; an unavailable index is reported explicitly.
Paramètres, retour & exemple (3)
Paramètresyear· integer · optionnelscope_id· string · optionnelfamily_id· string · optionnel
Exemple d'appel{"name": "get_geography", "arguments": {"year": 1, "scope_id": "texte", "family_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "reason": "texte", "catalog": "geometry", "coverage": [], "guidance": {}, "scope_id": "texte", "warnings": [], "family_id": "texte", "next_step": {}, "provenance": {}, "request_id": "texte", "admin_spine": {}}} - get_loc_id_info≈ 836 tokens
Look up one known loc_id or a small batch in the selected reference graph. Return its identity and directly recorded loc_id connections, with family, direction, and relationship evidence. Each ID returns at most 50 connections and an explicit has_more flag. This tool does not expand descendants, infer containment, read shapes, search catalogs, or consult external adapters. No payment required.
Paramètres, retour & exemple (4)
Paramètresloc_id· string · optionnel
DaedalMap loc_id, e.g. 'USA-CA'.loc_ids· array · optionnel
Up to 10 known loc_ids, including a resolve_point stack.batch_id· string · optionnel
Optional caller-supplied batch id for tracing.request_id· string · optionnel
Optional caller-supplied request id for tracing.
Exemple d'appel{"name": "get_loc_id_info", "arguments": {"loc_id": "texte", "loc_ids": [], "batch_id": "texte", "request_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "iso3": "texte", "name": "texte", "error": {}, "family": "texte", "loc_id": "texte", "reason": "texte", "results": [], "batch_id": "texte", "guidance": {}, "has_more": true, "warnings": []}} - 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_shape≈ 788 tokens
Shape lookup for exact existing loc_ids only. The default returns shape availability, centroid, and bounding box; include_polygon=true adds GeoJSON coordinates. Obtain any descendant IDs before this call. Historical geometry is returned first and successors are never substituted automatically. Year selection is not yet supported.
Paramètres, retour & exemple (5)
Paramètresloc_id· string · optionnel
DaedalMap loc_id, such as USA-CA-037, USA-Z-00601, USA-NWSFZ-AKZ317, EEZ-USA, or IHO1953-240001002.loc_ids· array · optionnel
Exact DaedalMap loc_ids to fetch in one call. Default public cap is deployment-configurable and lower when include_polygon is true.batch_id· string · optionnel
Optional caller-supplied batch id for tracing.request_id· string · optionnel
Optional caller-supplied request id for tracing.include_polygon· boolean · optionnel
When true, include the full GeoJSON geometry. Default false.
Exemple d'appel{"name": "get_shape", "arguments": {"loc_id": "texte", "loc_ids": [], "batch_id": "texte", "request_id": "texte", "include_polygon": true}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "error": {}, "items": [], "reason": "texte", "missing": 1, "batch_id": "texte", "guidance": {}, "warnings": [], "available": 1, "next_step": {}, "requested": 1, "selection": "exact_loc_ids"}} - 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é ».