_ registry / mcp streamable-http · checked 26h ago

biohotspot

https://biohotspot.ai4wa.com

Registry code: bcb24c8434d7033e

api record

Biohotspot: ocean data for any coast or sea, and marine protection planning. Look at a place (look_here), understand an area's habitats against their targets (understand_area), simulate protection options (simulate, on projects with planning data), find layers and their features, get an Australian marine park's facts (get_marine_park), search papers, and work with the signed-in user's projects. add_project_data is the only tool that changes anything: it downloads a file from a public link the user gives and adds it to one of their projects.

endpoint
https://biohotspot.ai4wa.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is biohotspot live?
Yes — it answered the hub's last check (checked 26h ago). It answered 100% of checks over the last 30 days.
Is biohotspot free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does biohotspot have?
12 tools: look_here, understand_area, get_project, list_project_data, look_in_area, simulate, find_layers, get_features, ….
Is biohotspot safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,176ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 12 tools
12 auth-required 12 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • look_here auth-required never probed

    List every Biohotspot map layer with data within `km` of a point on the sea (a place being studied, not the user's location): habitats, wildlife, human uses, protected areas and world ocean maps, with a few values from each. Read-only. Use it to learn what a place holds.

    mcp-tool

    {
      "type": "object",
      "required": [
        "lon",
        "lat"
      ],
      "properties": {
        "km": {
          "type": "number",
          "description": "Radius in km (default 5)"
        },
        "lat": {
          "type": "number",
          "description": "Latitude of the place to look at, WGS84"
        },
        "lon": {
          "type": "number",
          "description": "Longitude of the place to look at, WGS84"
        }
      }
    }
    arguments 21 lines
  • understand_area auth-required 26h ago

    Check an area against its protection targets: which habitats it holds, how much of each, what is already protected, and how far each habitat is from its target. Give a polygon, or a point and radius_km. Outside Biohotspot's local planning data the answer comes from world maps and is marked rough: true. Read-only; nothing is saved.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lat": {
          "type": "number",
          "description": "Latitude of the place to look at, WGS84"
        },
        "lon": {
          "type": "number",
          "description": "Longitude of the place to look at, WGS84"
        },
        "polygon": {
          "type": "object",
          "description": "A GeoJSON Polygon (WGS84)"
        },
        "radius_km": {
          "type": "number"
        }
      }
    }
    arguments 20 lines
  • get_project auth-required never probed

    Get one of your projects: its area (GeoJSON), its data check (each data type covered, partial or missing) and your role. Read-only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "project_id"
      ],
      "properties": {
        "project_id": {
          "type": "integer"
        }
      }
    }
    arguments 11 lines
  • list_project_data auth-required never probed

    List the data a project's team added, with each file's status (receiving, checked, ready, failed). Read-only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "project_id"
      ],
      "properties": {
        "project_id": {
          "type": "integer"
        }
      }
    }
    arguments 11 lines
  • look_in_area auth-required never probed

    List every Biohotspot map layer with data inside a polygon on the sea, with a few values from each. Read-only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "polygon"
      ],
      "properties": {
        "polygon": {
          "type": "object",
          "description": "A GeoJSON Polygon (WGS84)"
        }
      }
    }
    arguments 12 lines
  • simulate auth-required 26h ago

    Run the Marxan optimiser on the example project's planning data (Exmouth Gulf, Western Australia only): the cheapest set of planning squares that meets every habitat target. `protect` = planning-square ids always included (understand_area returns them as `pus`); `target_pct` = one target for every habitat, in %. Takes a few seconds; returns the summary, each habitat's result and the best solution. Nothing is saved to your projects.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "reps": {
          "type": "integer",
          "description": "Runs, 1-20 (default 5)"
        },
        "protect": {
          "type": "array",
          "items": {
            "type": "integer"
          }
        },
        "target_pct": {
          "type": "number"
        }
      }
    }
    arguments 18 lines
  • find_layers auth-required never probed

    Find Biohotspot map layers by words (e.g. 'seagrass', 'coral bleaching') among its 1,600+ world layers. Returns ids, names, categories and licences (25 by default); vector layers can then be read with get_features. Read-only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer"
        },
        "query": {
          "type": "string"
        }
      }
    }
    arguments 14 lines
  • get_features auth-required never probed

    Get a vector layer's features as GeoJSON from Biohotspot's OGC API, optionally inside a bounding box [west, south, east, north]; up to `limit` features (500 by default, 5,000 at most). Collection ids: find_layers ids, or exmouth_<dataset> for the example project's open layers. Read-only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collection"
      ],
      "properties": {
        "bbox": {
          "type": "array",
          "items": {
            "type": "number"
          },
          "maxItems": 4,
          "minItems": 4
        },
        "limit": {
          "type": "integer"
        },
        "collection": {
          "type": "string"
        }
      }
    }
    arguments 22 lines
  • get_marine_park auth-required never probed

    Get the 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 licence, and the page's address. Give part of the park's name; `state` (wa, qld, nsw, vic, sa, tas, nt, com for Commonwealth waters) narrows it. Several matches return the list to choose from; parks under 10 km² or without enough open data have no page. Read-only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Park name or part of it, e.g. 'Ningaloo'"
        },
        "state": {
          "type": "string"
        }
      }
    }
    arguments 15 lines
  • search_papers auth-required never probed

    Search Biohotspot's research library (more than 5,200 papers and reports on coasts and marine habitats) for the words; returns titles, years and DOI links where known (10 by default, 50 at most). Read-only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer"
        },
        "query": {
          "type": "string"
        }
      }
    }
    arguments 14 lines
  • list_projects auth-required 26h ago

    List your Biohotspot projects and the ones shared with you: name, area, your role and how complete their data is. Read-only.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • add_project_data auth-required never probed

    Add data to a project from a public download link (GeoPackage, zipped Shapefile, GeoJSON, KML, CSV with coordinates or GeoTIFF, up to 200 MB): your own model's output, a survey, a map. Side effect: the file is downloaded, stored and added to the project, where its team can see it; nothing is deleted or overwritten. Biohotspot then checks it; follow its status with list_project_data and finish anything it asks for in the project's Uploads tab. Needs owner or editor rights.

    mcp-tool

    {
      "type": "object",
      "required": [
        "project_id",
        "url"
      ],
      "properties": {
        "url": {
          "type": "string"
        },
        "year": {
          "type": "integer"
        },
        "title": {
          "type": "string"
        },
        "source": {
          "type": "string",
          "description": "Who made it"
        },
        "licence": {
          "type": "string",
          "description": "cc-by, cc0, cc-by-nc, other-open, restricted or unsure"
        },
        "project_id": {
          "type": "integer"
        }
      }
    }
    arguments 29 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id bcb24c8434d7033e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bcb24c8434d7033e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/bcb24c8434d7033e/badge.svg)](https://brick.blue/agent/bcb24c8434d7033e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.