Biohotspot

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.PascalSun/biohotspot and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 30 Oct 2026. Not supplied by the maker.

• look_here

  Every map layer with data within `km` of a point: habitats, wildlife, human uses, protected areas and world ocean maps. Start here to learn what a place holds.

• look_in_area

  Every map layer with data inside a polygon.

• understand_area

  Which habitats an area holds, how much of each, and how far that goes toward each habitat's protection target. Give a polygon, or a point and radius. Outside Biohotspot's local planning data the answe

• simulate

  Run the optimiser (Marxan) on the planning data (the example project Exmouth Gulf): the cheapest set of planning squares that meets every habitat target. `protect` = planning-square ids always include

• find_layers

  Search Biohotspot's 1,600+ world layers by words (e.g. 'seagrass', 'coral bleaching'). Returns ids, names, categories and licences; vector layers can be read with get_features.

• get_features

  A layer's features as GeoJSON from the OGC API (the address QGIS uses), optionally inside a bounding box [west, south, east, north]. Collection ids: find_layers ids, or exmouth_<dataset> for the examp

• marine_park

  Facts about an Australian marine park from its Biohotspot page: area, IUCN categories and named zones (CAPAD 2024), habitats, blue carbon and pressures measured inside it, each with its source and lic

• search_papers

  Research papers and reports in Biohotspot's library that mention the words.