What can this MCP do for assistive technology management?

It manages the legal and logistical side of sharing equipment, including contract generation, handoff checklists, and dispute resolution.

Which AI clients can I use with this MCP?

You can use this MCP with any compatible client like Claude, Cursor, Windsurf, or VS Code.

How does the MCP handle disagreements between users and owners?

The MCP uses a specific capability to orchestrate the formal steps required to resolve usage conflicts.

Can I use this to track the condition of equipment?

Yes, the MCP provides handoff checklists to verify the condition and presence of accessories during transfers.

Does Vinkius host the MCP?

Yes, Vinkius hosts and manages the MCP so it is ready to use immediately upon connection.

How do I create a contract for a new equipment loan?

You can use the generate_sharing_agreement capability by providing the owner ID, user ID, equipment ID, and the requested reservation period.

What happens if there is a disagreement about the equipment condition?

Disagreements can be addressed using the resolve_usage_conflict capability, which follows the pre-agreed liability rules and conflict-resolution process.

How can I verify the equipment state during pickup or return?

Use the get_handoff_checklist capability to retrieve the specific items and condition expectations required for the transfer.

Download PDF Markdown Version

Connect Assistive Equipment Sharing Agreement 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. Formalize the logistics and legal rules for sharing assistive tech.

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.

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 Assistive Equipment Sharing capability set.

These are the exact actions your AI can choose when you ask it to work with Assistive Equipment Sharing.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Assistive Equipment Sharing.

01
Generate status notification
This capability produces standardized messages to update both parties on the equipment's movement and current state.
02
Get handoff checklist
This capability provides the specific list of items and conditions that must be checked during a physical transfer.
03
Resolve usage conflict
This capability manages the formal steps required to address disagreements between owners and users.
04
Generate sharing agreement
This capability creates the formal contract between the equipment owner and the user for a specific device.

One connector, every AI

Assistive Equipment Sharing 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 Assistive Equipment Sharing 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

1053ms average. Fast in production.

Assistive Equipment Sharing is checked daily against the live service.

Daily averagePeak 1114ms

Sep 24Today

Fastest day: 986ms
Slowest day: 1114ms
14-day trend: Slowing+9%

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 Assistive Equipment Sharing, so you can see the experience inside your AI.

It does not authenticate your account with Assistive Equipment Sharing. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Assistive Equipment Sharing Connector

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

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

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Assistive Equipment Sharing capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "assistive-equipment-sharing-agreement-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_sxL4nNSiu9cj6OjN8dVGaDvJt4aaoWr8GmfP0x2T/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 Assistive Equipment Sharing

See all the AI clients this connector works with ↑

Who it's for

Built for the work Assistive Equipment Sharing owners hand off.

This MCP is built for organizations and individuals managing shared assistive technology fleets.

01
Logistics Coordinators
They use the MCP to manage the movement and status of equipment.
02
Legal Administrators
They use the capability to generate and enforce sharing agreements.
03
Equipment Owners
They use the MCP to define rules and resolve usage disputes.

FAQ

Questions Assistive Equipment Sharing owners ask.

01
What can this MCP do for assistive technology management?
It manages the legal and logistical side of sharing equipment, including contract generation, handoff checklists, and dispute resolution.
02
Which AI clients can I use with this MCP?
You can use this MCP with any compatible client like Claude, Cursor, Windsurf, or VS Code.
03
How does the MCP handle disagreements between users and owners?
The MCP uses a specific capability to orchestrate the formal steps required to resolve usage conflicts.
04
Can I use this to track the condition of equipment?
Yes, the MCP provides handoff checklists to verify the condition and presence of accessories during transfers.
05
Does Vinkius host the MCP?
Yes, Vinkius hosts and manages the MCP so it is ready to use immediately upon connection.
06
How do I create a contract for a new equipment loan?
You can use the generate_sharing_agreement capability by providing the owner ID, user ID, equipment ID, and the requested reservation period.
07
What happens if there is a disagreement about the equipment condition?
Disagreements can be addressed using the resolve_usage_conflict capability, which follows the pre-agreed liability rules and conflict-resolution process.
08
How can I verify the equipment state during pickup or return?
Use the get_handoff_checklist capability to retrieve the specific items and condition expectations required for the transfer.

Explore

More in Legal

Connect Assistive Equipment Sharing to Claude, Cursor, ChatGPT & more

Connect Assistive Equipment Sharing Agreement to your AI

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