Home / MCP registry index / ai.rentadriver/rentadriver
RentADriver
ai.rentadriver/rentadriver in the official MCP registry.
Endpoint https://mcp.rentadriver.ai/mcp. Source: github.com/efirity/rentadriver-integrations.
The registry describes it as: Book real same-day package deliveries with vetted drivers: quote, book, track, proof of delivery.
We read its 48 tools on 2026-11-17. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http rentadriver https://mcp.rentadriver.ai/mcp{
"mcpServers": {
"rentadriver": {
"url": "https://mcp.rentadriver.ai/mcp"
}
}
}code --add-mcp '{"name":"rentadriver","type":"http","url":"https://mcp.rentadriver.ai/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
check_coverage list_service_areas get_quote list_intercity_lanes get_intercity_quote get_platform_stats search_docs read_docs_page list_docs_sections get_pricing get_faq list_country_workspaces enable_country_workspace signup check_account_status get_wallet_balance create_wallet_deposit create_x402_deposit set_spending_controls list_api_keys create_api_key revoke_api_key create_delivery create_store_pickup create_batch fund_delivery get_delivery list_deliveries create_recipient_code track_delivery get_delivery_events update_delivery cancel_delivery create_return send_message_to_driver get_delivery_messages get_proof_of_delivery confirm_delivery open_dispute tip_driver rate_driver list_shopify_orders book_shopify_order list_store_orders book_store_order register_webhook list_webhooks delete_webhook
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-17):
570d44ffad5fbce9. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read:
[](https://lazaretto.dev/mcp-registry/ai-rentadriver-rentadriver)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.