Georgia MCP
REMOTE · GEO-MCP.ABGEO.CLOUD · 2 COMPONENTS
An MCP server for Georgian public data, read from the organizations that publish it.
Available components
Last scanned (22 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8682 tokens (~201/item across 43 items; 43 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 43 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 −2
- HSTS header: pass → fail ▼ security
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
- Tool “offers_search_offers” rewrote its description, which is the text the model reads security
- Server version: v1.2.1 → v1.3.0 functional
- New tool “energy_get_grid” functional
- New tool “energy_list_prices” functional
- New tool “energy_get_balance” functional
- 15 Nov 26 +1
- Schema quality: 5321 → 8119 ▼ functional
- Server version: v1.1.2 → v1.2.1 functional
- New tool “parliament_get_vote” functional
- New tool “parliament_list_votes” functional
- New tool “parliament_search_questions” functional
- New tool “permits_get_application” functional
- New tool “permits_search_applications” functional
- New tool “parliament_search_bills” functional
- New tool “holidays_get_day” functional
- New tool “holidays_list_holidays” functional
- New tool “law_get_act” functional
- New tool “law_search_acts” functional
- New tool “parcels_get_parcel” functional
- New tool “parcels_list_nearby_parcels” functional
- New tool “parcels_search_addresses” functional
- New tool “parliament_get_bill” functional
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: v1.1.1 → v1.1.2 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://geo-mcp.abgeo.cloud/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=abgeo.cloud | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 50b3735dd3d89c1413662863e39fecd8 |
| SANs: abgeo.cloud, *.abgeo.cloud | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of geo-mcp.abgeo.cloud. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| cloud. | DS published | 7041 | 13 | Verified |
| abgeo.cloud. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://geo-mcp.abgeo.cloud/mcp | Verified | 200 | |
| http (plaintext) | http://geo-mcp.abgeo.cloud/mcp | HTTPS enforced | 301 | https://geo-mcp.abgeo.cloud/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
transit_get_timetable Timetable of a route at a stop ~192
Returns the planned departure times of one direction of a route of the TTC at one stop, on a date of the current week. A time of 24:00 or later is after midnight, on the next date.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The date, YYYY-MM-DD, in the current week. The default is today in Tbilisi. |
| direction | null|integer | – | The direction number from transit_get_route. Required when the route has two directions. |
| kind | string | – | The kind, when two routes share the number: bus, minibus, metro, or cable_car. |
| language | string | – | The language of the names: ka or en. The default is en. |
| route | string | yes | The route number (385) or the route id. |
| stop | string | yes | The stop id or the stop code. The stop must be on the direction. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | The instant at which the server read the timetable, RFC 3339. |
| date | string | yes | The date of the times, YYYY-MM-DD. |
| direction | integer | yes | The direction number. |
| headsign | string | yes | The destination of the direction. |
| route | object | yes | The route. |
| source | string | yes | The source of the data: TTC. |
| stale | boolean | yes | True when the TTC did not answer and the server returns a timetable it read before. |
| stop | object | yes | The stop. |
| times | null|array | yes | The planned departure times, HH:MM, in order. 24:00 or later is after midnight. |
No examples provided.
transit_list_arrivals Next arrivals at a stop in Tbilisi ~166
Lists the next vehicles of the TTC at a stop: route number, kind, headsign, minutes from as_of, and the expected instant. live is true when the TTC tracks the vehicle; else the time comes from the timetable. With a route, lists the next vehicles of that route only.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | The language of the names: ka or en. The default is en. |
| limit | integer | – | The maximum count of arrivals, 1 to 30. The default is 10. |
| route | string | – | Only this route: its number (385) or its id. Empty gives the next vehicle of each route. |
| stop | string | yes | The stop id (1:1000) or the stop code (1000). |
| Name | Type | Req | Description |
|---|---|---|---|
| arrivals | null|array | yes | The next arrivals, soonest first. |
| as_of | string | yes | The instant at which the server read the arrivals, RFC 3339. minutes count from it. |
| note | string | – | Why the list is empty. |
| source | string | yes | The source of the data: TTC. |
| stop | object | yes | The stop. |
No examples provided.
transit_list_nearby_stops Stops near a point in Tbilisi ~179
Lists the stops of the TTC within a distance of a point in Tbilisi, nearest first, with the distance in metres. Use transit_search_places to get the coordinates of a place.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Only stops of this kind: bus, metro, or cable_car. Empty gives every kind. |
| language | string | – | The language of the names: ka or en. The default is en. |
| lat | number | yes | The latitude of the point, in degrees. |
| limit | integer | – | The maximum count of stops, 1 to 50. The default is 10. |
| lon | number | yes | The longitude of the point, in degrees. |
| radius_m | integer | – | The distance from the point in metres, 1 to 2000. The default is 500. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | The instant at which the server read the stops, RFC 3339. |
| source | string | yes | The source of the data: TTC. |
| stale | boolean | yes | True when the TTC did not answer and the server returns stops it read before. |
| stops | null|array | yes | The stops within the distance, nearest first. |
No examples provided.
transit_plan_trip Plan a trip by public transport in Tbilisi ~253
Plans a trip by public transport of the TTC in Tbilisi between two points, given as coordinates. Returns up to 3 itineraries with each leg: walk or ride, route, stops, instants, distance in metres. Use transit_search_places to get coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The date of depart_at or arrive_by, YYYY-MM-DD. The default is today in Tbilisi. |
| from | object | yes | The start point in Tbilisi. |
| kinds | null|array | – | The kinds to ride: bus, minibus, metro, cable_car. bus and minibus go together. Empty gives every kind. A walk is always allowed. |
| language | string | – | The language of the names: ka or en. The default is en. |
| preference | string | – | fastest, less_walking, or fewer_transfers. The default is fastest. |
| time | string | – | The time of depart_at or arrive_by, HH:MM in Tbilisi. Required with them. |
| timing | string | – | leave_now, depart_at, or arrive_by. The default is leave_now. |
| to | object | yes | The end point in Tbilisi. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | The instant at which the server read the plan, RFC 3339. |
| itineraries | null|array | yes | Up to 3 ways to travel, in the order of the TTC. |
| note | string | – | Why the list is empty. |
| source | string | yes | The source of the data: TTC. |
No examples provided.
transit_search_places Search places in Tbilisi ~116
Finds places in Tbilisi (addresses, streets, buildings) by text, with their coordinates, for transit_plan_trip and transit_list_nearby_stops. Data from OpenStreetMap through the TTC.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | The language of the names: ka or en. The default is en. |
| limit | integer | – | The maximum count of places, 1 to 20. The default is 5. |
| query | string | yes | An address, a street, or a building in Tbilisi. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | The instant at which the server read the places, RFC 3339. |
| note | string | – | Why the list is empty. |
| places | null|array | yes | The matching places, in the order of the TTC. |
| source | string | yes | The source of the data: TTC, from OpenStreetMap. |
| stale | boolean | yes | True when the TTC did not answer and the server returns places it read before. |
No examples provided.
transit_search_routes Search the routes of Tbilisi ~132
Finds the routes of the TTC by number or by name. Kinds: bus, minibus, metro, cable_car. With no query, lists every route.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Only routes of this kind: bus, minibus, metro, or cable_car. |
| language | string | – | The language of the names: ka or en. The default is en. |
| limit | integer | – | The maximum count of routes, 1 to 100. The default is 20. |
| query | string | – | A route number or a part of a route name. Empty gives every route. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | The instant at which the server read the routes, RFC 3339. |
| routes | null|array | yes | The matching routes, best match first. |
| source | string | yes | The source of the data: TTC. |
| stale | boolean | yes | True when the TTC did not answer and the server returns routes it read before. |
No examples provided.
transit_search_stops Search the stops of Tbilisi ~149
Finds the stops of the Tbilisi Transport Company (bus stops, metro stations, cable car stations) by name or stop code, in Georgian or English. Use the stop id of the result with transit_list_arrivals or transit_get_timetable.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Only stops of this kind: bus, metro, or cable_car. Empty gives every kind. |
| language | string | – | The language of the names: ka or en. The default is en. |
| limit | integer | – | The maximum count of stops, 1 to 50. The default is 10. |
| query | string | yes | A stop name or a stop code, in Georgian or English. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | The instant at which the server read the stops, RFC 3339. |
| source | string | yes | The source of the data: TTC. |
| stale | boolean | yes | True when the TTC did not answer and the server returns stops it read before. |
| stops | null|array | yes | The matching stops, best match first. |
No examples provided.
How do I install the Georgia MCP server?
Georgia MCP is a hosted endpoint at https://geo-mcp.abgeo.cloud/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · geo-mcp.abgeo.cloud
claude mcp add --transport http abgeo-georgia-mcp 'https://geo-mcp.abgeo.cloud/mcp'
What is the Georgia MCP server?
Georgia MCP is listed in the public MCP registry as io.github.ABGEO/georgia-mcp. An MCP server for Georgian public data, read from the organizations that publish it. This page covers its hosted endpoint (https://geo-mcp.abgeo.cloud/mcp).
Is the Georgia MCP server safe to use?
Georgia MCP scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Georgia MCP server expose?
Georgia MCP exposes 43 tools: air_get_quality, air_list_history, cinema_get_seat_map, cinema_list_cinemas, cinema_list_movies, and 38 more. Their descriptions and schemas cost roughly 8,682 tokens of context every time the server is loaded.
Does the Georgia MCP server require authentication?
No. We connected to Georgia MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Georgia MCP server still maintained?
Georgia MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Georgia MCP server?
VerifyMCP ran 13 checks on Georgia MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.