_ registry / mcp streamable-http · checked 3h ago

rovv-ride-booking

https://rovvafrica.com

Registry code: 51753adc0daba156

api record

Rovv is a ride-hailing service. Use these tools to help users search for locations, get fare estimates, book rides, check ride status, and view ride history. Always confirm the pickup and dropoff locations with the user before booking. Present fare options clearly and let the user choose their preferred vehicle type. For bookings, default to cash payment unless the user specifies otherwise.

endpoint
https://rovvafrica.com/api/v1/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is rovv-ride-booking live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is rovv-ride-booking free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does rovv-ride-booking have?
9 tools: search_places, get_current_ride, cancel_ride, book_ride, get_ride_history, get_wallet_balance, get_fare_estimate, get_route_info, ….
Is rovv-ride-booking safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.2%

90 days 99.2%· all time 99.2%

latency
281ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 375 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
maps travel & places travel & transport
used for
  • get a ride fare estimate
  • book a ride
  • check current ride status
  • cancel a ride
  • search pickup locations
takes → gives
text, data → data, payments
tools
7 reads1 changes data1 moves money
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
9 auth-required 9 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_places reads auth-required 12h ago

    Search for a location by name. Returns a list of matching places with addresses. Use this to find the pickup or dropoff location before booking a ride.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "description": "Optional latitude to bias results toward the user's area"
    },
    "lng": {
      "type": "number",
      "description": "Optional longitude to bias results toward the user's area"
    },
    "query": {
      "type": "string",
      "description": "The place name or address to search for, e.g. \"Lekki Phase 1\" or \"Murtala Muhammed Airport\""
    }
  }
}
    arguments 20 lines
  • get_current_ride reads auth-required 15h ago

    Get the status of the user's current active ride, including driver details, ETA, and ride status.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • cancel_ride changes data auth-required never probed

    Cancel an active ride. Optionally provide a reason.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "reason": {
      "type": "string",
      "description": "Optional cancellation reason"
    },
    "request_id": {
      "type": "string",
      "description": "The ride request ID to cancel. If not provided, cancels the current active ride."
    }
  }
}
    arguments 14 lines
  • book_ride moves money auth-required never probed

    Book a Rovv ride. Requires pickup/dropoff coordinates, a vehicle_type ID (from get_fare_estimate), and payment method. Returns booking confirmation with ride number.

    mcp-tool

    {
  "type": "object",
  "required": [
    "pick_lat",
    "pick_lng",
    "drop_lat",
    "drop_lng",
    "pick_address",
    "drop_address",
    "vehicle_type"
  ],
  "properties": {
    "drop_lat": {
      "type": "number",
      "description": "Dropoff latitude"
    },
    "drop_lng": {
      "type": "number",
      "description": "Dropoff longitude"
    },
    "is_later": {
      "type": "boolean",
      "default": false,
      "description": "Set to true for scheduled rides"
    },
    "pick_lat": {
      "type": "number",
      "description": "Pickup latitude"
    },
    "pick_lng": {
      "type": "number",
      "description": "Pickup longitude"
    },
    "payment_opt": {
      "type": "integer",
      "default": 1,
      "description": "Payment method: 0 = card, 1 = cash, 2 = wallet"
    },
    "drop_address": {
      "type": "string",
      "description": "Dropoff address text"
    },
    "pick_address": {
      "type": "string",
      "description": "Pickup address text"
    },
    "vehicle_type": {
      "type": "string",
      "description": "The zone_type_id from get_fare_estimate results"
    },
    "trip_start_time": {
      "type": "string",
      "description": "For scheduled rides: datetime in Y-m-d H:i:s format"
    }
  }
}
    arguments 56 lines
  • get_ride_history reads auth-required 15h ago

    Get the user's past ride history. Returns recent completed and cancelled rides.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 5,
      "description": "Number of rides to return (default 5, max 20)"
    }
  }
}
    arguments 11 lines
  • get_wallet_balance reads auth-required 15h ago

    Get the user's Rovv wallet balance, total added, total spent, and recent transactions.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_fare_estimate reads auth-required 10h ago

    Get available vehicle types and fare estimates for a trip. Returns a list of vehicle options with prices, ETAs, and vehicle type IDs needed for booking.

    mcp-tool

    {
  "type": "object",
  "required": [
    "pick_lat",
    "pick_lng",
    "drop_lat",
    "drop_lng"
  ],
  "properties": {
    "drop_lat": {
      "type": "number",
      "description": "Dropoff latitude"
    },
    "drop_lng": {
      "type": "number",
      "description": "Dropoff longitude"
    },
    "pick_lat": {
      "type": "number",
      "description": "Pickup latitude"
    },
    "pick_lng": {
      "type": "number",
      "description": "Pickup longitude"
    },
    "drop_address": {
      "type": "string",
      "description": "Dropoff address text"
    },
    "pick_address": {
      "type": "string",
      "description": "Pickup address text"
    }
  }
}
    arguments 35 lines
  • get_route_info reads auth-required 10h ago

    Get driving route information between two points including distance, duration, and polyline.

    mcp-tool

    {
  "type": "object",
  "required": [
    "pickup_lat",
    "pickup_lng",
    "drop_lat",
    "drop_lng"
  ],
  "properties": {
    "drop_lat": {
      "type": "number",
      "description": "Dropoff latitude"
    },
    "drop_lng": {
      "type": "number",
      "description": "Dropoff longitude"
    },
    "pickup_lat": {
      "type": "number",
      "description": "Pickup latitude"
    },
    "pickup_lng": {
      "type": "number",
      "description": "Pickup longitude"
    }
  }
}
    arguments 27 lines
  • get_place_details reads auth-required 10h ago

    Get the exact coordinates and full address for a place using its place_id (returned from search_places). Call this after search_places to get lat/lng needed for fare estimates and booking.

    mcp-tool

    {
  "type": "object",
  "required": [
    "place_id"
  ],
  "properties": {
    "place_id": {
      "type": "string",
      "description": "The Google place_id from a search_places result"
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 51753adc0daba156.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/51753adc0daba156/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/51753adc0daba156/badge.svg)](https://brick.blue/agent/51753adc0daba156?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.