# Accessible Transport Disruption Plan AI Agent Connect

> Accessible Transport Disruption Plan MCP handles contingency management for users with mobility requirements. When transport providers fail or delay, your AI client uses this MCP to trigger response protocols, check provider status, and validate that fallback routes meet strict accessibility standards.

## Overview
- **Category:** transportation
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_czoCohHkVyTEfkYBHD4GyzCNA8mrSideMgpRVVGC/ai-agent-connect
- **Tags:** mobility, contingency, transport, accessibility, disruption

## Description

When transport networks fail, users with mobility needs face much higher risks than the general public. This MCP gives your AI agent the logic needed to manage these disruptions in real time. Instead of manual troubleshooting, your agent can instantly check if a provider is running late, verify if a new route is actually wheelchair accessible, and execute a pre-planned fallback sequence. You can use it to build reliable, automated safety nets for recurring journeys. It moves beyond simple navigation by focusing on the specific constraints of accessibility, ensuring that a delay doesn't turn into a stranded passenger situation. Your agent handles the heavy lifting of checking provider availability and validating that every contingency plan stays compliant with mobility requirements.

## Tools

### get_disruption_plan
Generates a complete contingency response for a specific journey when a disruption occurs.

### get_provider_status
Checks the current availability or delay status of a specific transport provider.

### simulate_fallback_sequence
Tests a user's fallback rules against a hypothetical disruption to ensure the plan is viable.

### validate_journey_parameters
Ensures a new recurring journey configuration is logically sound and meets accessibility requirements.

## Prompt Examples

**Prompt:** 
```
My primary transport provider is delayed by 20 minutes. What is the contingency plan?
```

**Response:** 
```
The disruption trigger has been activated. The system will notify your primary contact via SMS and then attempt to book your secondary provider, Provider B.
```

**Prompt:** 
```
Check if my current transport provider is available for my 10:00 AM trip.
```

**Response:** 
```
Provider Alpha is currently available and is running on schedule for your 10:00 AM trip.
```

**Prompt:** 
```
Is my new journey configuration valid for someone using a wheelchair?
```

**Response:** 
```
The journey configuration is valid. All selected pickup points are marked as accessible and the fallback providers are correctly prioritized.
```

## Capabilities

### Contingency Generation
Your agent creates specific response protocols when a transport failure is detected.

### Real-time Status Monitoring
The AI checks for delays or availability issues with specific transport providers.

### Accessibility Validation
Your agent verifies that new journey configurations meet necessary mobility requirements.

### Fallback Testing
The AI simulates disruptions to confirm that fallback rules actually work before a real event occurs.

## Use Cases

### Emergency Transport Switching
When a primary vehicle is delayed, the agent automatically triggers a secondary provider.

### Route Compliance Auditing
The AI checks if a proposed recurring route meets specific wheelchair accessibility needs.

### Proactive Plan Testing
Operators simulate transport failures to ensure their fallback rules are actually functional.

### Real-time Delay Monitoring
The agent monitors provider status to anticipate disruptions before they impact the user.

## Benefits

- Automates the transition from primary to secondary transport providers.
- Reduces manual verification of accessibility compliance for new routes.
- Validates fallback plans through simulation before disruptions happen.
- Provides instant status updates on transport provider delays.

## How It Works

Connect the MCP to your AI client to start managing transport contingencies.

1. Connect your preferred MCP-compatible client to Vinkius.
2. Grant the agent access to the Accessible Transport Disruption Plan MCP.
3. The agent uses the tools to monitor providers or validate routes.
4. The agent executes contingency plans or notifies contacts when disruptions occur.

## Frequently Asked Questions

**What does this MCP do?**
It provides tools for managing transport disruptions specifically for users with mobility needs. It handles contingency planning, provider status checks, and accessibility validation.

**How do I use this with my AI agent?**
You connect your AI client, such as Claude or Cursor, to the Vinkius platform. Once connected, your agent can immediately call the tools provided by this MCP.

**Can I test my contingency plans before they are needed?**
Yes. You can use the simulate_fallback_sequence tool to test your fallback rules against hypothetical disruptions to ensure they work.

**Does it check for wheelchair accessibility?**
Yes. The validate_journey_parameters tool is specifically designed to ensure journey configurations meet accessibility requirements.

**Which clients are compatible?**
This MCP works with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

**How does the system handle a provider delay?**
The system uses `get_disruption_plan` to evaluate if a delay exceeds the user's maximum acceptable limit and then triggers the pre-defined fallback rules.

**Can I test my fallback rules before a real disruption occurs?**
Yes, you can use the `simulate_fallback_sequence` tool to run hypothetical failure scenarios and verify that the replacement actions are viable.

**How are accessibility requirements enforced?**
The `validate_journey_parameters` tool ensures that all pickup points are explicitly marked as accessible and that the journey configuration is logically sound.