Skip to content

Biohotspot MCP server

io.github.PascalSun/biohotspotPascalSunstreamable-httpv0.9.0Scanned

Ocean data for any coast or sea, Australian marine park facts and Marxan reserve design.

31 tools: 3 can delete or cancel things, 1 do something that can't be undone, 11 change things and 16 only read.

Tools: 3 delete, 1 irreversible, 11 write, 16 read.
  • Reads private data · 2
  • Reads text others write · 3
  • Can send data out · 2
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Biohotspot MCP server can do

The Biohotspot MCP server is published by the GitHub account PascalSun. It has 31 tools. It can delete or cancel things (3 tools: delete_scenario, update_project and remove_project_from_list), do things that cannot be undone, such as sending, paying or publishing (email_report) and create or change data (11 tools: understand_area, simulate, save_scenario, run_scenario and 7 more). 16 tools only read.

2 tools read private data (list_project_data and read_paper); 3 tools bring in text other people can write (add_project_data, share_project and email_report); 2 tools can send data out of your system (add_project_data and email_report). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 0.9.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

31 tools

Deletes or cancels 3Claude Code: deny
  • delete_scenarioPermanently delete one of your own saved scenarios and the runs kept with it, as the website's delete does.No findings

    Why it is in this group

    • The name "delete_scenario" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Permanently delete one of your own saved scenarios and the runs kept with it, as the website's delete does. It cannot be undone. Only the person who saved a scenario can delete it; projects and their data cannot be deleted with these tools. Tell the user the scenario's name and ask them to confirm before calling it.

    Annotations the server declares

    • title: Delete a scenario
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • remove_project_from_listTake a project off your list: a public project you loaded, or a project shared with you, which you then leave (its team must add you again for you to see its team-only data).No findings

    Why it is in this group

    • The name "remove_project_from_list" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Take a project off your list: a public project you loaded, or a project shared with you, which you then leave (its team must add you again for you to see its team-only data). Your own projects cannot be removed this way. Ask the user before calling it for a shared project.

    Annotations the server declares

    • title: Take a project off your list
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • update_projectRename one of your projects or replace its area (a GeoJSON polygon; the data check runs again).No findings

    Why it is in this group

    • The name "update_project" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Rename one of your projects or replace its area (a GeoJSON polygon; the data check runs again). Overwrites the old name or area. Needs owner or editor rights; who can see the project is changed on the website only.

    Annotations the server declares

    • title: Rename or redraw a project
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • email_reportEmail a scenario's PDF report to up to 10 people with a link to the scenario, in your name (replies reach you), as the website's Share report does.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Email a scenario's PDF report to up to 10 people with a link to the scenario, in your name (replies reach you), as the website's Share report does. Side effect: an email is sent. Confirm the addresses with the user first.

    Annotations the server declares

    • title: Email a scenario report
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Changes things 11Claude Code: ask
  • add_project_dataAdd 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 …Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "add_project_data" says "add": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Add data to a project
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • create_projectCreate a Biohotspot project of yours for an area on the sea: a name and a GeoJSON polygon.No findings

    Why it is in this group

    • The name "create_project" says "create": a word for a change.
    Description, as the server wrote it
    Create a Biohotspot project of yours for an area on the sea: a name and a GeoJSON polygon. Biohotspot then runs its data check (what data covers the area). Side effect: adds a project you own; nothing else changes. Needs a verified sign-in.

    Annotations the server declares

    • title: Create a project
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • finish_uploadFinish a file added to a project (list_project_data shows those waiting): say what it is (title, source, year, licence: cc-by, cc0, cc-by-nc, other-open, restricted or unsure; item…No findings

    Why it is in this group

    • The name "finish_upload" says "upload": a word for a change.
    Description, as the server wrote it
    Finish a file added to a project (list_project_data shows those waiting): say what it is (title, source, year, licence: cc-by, cc0, cc-by-nc, other-open, restricted or unsure; item = the data-check item it fills), match its columns (`mapping`, {field: column}, e.g. {"scientificName": "species"}), run Biohotspot's checks and, unless accept is false, use it so it shows on the map and counts in the data check. What is not given keeps its current value. Returns the check's verdict. Needs owner or editor rights.

    Annotations the server declares

    • title: Finish an upload
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • load_public_projectAdd a public project (list_public_projects) to your list, view only, to look at and plan in it.No findings

    Why it is in this group

    • The description's first verb is "add": a word for a change.
    Description, as the server wrote it
    Add a public project (list_public_projects) to your list, view only, to look at and plan in it. Side effect: it appears in your project list; nothing else changes.

    Annotations the server declares

    • title: Add a public project to your list
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • look_in_project_dataWhat a project team's own data (their accepted uploads) holds at a point on the sea within `km` (default 1), or inside a polygon: per upload, how many features are there and a few …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What a project team's own data (their accepted uploads) holds at a point on the sea within `km` (default 1), or inside a polygon: per upload, how many features are there and a few of their names, or a grid's value at the point. Only the data you may see on that project. Read-only.

    Annotations the server declares

    • title: Look in a project's own data
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • make_reportMake a PDF report and get a link to it, good for a day: give project_id for the project's data report (what data covers the area, what is missing, the team's files and scenarios) o…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Make a PDF report and get a link to it, good for a day: give project_id for the project's data report (what data covers the area, what is missing, the team's files and scenarios) or scenario_id for a scenario report (its habitats against their targets, its kept Marxan runs compared, the best run habitat by habitat). The PDF is built when the link is opened, for the person who asked. Read-only.

    Annotations the server declares

    • title: Make a PDF report
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • run_scenarioRun Marxan for one of your saved scenarios with its saved settings (any setting given here replaces the saved one for this run) and keep the run with the scenario, as the website d…No findings

    Why it is in this group

    • The name "run_scenario" says "run": a word for a change.
    Description, as the server wrote it
    Run Marxan for one of your saved scenarios with its saved settings (any setting given here replaces the saved one for this run) and keep the run with the scenario, as the website does. Takes a few seconds to a minute; returns the run's summary and each habitat's result. Side effect: adds a run; nothing is overwritten. Only the person who saved the scenario can run it.

    Annotations the server declares

    • title: Run a saved scenario (Marxan)
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • save_scenarioSave a scenario in one of your projects, where its team sees it on the website: a name, an area (a GeoJSON polygon, optional) and Marxan settings that run_scenario then uses.No findings

    Why it is in this group

    • The name "save_scenario" says "save": a word for a change.
    Description, as the server wrote it
    Save a scenario in one of your projects, where its team sees it on the website: a name, an area (a GeoJSON polygon, optional) and Marxan settings that run_scenario then uses. Side effect: adds a scenario; nothing is overwritten or deleted. Needs a verified sign-in and a place on the project's team.

    Annotations the server declares

    • title: Save a scenario
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • share_projectShare one of your projects with a person by email, as an editor or a viewer: Biohotspot emails them a link in your name.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Share one of your projects with a person by email, as an editor or a viewer: Biohotspot emails them a link in your name. Side effect: an email is sent and they join the project's team. Only adds people: someone already on the team keeps their role (change roles on the website). Needs owner or editor rights. Confirm the address with the user first.

    Annotations the server declares

    • title: Share a project
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • simulateRun the Marxan optimiser on Biohotspot's planning data (Exmouth Gulf, Western Australia, for now): the cheapest set of planning squares that meets every habitat target.1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "simulate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run the Marxan optimiser on Biohotspot's planning data (Exmouth Gulf, Western Australia, for now): the cheapest set of planning squares that meets every habitat target. `polygon` protects the squares mostly inside it (unless `protect` is given); the other settings change targets, compactness and what stays open. Takes a few seconds; returns the summary, each habitat's result and the best solution. Nothing is saved: use save_scenario and run_scenario to keep a run in a project.

    Annotations the server declares

    • title: Run the protection options (Marxan)
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • understand_areaCheck 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check an area against its targets
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 16Show 16 read-only tools
  • compare_runsCompare a scenario's kept runs (up to 50, newest first): for each, the targets met, area and cost of the best solution and its settings, ranked best first (most targets met, then l…No findings

    Why it is in this group

    • The name "compare_runs" says "compare": a word for reading.
    Description, as the server wrote it
    Compare a scenario's kept runs (up to 50, newest first): for each, the targets met, area and cost of the best solution and its settings, ranked best first (most targets met, then lowest cost, then smallest area), with why each other run ranks lower. Read-only.

    Annotations the server declares

    • title: Compare a scenario's runs
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • find_layersFind Biohotspot map layers by words (e.g.No findings

    Why it is in this group

    • The name "find_layers" says "find": a word for reading.
    Description, as the server wrote it
    Find Biohotspot map layers by words (e.g. 'seagrass', 'coral bleaching') among its 1,600+ world layers. Returns ids, names and categories (25 by default), and whether each can be read with get_features: only layers whose licence lets Biohotspot share their features are (the others still show in look_here and look_in_area). Also finds the Exmouth Gulf example project's open layers (exmouth_…). Read-only.

    Annotations the server declares

    • title: Find map layers
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_featuresGet 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 mo…No findings

    Why it is in this group

    • The name "get_features" says "get": a word for reading.
    Description, as the server wrote it
    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). Give an id that find_layers marks get_features: true. Read-only.

    Annotations the server declares

    • title: Read a layer's features
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_habitatGet one habitat across Australia's marine parks, as its Biohotspot page shows it: the parks that hold it with their figures, sources and the page's address.No findings

    Why it is in this group

    • The name "get_habitat" says "get": a word for reading.
    Description, as the server wrote it
    Get one habitat across Australia's marine parks, as its Biohotspot page shows it: the parks that hold it with their figures, sources and the page's address. Give its id from list_habitats or part of its name. Read-only.

    Annotations the server declares

    • title: A habitat across marine parks
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_layer_yearsHow many features of a world map layer fall in each year (for layers with dates, such as sightings or bleaching surveys): the series the map's year slider draws.No findings

    Why it is in this group

    • The name "get_layer_years" says "get": a word for reading.
    Description, as the server wrote it
    How many features of a world map layer fall in each year (for layers with dates, such as sightings or bleaching surveys): the series the map's year slider draws. Give a find_layers id. Read-only.

    Annotations the server declares

    • title: A layer's features by year
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_marine_parkGet 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, …No findings

    Why it is in this group

    • The name "get_marine_park" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Australian marine park facts
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_projectGet one of your projects: its area's bounding box and size, its data check (each data type covered, partial or missing, with the best layer found) and your role.No findings

    Why it is in this group

    • The name "get_project" says "get": a word for reading.
    Description, as the server wrote it
    Get one of your projects: its area's bounding box and size, its data check (each data type covered, partial or missing, with the best layer found) and your role. full=true adds the boundary as GeoJSON and every layer found. Read-only.

    Annotations the server declares

    • title: Read a project
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_habitatsList the habitats Biohotspot measures across Australia's marine parks (mangroves, the modelled kelp forest biome and tidal marshes, for now): each one's id, name, how many parks ho…No findings

    Why it is in this group

    • The name "list_habitats" says "list": a word for reading.
    Description, as the server wrote it
    List the habitats Biohotspot measures across Australia's marine parks (mangroves, the modelled kelp forest biome and tidal marshes, for now): each one's id, name, how many parks hold it and whether it has a page. Read-only.

    Annotations the server declares

    • title: List the habitats
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_project_dataList the data a project's team added, with each file's status (receiving, checked, ready, failed).Reads private dataNo findings

    Why it is in this group

    • The name "list_project_data" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "file": it reads files.
    Description, as the server wrote it
    List the data a project's team added, with each file's status (receiving, checked, ready, failed). Read-only.

    Annotations the server declares

    • title: Read a project's data
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_projectsList your Biohotspot projects and the ones shared with you: name, area, your role and how complete their data is.No findings

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.
    Description, as the server wrote it
    List your Biohotspot projects and the ones shared with you: name, area, your role and how complete their data is. Read-only.

    Annotations the server declares

    • title: List your projects
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_public_projectsList Biohotspot's public projects, the worked examples first: name, area and how complete their data is, and whether each is already in your list.No findings

    Why it is in this group

    • The name "list_public_projects" says "list": a word for reading.
    Description, as the server wrote it
    List Biohotspot's public projects, the worked examples first: name, area and how complete their data is, and whether each is already in your list. Read-only.

    Annotations the server declares

    • title: List the public projects
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_scenariosList the scenarios saved by you and by the teams of your projects (or one project's, with project_id): name, project, who saved it and its last run's headline numbers.No findings

    Why it is in this group

    • The name "list_scenarios" says "list": a word for reading.
    Description, as the server wrote it
    List the scenarios saved by you and by the teams of your projects (or one project's, with project_id): name, project, who saved it and its last run's headline numbers. Read-only.

    Annotations the server declares

    • title: List your scenarios
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • look_hereList 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 wo…No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    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 its nearest few items each. Read-only. Use it to learn what a place holds; give `layer` (an id from the answer) for that layer in full.

    Annotations the server declares

    • title: Look at a place
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • look_in_areaList every Biohotspot map layer with data inside a polygon on the sea, with its nearest few items each.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List every Biohotspot map layer with data inside a polygon on the sea, with its nearest few items each. Read-only. Give `layer` (an id from the answer) for that layer in full.

    Annotations the server declares

    • title: Look inside an area
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • read_paperRead a research library document's text, page by page (pages `from_page` to `to_page`, at most 30 at once; default the first 5).Reads private dataNo findings

    Why it is in this group

    • The name "read_paper" says "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "document": it reads documents.
    Description, as the server wrote it
    Read a research library document's text, page by page (pages `from_page` to `to_page`, at most 30 at once; default the first 5). Give a document id from search_papers. Documents without a PDF in the library have no pages. Read-only.

    Annotations the server declares

    • title: Read a library document
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • search_papersSearch 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 defaul…No findings

    Why it is in this group

    • The name "search_papers" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search the research library
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

12 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__biohotspot__add_project_data",
      "mcp__biohotspot__email_report"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:23 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
15
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://biohotspot.ai4wa.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://biohotspot.ai4wa.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 15 tools that change things (3 destructive, 1 irreversible, 11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://biohotspot.ai4wa.com/mcp: tools/list returned 31 tools to an anonymous client, including delete_scenario (destructive), update_project (destructive), remove_project_from_list (destructive), email_report (irreversible), understand_area (write) and 10 more

    What this check looks for

Posture changes

  1. Nov 14, 2026
    • Tools that change things, listed without credentials: 3 to 15

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "simulate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 15.View diff
    • Tools that change things, listed without credentials: 3 to 15
  2. Tools19 added, 6 changed.+19 added~6 changedView diff
  3. Tools2 added, 2 removed, 10 changed.+2 added−2 removed~10 changedView diff

Install

Pinned to version 0.9.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http biohotspot https://biohotspot.ai4wa.com/mcp
claude mcp add --transport http biohotspot https://biohotspot.ai4wa.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__biohotspot__look_here",
      "mcp__biohotspot__look_in_area",
      "mcp__biohotspot__list_scenarios",
      "mcp__biohotspot__compare_runs",
      "mcp__biohotspot__find_layers",
      "mcp__biohotspot__get_features",
      "mcp__biohotspot__get_marine_park",
      "mcp__biohotspot__search_papers",
      "mcp__biohotspot__list_projects",
      "mcp__biohotspot__get_project",
      "mcp__biohotspot__list_project_data",
      "mcp__biohotspot__list_habitats",
      "mcp__biohotspot__get_habitat",
      "mcp__biohotspot__get_layer_years",
      "mcp__biohotspot__read_paper",
      "mcp__biohotspot__list_public_projects"
    ],
    "ask": [
      "mcp__biohotspot__understand_area",
      "mcp__biohotspot__simulate",
      "mcp__biohotspot__save_scenario",
      "mcp__biohotspot__run_scenario",
      "mcp__biohotspot__add_project_data",
      "mcp__biohotspot__look_in_project_data",
      "mcp__biohotspot__create_project",
      "mcp__biohotspot__finish_upload",
      "mcp__biohotspot__load_public_project",
      "mcp__biohotspot__share_project",
      "mcp__biohotspot__make_report",
      "mcp__biohotspot__email_report"
    ],
    "deny": [
      "mcp__biohotspot__delete_scenario",
      "mcp__biohotspot__update_project",
      "mcp__biohotspot__remove_project_from_list"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as biohotspot. Review it before you use it.

Capability tags behind 5 rules
  • mcp__biohotspot__list_project_data private-data
  • mcp__biohotspot__add_project_data untrusted-input, outbound
  • mcp__biohotspot__read_paper private-data
  • mcp__biohotspot__share_project untrusted-input
  • mcp__biohotspot__email_report untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.PascalSun/biohotspot/verify?hash=c0f329b1e37d440a71596aa8a1a314c5a46eca3da3d2935dc3146922639b412c" | jq -e '.changed == false'

Pinned hash c0f329b1e37d, from Nov 13, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.PascalSun/biohotspot/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.PascalSun/biohotspot
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.PascalSun/biohotspot.svg)](https://radar.anlyon.com/servers/io.github.PascalSun/biohotspot)

Source: MCP Registry. Synced Nov 13, 2026, 02:17 UTC.

Biohotspot MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Biohotspot MCP server safe?

No scan can promise that. What its definitions show: 31 tools, 15 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Biohotspot MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: delete_scenario, update_project and remove_project_from_list.

Can the Biohotspot MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: email_report.

What tools does the Biohotspot MCP server have?

31 tools: 3 destructive, 1 irreversible, 11 write, 16 read. delete_scenario, update_project, remove_project_from_list, email_report, understand_area, simulate, save_scenario, run_scenario and 23 more.

Does the Biohotspot MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Biohotspot MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): add_project_data and email_report.

Has the Biohotspot MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.