Connect Accessible Ride Request Protocol to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Handle complex mobility transit logistics without the manual errors.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

How Vinkius works: one connection, every tool, in any AI
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Complete set · 4 capabilities

The complete Accessible Ride Request Protocol capability set.

These are the exact actions your AI can choose when you ask it to work with Accessible Ride Request Protocol.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Accessible Ride Request Protocol.

  1. 01

    Build handoff checklist

    This capability creates a custom checklist for users or caregivers. It ensures a smooth transition during the pickup process.

  2. 02

    Validate equipment fit

    This capability checks if specific mobility equipment will physically fit inside a designated vehicle type.

  3. 03

    Generate ride request

    This capability produces a full suite of ride documentation. It validates all user inputs against specific provider rules first.

  4. 04

    Verify contingency chain

    This capability audits your emergency contact sequence. It makes sure the fallback list is logical and contains all necessary escalation data.

One connector, every AI

Accessible Ride Request Protocol works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Accessible Ride Request Protocol to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1056ms average. Fast in production.

Accessible Ride Request Protocol is checked daily against the live service.

Daily averagePeak 1105ms
Sep 24Today
Fastest day
991ms
Slowest day
1105ms
14-day trend
Stable-4%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Accessible Ride Request Protocol, so you can see the experience inside your AI.

It does not authenticate your account with Accessible Ride Request Protocol. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Accessible Ride Request Protocol Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_3dszoLNH992kw7cxvYfeG340UkRDD0s6Y8IYBcH9/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Accessible Ride Request Protocol capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "accessible-ride-request-protocol-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_3dszoLNH992kw7cxvYfeG340UkRDD0s6Y8IYBcH9/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? How to give Claude access to Accessible Ride Request Protocol

See all the AI clients this connector works with ↑

Who it's for

Built for the work Accessible Ride Request Protocol owners hand off.

This MCP is designed for professionals managing specialized transit and mobility services.

  • 01

    Transit Coordinators

    They hand off equipment specs and destination data to generate ride requests.

  • 02

    Care Managers

    They use the capability to build handoff checklists for caregivers and clients.

  • 03

    Logistics Dispatchers

    They use it to validate vehicle compatibility for mobility devices.

FAQ

Questions Accessible Ride Request Protocol owners ask.

  • 01

    How does this MCP ensure a wheelchair will fit in a vehicle?

    The validate_equipment_fit capability compares the specific dimensions of the mobility equipment against the known constraints of the vehicle type.

  • 02

    Can I use this with Claude or Cursor?

    Yes, you can connect this MCP to any MCP-compatible client like Claude, Cursor, or Windsurf through Vinkius.

  • 03

    What kind of documentation does it produce?

    The generate_ride_request capability produces a full suite of ride documentation that has been validated against provider rules.

  • 04

    Does it help with emergency planning?

    Yes, the verify_contingency_chain capability checks that your fallback contact sequences are logical and contain all necessary data.

  • 05

    How do caregivers use this capability?

    Caregivers can use the build_handoff_checklist capability to get a customized list of steps for a smooth pickup.

  • 06

    How does the capability ensure equipment will fit in the vehicle?

    The validate_equipment_fit capability compares the physical dimensions and weight of the mobility aid against the specific interior clearances and ramp capacities of the vehicle.

  • 07

    What is included in the ride request package?

    The generate_ride_request capability produces a request brief for the driver, confirmation questions for the user, a handoff checklist, and a fallback contact sequence.

  • 08

    Can I customize the pickup instructions?

    Yes, the build_handoff_checklist capability creates a personalized sequence of actions based on your specific transfer preferences and communication needs.

Connect Accessible Ride Request Protocol to Claude, Cursor, ChatGPT & more