What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: query databases in plain language.Similar tools
Listed for the same task: query databases in plain languageReviews
No review yet. Used AgenticGeoMate? Be the first to help others choose.What it does
AgenticGeoMate is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: sql querying. That makes it a candidate for tasks such as query databases in plain language or build data pipelines.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 3h ago (live check)Hosted endpoint
https://geomate.nlp-tlp.org/mcpstreamable-http
In Claude Code: claude mcp add --transport http agenticgeomate https://geomate.nlp-tlp.org/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"agenticgeomate": {
"url": "https://geomate.nlp-tlp.org/mcp"
}
}
}Reliability
Re-tested about every 3 days · last check 3h agoObserved endpoint availability: the share of our conclusive checks that got an answer. A request for a key or sign-in counts as an answer (the server is up, its access is protected). Timeouts, unreachable endpoints, server errors and invalid MCP replies count as failures; rate-limited checks and checks during our own incidents are not counted. This is what we observed at each check, not continuous uptime: an outage between two checks may go unseen. The 90-day figure will appear once 90 days of checks exist (checks since 21 Nov 2026). How we measure
Live check
Electra Index connected to the hosted endpoint 3h agoONLINE AgenticGeoMate answered an MCP connection on 21 Nov 2026 and introduced itself as AgenticGeoMate (MCP protocol 2025-06-18).
92 tools offered to AI assistants
list_datasets· Use when the user asks which datasets they can read in the data library: their own uploads, datasets shared with them and datasets published publicly. Optional `query` filters by name or description. Returns each dataset's id, name, descripdescribe_dataset· Use to look at one data-library dataset (`dataset_id` from list_datasets) before querying or reusing it. Returns its name, description, visibility, citation, source link and licence (check the licence before reusing it), the projects it belquery_features· Use to read the features or rows of a data-library layer (`layer_id` from describe_dataset), a WA data library layer (`layer_id` "lib:..." from search_wa_data_library, e.g. the geology polygons in a box or of one rock type) or a table (`tabget_dataset_feature· Use to read one feature of a published data-library layer (`layer_id` and `feature_id` from query_features). Returns all of its attributes and its GeoJSON geometry.search_dataset_documents· Use to find words in the PDF documents of the data library that the user can read. Accepts Postgres websearch syntax (quoted phrases, OR, -excluded). Returns each hit's document id, dataset, page and a snippet with <mark> around the matchesread_dataset_document· Use to read one page of a data-library document (`document_id` from list_datasets or search_dataset_documents; `page` is 1-based). Returns the page's text.describe_raster· Use to see what a raster dataset holds before sampling it (`raster_id` from list_datasets or list_geophysics_grids). Returns its size, bands, data type, nodata, resolution, WGS84 extent, per-band min / max / mean / p2 / p98, and its classessample_raster· Use to read a raster's values at up to 50 WGS84 points ({lon, lat}). Returns the value of each band at each point; a point outside the raster has no value.get_image· Use to read the details of an image dataset (`image_id` from list_datasets). Returns its size, format, colour mode and frame count; for the image's owner, also its camera metadata (EXIF) without the artist field.get_download_url· Use when the user asks to download a dataset's original uploaded file. Returns a short-lived download link. Available to the dataset's owner, and to anyone when the owner allowed original download of a public dataset.upload_data· Use when the user asks to add a file from a public https link to their own data library (the platform downloads it; links to private or internal addresses are refused). Accepts any file the library takes: a PDF, Word or PowerPoint document,estimate_download· Use when the user wants to download the files of public exploration reports and publications, to count the files and their size first. It saves the count as an estimate, under an id that prepare_download takes; nothing is packaged, sent, ch
Show 80 more
prepare_download· Use only after the user has agreed to the size that estimate_download reported, to package those files for the user to download. The package is built in the background as ZIP parts of about 10 GB, each listing its files (MANIFEST.csv) and adownload_status· Use to check on one of the user's own download packages or estimates (the id from estimate_download or prepare_download). Read-only. Returns its state, its progress (files and bytes done, time left) and, for each finished ZIP part, a temporgeothought_projects· Use when the user asks which GeoThought projects they have. Returns each of the signed-in user's projects: id, name, how many documents, and the schemas (with their question counts) it reads with. Pass a project id to geothought_project orgeothought_start_agent_reading· Use when the user wants this assistant, rather than GeoThought's own model, to read a project's documents and answer its schemas' questions. Queues the documents that have no answer yet; the answers given are saved with the project. Optionageothought_next_document· Use during an assistant reading (after geothought_start_agent_reading) to take the next document. Returns `task` and `token` (needed for every call about this document), the `instructions` and the `checklist` of questions (Q1..Qn), and thegeothought_document_sections· Use to fetch another page of sections of the document taken with geothought_next_document (page 0 is the first). Returns that page's numbered sections and their text.geothought_submit_replies· Use to send the answers for some or all sections of the document being read: `replies` is {"<section number>": {"Q1": {"status": "found", "value": ..., "quote": "verbatim from that section"}, ...}}, leaving out the questions a section doesgeothought_release_document· Use to hand a document back unread, e.g. when it is too long to read now; it is offered again later. Returns whether it was released.geothought_reading_status· Use to check a project's reading. Returns its latest reading's state: documents done, being read and waiting, the reader, and a short reason if it failed.geothought_stop_reading· Use when the user asks to stop a project's reading. Documents not yet taken are dropped; answers already saved stay. Returns the reading's final state.geothought_questions· Use to list the user's saved GeoThought questions (their question library). Returns each question's id, text and answer type.geothought_save_question· Use to save a question to the user's library; with `id`, it replaces that saved question. `question` is {text, answer_type: boolean|enum|numeric|date|text|place|list|relation, enum_values?, unit?, relation?, context?, temporal?, spatial?}.geothought_delete_question· Use when the user asks to delete a saved question from their library. Returns the deleted id.geothought_templates· Use to list GeoThought's ready-made schemas (refs t:<id>), which a project can read with as they are. Returns each one's ref, name, kind, description and question count.geothought_schemas· Use to list the user's own schemas (refs s:<id>). Returns each one's ref, name, kind, visibility and question count.geothought_get_schema· Use to read a schema's body by its ref (s:<id> for the user's own, t:<id> for a template). Returns the schema.geothought_draft_schema· Use when the user describes what they want to find out in documents and needs a schema for it. GeoThought's model drafts one; nothing is saved. kind: mindmap (questions grouped as a tree), relation (relations between things) or thoughtgraphgeothought_arrange_schema· Use to turn a set of questions into a schema of a kind: GeoThought's model groups and orders them; nothing is saved. Give `question_ids` of saved questions and/or `questions` objects, and optionally a `goal`. Returns the arranged schema. Ageothought_check_schema· Use to check a schema body before saving it. Returns what is wrong or missing in it (unreachable questions, bad edges, ...). A schema is {kind: mindmap|relation|thoughtgraph, name, description?, questions: [Question], tree?, edges?}. A Quesgeothought_convert_schema· Use to turn a schema into another kind (mindmap, relation, thoughtgraph); nothing is saved. Returns the converted schema.geothought_save_schema· Use to save a schema as the user's own (private); with `id`, it replaces that schema of theirs (the projects reading with it follow). Returns its ref (s:<id>) to put in a project. A schema is {kind: mindmap|relation|thoughtgraph, name, descgeothought_delete_schema· Use when the user asks to delete one of their schemas. Projects reading with it keep their answers. Returns the deleted id.geothought_project· Use to look at one GeoThought project (the user's own or a public one). Returns its schemas, period, documents (each with its corpus and key; an uploaded file with how far it has been read: text, layout, OCR), whether it is the user's and wgeothought_create_project· Use when the user asks for a new GeoThought project. Creates a private project with a name, the schemas it reads with (refs from geothought_schemas / geothought_templates), optionally its documents ([{corpus, key}] from geothought_find_docugeothought_update_project· Use to change one of the user's projects: name, description, schemas (refs; replaces the list), corpora, period. Making it public is geothought_publish_project. Returns the project's new settings.geothought_copy_project· Use to copy a project (the user's or a public one) into a new private project of theirs; uploaded files of another account are left out. Returns the copy's id.geothought_delete_project· Use when the user asks to delete one of their projects, with its document list and its readings. Cannot be undone. Returns the deleted id.geothought_find_documents· Use to find documents to add to a project. mode=search: by words (`query`); mode=suggest: documents likely to answer the questions of `schemas` (refs) or of `project`'s schemas; mode=browse: a corpus's catalogue by words (`query`), `tags` (geothought_add_documents· Use to add documents to one of the user's projects: `documents` [{corpus, key, title?}] and/or `uploads` (dataset ids of their own files, from geothought_uploads or upload_data). Only the user's own files can be added; GeoThought reads at mgeothought_remove_documents· Use to take documents out of a project (`documents` [{corpus, key}], `uploads` ids, or all=true). The files themselves stay. Returns how many were removed and the project's document count.geothought_uploads· Use to list the user's own document files (every PDF, Word or PowerPoint file in their data library, however it was uploaded). Returns how far each has been read (state; steps: text, layout, OCR), a short reason when a step failed, the projgeothought_edit_document_details· Use when the user asks to change the details of one of their own uploaded documents: its title, year, operator or commodity. Only the fields given are changed, and the new details show in every project that holds the document. Returns the dgeothought_delete_upload· Use when the user asks to delete one of their files: it is taken out of every project, its answers deleted, and the file moved to their data library's trash. Returns what was deleted.geothought_models· Use to see which models the user can read and ask with (GeoThought's own and any they added on the website). Returns each model's id and name, and which ones the user chose.geothought_read_plan· Use before reading a project to see what it would take. Returns the documents, questions, answers already there and what is left. Optional `schemas` (names) and `documents` [{corpus, key}].geothought_start_reading· Use when the user asks GeoThought's own reader to read one of their projects: every document is asked its schemas' questions and the answers are kept with their page and box. `model`: a model id from geothought_models (default: the user's cgeothought_answers· Use to read a project's answers: for a page of its documents (offset, limit) or one `document` {corpus, key}. Returns each question's answer with the quote, page and box it came from. Optional `schema` (name) for its questions only.geothought_insights· Use to summarise a project's answers to one schema. Returns, per question, the counts and values; relations; places and years; a thought graph's routes.geothought_ask· Use when the user asks a question about a project's documents in words. GeoThought answers from the project's documents and saved answers. Returns the answer with each claim cited to a document page. For a follow-up, `earlier_questions` maygeothought_publish_project· Use only when the user asks to make one of their projects public, or private again. public=true: anyone can then open the project, its documents (including the user's own uploaded files in it) and its answers, through the returned link andsearch_tenement_holders· Use when the user names a company or project and wants what it holds in Western Australia: its tenements, drillholes and WAMEX reports. A company groups its legal names ("Northern Star (KLV) Pty Ltd", "Northern Star Resources Ltd", ...) undfind_drillholes· Use when the user asks which drillholes there are in a place or of a company or project (WA open-file and company collars). Filter by a bbox or a point and radius, and/or a company or project key from search_tenement_holders; drilling typesearch_wa_data_library· Use to find a Western Australian open-file dataset from the DMIRS Data and Software Centre (DASC) by its title: about 600 datasets (geology, geophysics compilations, mineralisation, WAROX field data, heritage, land, infrastructure, ...) andget_wa_library_features· Use to see what one WA data library layer (a "lib:..." id from search_wa_data_library) holds around a point, e.g. the bedrock units, dykes, heritage places or WAROX observations around a prospect. Returns the features within the radius, sorget_outcrop_photos· Use when the user asks for field photographs of outcrops or rock samples near a point in Western Australia (GSWA's WAROX field database). Returns, for the nearest WAROX sites and samples that have photographs, their description and each phomake_map_link· Use to give the user a link that opens the public data map (https://geo.nlp-tlp.org/map) on a view that shows an answer. The view can set layers to turn on (map layer ids such as drillholes, tenements, wamex, geology_au, geology, faults, offind_drillhole_intercepts· Use when the user asks for downhole intercepts ("8 m @ 2.1 g/t Au from 120 m") of an element in the drillholes around a point. They are computed from the company assays the platform holds, by one stated rule: a run starts and ends on a sampmake_drillhole_section· Use when the user asks for a vertical cross-section through a drillhole. The section runs along the hole's own azimuth (east-west for a vertical hole or one whose direction was not recorded), as far as the drilling near the line reaches. Refind_on_map· Use to locate an identifier or a place on the map: a tenement ("E 53/1209"), a WAMEX report ("A12345"), a drillhole id, a map sheet, a place name, or coordinates in decimal degrees ("-30.75, 121.47"), degrees-minutes-seconds ("30°45'S 121°2measure_distance_or_area· Use when the user asks how long a line is or how large an area is. Give points as [[lon, lat], ...]; closed=true reads them as a polygon (the first point need not be repeated). Returns the geodesic (WGS84 ellipsoid) length of a line in km wget_geology_at_point· Use when the user asks what the geology is at a point in Western Australia. Returns the GSWA 1:500k unit and its place in its 1:250k sheet's stratigraphic column (map2loop: above, below, nearest contact and its type), the nearest fault (namsearch_data_catalogue· Use when the user asks what data the platform holds on a subject, or where a dataset comes from and under which licence. Searches the platform's data catalogue (geo.nlp-tlp.org/data). Returns each dataset's title, summary, family, coverage,get_catalogue_dataset· Use to read one data catalogue entry by its slug (from search_data_catalogue), e.g. before citing or downloading it. Returns its fields, coverage, period, citation and attribution, licence, the tables behind it, how to download it and an APlist_geophysics_grids· Use to find a public geophysics or terrain grid to read values from: GA's national gravity, magnetics (TMI, RTP, 1VD...), radiometrics, isostatic residuals, SGTool products and DEM, and GSWA's WA Moho and scanned geological map mosaics. Retget_place_summary· Use when the user asks for an overview of a 1:250k map area ('areas'), a geological province ('provinces'), a commodity ('commodities') or a Minedex mine or deposit ('mines'), built from the platform's own data. Without slug: returns the sufind_core_scans· Use when the user asks for drill core scanned by HyLogger (the national NVCL library, as CoreFlagging shows it): holes by name, operator or project (q), around a point (lon, lat, radius_km), in a bbox, and/or in a State. Returns each hole'sdownload_drillholes· Use when a signed-in user asks for drillhole data as a file: every hole within radius_km (at most 10) of a point, or one hole, as a CSV set (a zip of collars, survey, desurveyed path, assays and lithology, with a README) or as one OMF fileget_core_scan_hole· Use to read one HyLogger-scanned hole by its key (from find_core_scans). Returns where and what it is, the scanned depth range, logged geology per metre (summarised to up to 15 rock types and their metres), the spectral datasets and which wscore_point· Use when the user asks how prospective a location in Western Australia is for a metal (Au, Cu, Ni, W, Sn, Co, Ta, Mn). Returns the model's prospectivity score (%), tier, data coverage and uncertainty, the nearest known mineral site, the geoscore_region· Use when the user asks how prospective an area drawn as a polygon is for a metal. Scores an 8x8 grid of points inside the polygon and returns the median score (%), tier, the lowest and highest grid score, uncertainty and a mapUrl. A large oscore_route· Use when the user asks how prospective the ground is along a road, track or planned drive. Give the ordered vertices of the route (for example a Mapbox Directions geometry); the line is resampled every `spacing_km` and each sample is scoredtop_prospects· Use when the user asks where the highest-scoring ground for a metal is across Western Australia. Returns up to `n` spaced-apart cells of the precomputed prospectivity grid, sorted by score, highest first, each with its coordinates and a maplist_targets· Use when the user asks which metals can be scored. Returns the metals the prospectivity model supports.inspect_point· Use when the user asks what is known about the ground around a point in Western Australia: who holds it, what has been mined, found or drilled nearby, and what limits access. Returns a compact summary within `radius_km` of: tenure (whetherinspect_region· Use when the user asks for an overview of what is inside a rectangular area (a bounding box). Returns counts for the area: tenements (live, pending, dead), mines (MINEDEX), known deposits, open-file drillholes, company drillhole and surfaceget_drillhole_traces· Use when the user asks for the drillholes in an area with their downhole paths or gold grades. Give a bbox (west/south/east/north) or a point (lon/lat, with radius_km). Returns holes[], each with collar lon/lat, src (company or openfile) ancompare_points· Use when the user asks to compare two to eight candidate locations. For each point returns the prospectivity score and tier, tenure status, and the counts of nearby mines, drillholes and WAMEX reports over the point, with a mapUrl; rows areget_geochem· Use when the user asks for the assay geochemistry (sample concentrations) around a point. Returns, per sample type (STREA stream sediment, ROCKC rock chip, DRILL, SHALL, SOIL) and per element, concentration statistics in ppm (n, min, p50, pget_model_inputs_at_points· Use when the user asks for the geophysical or structural values the prospectivity model reads at specific points. For up to 25 points returns geophysics (magnetic and gravity intensity and derivatives) and structure (distances to faults andlist_sites· Use when the user asks for a list of known mineral sites, deposits or occurrences. Returns up to 200 sites, each with name, commodity, label, isPositive (whether the model uses it as a confirmed training example) and coordinates. Filter bylist_export_layers· Use when the user wants to know which data layers export_data can export. Returns each layer with its filters, row cap and whether a bbox is required. The layers are tenements, minedex, drillholes, wamex, activity (historical exploration),export_data· Use when the user wants a whole data layer as a file (GeoJSON or CSV) for their own analysis. Exports one layer from list_export_layers, optionally clipped to a bbox and filtered, and returns a presigned download URL, the row count and a smsubmit_job· Use for calls that may take longer than a minute, such as score_region over a large or data-dense area. Queues the named tool with its arguments and returns a taskId at once; get_job returns the result when it is ready. Only the user who quget_job· Use to check on a job queued with submit_job. Give its taskId; returns its status (pending, running, done or failed) with the result once done, or a short error message if it failed. A job queued by another user reads as not found.sql_tables· Use before writing SQL, to see which tables exist when a question needs data the other tools do not cover. Returns every queryable table, grouped by schema, with estimated row counts. Schemas: public (GSWA assays, training sites, geophysicssql_describe· Use before writing a query against a table, to get its column names and types. Geometry columns are EPSG:4326 (lon/lat). `schema` is optional: without it the table is looked up by name (or pass "source.drillholes").sql_query· Use when a question needs a custom query over the AgenticGeoMate geoscience database. Runs one read-only SELECT (or WITH/EXPLAIN) and returns the rows. Read-only is enforced by the database connection, not only checked: INSERT/UPDATE/DELETEsearch_exploration_reports· Use when the user asks what exploration reports, geological survey publications or research papers say about a topic, place, company or mineral. Read-only full-text search of public documents, one corpus at a time; it changes nothing. Returdocument_files· Use when the user wants to open or download a public document found with search_exploration_reports. Read-only: give the hit's corpus and doc_key; returns the document's title and series and temporary download links to its files (it changeswamex_report_files· Use when the user wants the files of a WAMEX exploration report. Give an anumber (from inspect_point's reports, the wamex tables, or wamex_meta_* joins); returns mirror_files — the report's original PDF, appendix zips and an OCR'd copy, eac
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Re-tested about every 3 days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://geomate.nlp-tlp.org/mcp | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Website | https://geo.nlp-tlp.org/docs#agents | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Version | 1.1.0 | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 2h ago |
Change history
- NEW21 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is AgenticGeoMate still online?
Free alerts · no account▲ 0Do you run AgenticGeoMate? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about AgenticGeoMate
How do I connect AgenticGeoMate?
Use the hosted endpoint https://geomate.nlp-tlp.org/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does AgenticGeoMate offer?
When Electra Index connected on 21 Nov 2026, it listed 92 tools: list_datasets, describe_dataset, query_features, get_dataset_feature, search_dataset_documents, read_dataset_document, describe_raster, sample_raster and more. The full list is in "Live check" above.
Is AgenticGeoMate online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 3h ago.
What can I use AgenticGeoMate for?
Based on its description, it is most relevant to: query databases in plain language, build data pipelines.