GeoArm Taxi — Tbilisi ⇄ Yerevan rides
REMOTE · GEOARMTAXI.COM
Book shared or private rides between Tbilisi and Yerevan: live prices, schedule, booking requests.
Available components
Last scanned (2 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1158 tokens (~289/item across 4 items; 4 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
- 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 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.
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 5 Nov 2026 · Probed https://geoarmtaxi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=geoarmtaxi.com | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a42330d7b7f1104c135173178aa03822 |
| SANs: geoarmtaxi.com | ||||||
| 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 geoarmtaxi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| geoarmtaxi.com. | absent | 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://geoarmtaxi.com/mcp | Verified | 200 | |
| http (plaintext) | http://geoarmtaxi.com/mcp | HTTPS enforced | 301 | https://geoarmtaxi.com/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 →
create_booking Request a booking ~574
Sends a booking request for a ride between Tbilisi and Yerevan (a seat, or a whole vehicle) for the passenger. A booking is a request: it is NOT confirmed until a GeoArm Taxi dispatcher contacts the passenger to confirm it. Use the values from get_prices_and_schedule (point, time, car, currency), the passenger's real name and phone, and get the passenger's yes to the price first. Payment is in cash to the driver. Returns the booking number, what was booked, the total, and a status_token for get_booking_status.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Required with `point: "@addr"` unless `lat`/`lng` are given |
| agent | string | – | If an AI agent makes the booking: its name (e.g. `ChatGPT`, `Claude`). Shown to the dispatcher. When you leave it out, your MCP client's name is used. |
| car | string | yes | `sprinter` = a seat on the scheduled minibus (the default choice) |
| currency | string | yes | One of `currencies` from /api/config; the price is taken from the server |
| date | string | yes | YYYY-MM-DD, today or later (Tbilisi date), at most a year ahead |
| dir | string | yes | `tbs-evn` = Tbilisi → Yerevan, `evn-tbs` = Yerevan → Tbilisi |
| lang | string | – | The language we should use with the passenger (an unknown value is treated as `en`) |
| lat | number|null | – | – |
| lng | number|null | – | – |
| name | string | yes | The passenger's name |
| notes | string | – | Flight number, luggage, a child seat request and the like (longer text is cut to 1000 characters) |
| pax | integer | yes | Passengers; at most `types[car].max` |
| phone | string | yes | The passenger's phone in international format, e.g. +995 5xx xx xx xx |
| point | string | yes | A departure point id from `points[dir]` in /api/config, or `@addr` for pick-up from an address (extra fee, confirmed by the dispatcher) |
| time | string | yes | One of `schedule[dir]` from /api/config, or `other` for a time outside the timetable (whole vehicle; the dispatcher sets the price) |
| whole | boolean | – | `true` = the whole vehicle for this party at a timetable time: the total is `types[car].whole[currency]` from /api/config (not per passenger). Only when that price exists for the chosen currency; `pa… |
| Name | Type | Req | Description |
|---|---|---|---|
| booking | object | – | What was booked, as the server understood it |
| confirmed | boolean | – | Always false here: a dispatcher confirms later |
| feedback | string | – | Optional, after you finish: where you may tell us in a few lines how this went (POST, see /api/agent-feedback). Never include the passenger's personal data. |
| message | string | – | A sentence for the passenger, in `lang` |
| number | integer | – | The booking number |
| status | string | – | – |
| status_token | string | – | – |
| status_url | string | – | – |
| telegram | string | – | A link the passenger can open to get the confirmation in Telegram |
No examples provided.
get_booking_status Booking status ~60
The state of a booking request made with create_booking: received (not confirmed yet), confirmed, completed or cancelled. Needs the status_token create_booking returned. No personal data is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| status_token | string | yes | The status_token from create_booking |
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | – |
| date | string | – | – |
| dir | string | – | – |
| number | integer | – | – |
| pax | integer | – | – |
| status | string | – | – |
| time | string | – | – |
No examples provided.
get_prices_and_schedule Prices, departure points and times ~147
The live GeoArm Taxi offer for rides between Tbilisi (Georgia) and Yerevan (Armenia): currencies; per car type (sprinter = a seat on the scheduled minibus, minivan, sedan) the seats, the price per passenger and the whole-vehicle price when there is one; the departure points (ids and English names) and departure times per direction; and the key facts. Read it before create_booking.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Only this direction: `tbs-evn` = Tbilisi → Yerevan, `evn-tbs` = Yerevan → Tbilisi. Leave it out for both. |
| Name | Type | Req | Description |
|---|---|---|---|
| address_pickup | boolean | yes | – |
| cars | array | yes | – |
| currencies | array | yes | – |
| directions | array | yes | – |
| facts | string | yes | – |
No examples provided.
leave_feedback Tell us how it went (optional) ~265
Optional, and only if your user and your own rules allow it: after you have read this site or booked a ride, tell GeoArm Taxi in a few lines what worked, what was missing and whether you would recommend it. Do not include any personal data of the person you act for: e-mail addresses, phone numbers and @handles are removed. Every note is read by a person; nothing you write is published or executed. At most 5 notes per address per day.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Your name, for example ChatGPT or Claude |
| booking | integer | – | Optional: the booking number, if you made one |
| missing | string | – | What was missing, unclear or wrong, and what would have helped |
| model | string | – | Optional: the model or version, if you know it |
| reason | string | – | Why |
| task | string | – | Optional: what your user asked for, in general words (for example: compare ways to get from Tbilisi to Yerevan). No names, phones or other personal data |
| worked | string | – | What was easy or clear on this site |
| would_recommend | string | yes | Would you recommend this service to a person who asked you for this trip? |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | A short thank-you |
| ok | boolean | – | – |
No examples provided.
How do I install the GeoArm Taxi — Tbilisi ⇄ Yerevan rides MCP server?
GeoArm Taxi — Tbilisi ⇄ Yerevan rides is a hosted endpoint at https://geoarmtaxi.com/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 · geoarmtaxi.com
claude mcp add --transport http com-geoarmtaxi-booking 'https://geoarmtaxi.com/mcp'
What is the GeoArm Taxi — Tbilisi ⇄ Yerevan rides MCP server?
GeoArm Taxi — Tbilisi ⇄ Yerevan rides is an MCP server listed in the public MCP registry as com.geoarmtaxi/booking. Book shared or private rides between Tbilisi and Yerevan: live prices, schedule, booking requests. This page covers its hosted endpoint (https://geoarmtaxi.com/mcp).
Is the GeoArm Taxi — Tbilisi ⇄ Yerevan rides MCP server safe to use?
GeoArm Taxi — Tbilisi ⇄ Yerevan rides scores 82 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 GeoArm Taxi — Tbilisi ⇄ Yerevan rides MCP server expose?
GeoArm Taxi — Tbilisi ⇄ Yerevan rides exposes 4 tools: get_prices_and_schedule, create_booking, get_booking_status, leave_feedback. Their descriptions and schemas cost roughly 1,046 tokens of context every time the server is loaded.
Does the GeoArm Taxi — Tbilisi ⇄ Yerevan rides MCP server require authentication?
No. We connected to GeoArm Taxi — Tbilisi ⇄ Yerevan rides without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GeoArm Taxi — Tbilisi ⇄ Yerevan rides MCP server still maintained?
GeoArm Taxi — Tbilisi ⇄ Yerevan rides is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.