Connect Rider Benefit Matcher to ChatGPT, Claude and Gemini

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. Match policy rider clauses to specific loss events and expenses.

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 Rider Benefit Matcher capability set.

These are the exact actions your AI can choose when you ask it to work with Rider Benefit Matcher.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Rider Benefit Matcher.

  1. 01

    Analyze rider eligibility

    It determines which specific rider benefits are triggered by a loss event and its related costs.

  2. 02

    Summarize claim status

    This capability provides a high level overview of whether a claim is currently guaranteed or still pending.

  3. 03

    Identify document requirements

    This capability builds a specific checklist of the documents you need to prove a benefit is valid.

  4. 04

    Validate expense scope

    It checks if a specific expense is actually covered under the provided rider text.

One connector, every AI

Rider Benefit Matcher 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 Rider Benefit Matcher 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.

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 Rider Benefit Matcher, so you can see the experience inside your AI.

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

Rider Benefit Matcher Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_9TMaadfehQ68PVzvtonDbFwAFmQLYza7AbIkCHt8/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 — Rider Benefit Matcher capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "rider-benefit-matcher-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_9TMaadfehQ68PVzvtonDbFwAFmQLYza7AbIkCHt8/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 Rider Benefit Matcher

See all the AI clients this connector works with ↑

Who it's for

Built for the work Rider Benefit Matcher owners hand off.

This MCP is built for professionals handling insurance documentation and claim processing.

  • 01

    Claims Adjusters

    They hand off the initial verification of rider coverage to the AI.

  • 02

    Insurance Agents

    They use it to quickly explain coverage limits to clients.

  • 03

    Policy Analysts

    They use the logic engine to audit policy application against loss data.

FAQ

Questions Rider Benefit Matcher owners ask.

  • 01

    How does the MCP match expenses to riders?

    It evaluates the verbatim text of the rider against the specific details of the loss and the claimed expenses.

  • 02

    Can this MCP work with my existing AI capabilities?

    Yes, it works with any MCP-compatible client like Claude, Cursor, or Windsurf.

  • 03

    Does it replace a human claims adjuster?

    No, it identifies guaranteed benefits and flags items that still require manual adjudication by a human.

  • 04

    What kind of output does it provide for document needs?

    It generates a specific checklist of documents needed to substantiate a benefit.

  • 05

    Can it tell if an expense is out of scope?

    Yes, it can verify if a specific expense is considered within the scope of the provided rider text.

  • 06

    How does the engine determine if a benefit is an explicit match?

    An explicit match occurs when the loss details satisfy the specific triggers in the rider text and the expense description aligns with the coverage scope.

  • 07

    What happens if a rider uses subjective language?

    If the rider contains subjective qualifiers like 'reasonable' or 'necessary', the item is flagged as requiring insurer confirmation.

  • 08

    Can I use this with Cursor or Claude Desktop?

    Yes, you can connect this MCP server to Cursor, Claude Desktop, VS Code, Windsurf, and any other MCP-compatible client via Vinkius Edge.

Connect Rider Benefit Matcher to Claude, Cursor, ChatGPT & more