Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bota — car rental availability and bookings

REMOTE · MCP.BOTA-CHAT.COM · SCANNED SEP 28

Real availability, prices and bookings of car rental companies (rent-a-car), by conversation.

+3 this week 67 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1487 tokens (~185/item across 8 items; 8 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 Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 72% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "chat" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Bota — car rental availability and bookings MCP server?

Bota — car rental availability and bookings is a hosted endpoint at https://mcp.bota-chat.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 · mcp.bota-chat.com

# add to Claude Code
claude mcp add --transport http com-bota-chat-bota 'https://mcp.bota-chat.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-bota-chat-bota": {
      "url": "https://mcp.bota-chat.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-bota-chat-bota": {
      "type": "http",
      "url": "https://mcp.bota-chat.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-bota-chat-bota]
url = "https://mcp.bota-chat.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-bota-chat-bota": {
      "type": "remote",
      "url": "https://mcp.bota-chat.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-bota-chat-bota --url 'https://mcp.bota-chat.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-bota-chat-bota:
    url: "https://mcp.bota-chat.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-bota-chat-bota": {
      "Transport": "http",
      "Url": "https://mcp.bota-chat.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-bota-chat-bota -t streamable-http -u 'https://mcp.bota-chat.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-bota-chat-bota": {
      "type": "http",
      "url": "https://mcp.bota-chat.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 28 Sept 2026 · Probed https://mcp.bota-chat.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.bota-chat.com CN=WR3,O=Google Trust Services,C=US 21 Aug 2026 19 Nov 2026 RSA 2048 SHA256-RSA 30efbec7fe2ad0f912c40cf00b2ad30a
SANs: *.bota-chat.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.bota-chat.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
bota-chat.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://mcp.bota-chat.com/mcp Verified 200
http (plaintext) http://mcp.bota-chat.com/mcp HTTPS enforced 301 https://mcp.bota-chat.com:443/mcp
MCP tools · 8 exposed · ~1,362 tokens

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 →

Tool Tokens
chat ~176

Send a free-text message to the company's Bota agent within a session (questions about conditions, insurance, extras, changes…). Bota answers in the customer's language with the company's approved information. For companies with booking_via_agents=true the conversation can complete a booking.

NameTypeReqDescription
company_idstringyesCompany id from list_rental_companies.
languagestring–Language of the conversation, BCP-47 (es, en, pt-BR, fr, de, it…). Defaults to 'en'. Bota also answers in the language the customer writes.
messagestringyes–
session_idstring–Session id returned by a previous call for this company. Omit on the first call; ALWAYS pass it back on the next ones so Bota keeps the conversation (offers, selection, customer details).

No output schema declared.

No examples provided.

confirm_booking ~188

Confirm the booking summarised by Bota. Pass the confirmation_token returned by the previous call (it proves the customer saw that exact summary). Creates the reservation in the company's reservation system and returns the confirmation code (and a payment link when the company requires prepayment).

NameTypeReqDescription
company_idstringyesCompany id from list_rental_companies.
confirmation_tokenstringyesconfirmation_token from the response that showed the booking summary.
languagestring–Language of the conversation, BCP-47 (es, en, pt-BR, fr, de, it…). Defaults to 'en'. Bota also answers in the language the customer writes.
session_idstringyesSession id returned by a previous call for this company. Omit on the first call; ALWAYS pass it back on the next ones so Bota keeps the conversation (offers, selection, customer details).

No output schema declared.

No examples provided.

list_offices ~105

Rental offices (pickup/return locations) of a company: name, city, address, opening hours, timezone, coordinates. Use the office NAME in search_availability.

NameTypeReqDescription
company_idstringyesCompany id from list_rental_companies.
languagestring–Language of the conversation, BCP-47 (es, en, pt-BR, fr, de, it…). Defaults to 'en'. Bota also answers in the language the customer writes.

No output schema declared.

No examples provided.

list_rental_companies ~58

List the car-rental companies that sell through Bota. Returns id, name, website, active channels, whether bookings can be completed from this server (booking_via_agents) and whether it is the demo company. Start here.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

provide_customer_details ~211

Submit the driver's details for the booking in progress. Only call it after the customer has explicitly accepted the company's terms (terms_accepted must be true). Bota then shows the summary to confirm.

NameTypeReqDescription
company_idstringyesCompany id from list_rental_companies.
emailstringyes–
first_namestringyes–
flight_numberstring––
languagestring–Language of the conversation, BCP-47 (es, en, pt-BR, fr, de, it…). Defaults to 'en'. Bota also answers in the language the customer writes.
last_namestringyes–
notesstring––
phonestring––
session_idstringyesSession id returned by a previous call for this company. Omit on the first call; ALWAYS pass it back on the next ones so Bota keeps the conversation (offers, selection, customer details).
terms_acceptedbooleanyes–

No output schema declared.

No examples provided.

search_availability ~287

Search available vehicles with real prices for a company, office and dates. Prices are identical to the company's own web chat (mandatory charges, one-way and time rules included). Returns numbered offers; keep the session_id to select one.

NameTypeReqDescription
company_idstringyesCompany id from list_rental_companies.
driver_ageinteger––
languagestring–Language of the conversation, BCP-47 (es, en, pt-BR, fr, de, it…). Defaults to 'en'. Bota also answers in the language the customer writes.
pickup_datestringyesYYYY-MM-DD, office-local.
pickup_officestringyesPickup office name (from list_offices) or id.
pickup_timestring–HH:MM, office-local. Default 10:00.
promo_codestring––
return_datestringyesYYYY-MM-DD, office-local.
return_officestring–Return office name or id when different (one-way).
return_timestring–HH:MM, office-local. Default 10:00.
session_idstring–Session id returned by a previous call for this company. Omit on the first call; ALWAYS pass it back on the next ones so Bota keeps the conversation (offers, selection, customer details).

No output schema declared.

No examples provided.

select_extras ~178

Add optional extras (child seat, additional driver, coverage…) to the booking in progress using the extra ids returned after select_offer, or pass an empty list to continue without extras. Requires booking_via_agents=true.

NameTypeReqDescription
company_idstringyesCompany id from list_rental_companies.
extrasarrayyesExtra ids to add; empty array = no extras.
languagestring–Language of the conversation, BCP-47 (es, en, pt-BR, fr, de, it…). Defaults to 'en'. Bota also answers in the language the customer writes.
session_idstringyesSession id returned by a previous call for this company. Omit on the first call; ALWAYS pass it back on the next ones so Bota keeps the conversation (offers, selection, customer details).

No output schema declared.

No examples provided.

select_offer ~159

Choose one of the numbered offers returned by search_availability (same session). Bota then asks for extras or driver details as needed. Requires booking_via_agents=true.

NameTypeReqDescription
company_idstringyesCompany id from list_rental_companies.
languagestring–Language of the conversation, BCP-47 (es, en, pt-BR, fr, de, it…). Defaults to 'en'. Bota also answers in the language the customer writes.
offer_numberintegeryes–
session_idstringyesSession id returned by a previous call for this company. Omit on the first call; ALWAYS pass it back on the next ones so Bota keeps the conversation (offers, selection, customer details).

No output schema declared.

No examples provided.

Common questions

What is the Bota — car rental availability and bookings MCP server?

Bota — car rental availability and bookings is an MCP server listed in the public MCP registry as com.bota-chat/bota. Real availability, prices and bookings of car rental companies (rent-a-car), by conversation. This page covers its hosted endpoint (https://mcp.bota-chat.com/mcp).

Is the Bota — car rental availability and bookings MCP server safe to use?

Bota — car rental availability and bookings scores 67 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 Bota — car rental availability and bookings MCP server expose?

Bota — car rental availability and bookings exposes 8 tools: list_rental_companies, list_offices, search_availability, chat, select_offer, and 3 more. Their descriptions and schemas cost roughly 1,362 tokens of context every time the server is loaded.

Does the Bota — car rental availability and bookings MCP server require authentication?

No. We connected to Bota — car rental availability and bookings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Bota — car rental availability and bookings MCP server still maintained?

Bota — car rental availability and bookings is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.