A powerful MCP server built with NitroStack
Add via Cursor Settings UI (Settings > Features > MCP > Add New MCP Server):
{
"mcpServers": {
// your other mcp servers
"riva": {
"url": "https://riva-6a654a65-robotic-raccoons-amrita-university-coimbatore.app.nitrocloud.ai/mcp"
}
}
}
Connect remote tools directly via Claude's Web UI:
Configure custom tools directly via ChatGPT's Web UI:
Add the following configuration block under mcpServers in your Antigravity configuration file (~/.gemini/config/mcp_config.json):
{
"mcpServers": {
// your other mcp servers
"riva": {
"serverUrl": "https://riva-6a654a65-robotic-raccoons-amrita-university-coimbatore.app.nitrocloud.ai/mcp"
}
}
}
Add the following configuration block to your Codex configuration file (~/.codex/config.toml):
[mcp_servers.riva] url = "https://riva-6a654a65-robotic-raccoons-amrita-university-coimbatore.app.nitrocloud.ai/mcp"
Connect directly using the Server-Sent Events endpoint:
https://riva-6a654a65-robotic-raccoons-amrita-university-coimbatore.app.nitrocloud.ai/mcp
Find and compare ride options from Uber, Ola, and Rapido between an origin and destination, with an intelligent recommendation.
Modify constraints on a previous find_rides search — e.g. "find cheaper options" or "show faster rides" — and re-rank/re-filter accordingly.
Recommend the single best ride from a previous search according to a chosen strategy: cheapest, fastest, instant pickup, or best overall value.
Store rider preferences (female driver preference, budget limit, luggage constraints, vehicle exclusions) applied to future ride searches.
Get a detailed explanation of one specific ride option from a previous search.
Show simulated nearby Uber, Ola, and Rapido drivers around a pickup location.
Estimate the fare for a future return trip at a given time of day, e.g. "What will my return fare be at 9 PM?"
Analyze whether a driver should accept an offered ride: gross/net earnings, fuel cost, platform commission, cost per km, hourly earning, destination demand, and an ACCEPT/CONSIDER/REJECT recommendation.
Estimate ride demand around a destination: demand level, expected ride availability, expected waiting time, and return-trip probability. Uses simulated demand data.
Recommend where a driver should move next based on simulated demand, time of day, and historical patterns.
Summarize a driver's earnings for a session or day: total earnings, expenses, net profit, average earning per hour/trip/km, and recommendations.
Show simulated incoming ride requests near the driver's current location, ranked by estimated net earning.
Switch the conversation between Rider Mode and Driver Mode. This should normally be the FIRST tool called in a new conversation — ask the user "Customer or Driver?" before calling it, unless their first message already makes this obvious. Rider Mode surfaces ride discovery/comparison/travel-planning tools; Driver Mode surfaces trip-acceptance, demand, and earnings tools.
Plan a complete journey around a deadline (e.g. a flight or train): recommends when to leave, accounting for traffic and a safety buffer, and picks the best ride.
Estimate the fare, demand multiplier, and availability for a ride at a future time, e.g. "I need a ride tomorrow at 7 AM."
Plan a trip with one or more intermediate stops, e.g. "campus to airport, stopping at Gandhipuram" — totals distance, time, and fare.
Simulate matching with a nearby rider on a similar route and recommend whether to pool, e.g. "Can I share this ride?"
SIMULATED emergency SOS — shares the rider's current location and (if provided) active trip details with simulated emergency contacts. Does NOT contact real emergency services; direct the user to call their local emergency number for real danger.
Simulates the ride booking lifecycle (Searching → Driver Assigned → Driver Arriving → Trip Started → Completed). Requires searchId + optionId + confirmed:true to actually create a booking — otherwise returns a confirmation preview only. Call again with the returned bookingId to advance the lifecycle.