An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Collection Incident Notice Builder 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. Standardize your institutional response to collection issues.

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.

A futuristic MCP client docking bay
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.

Curated set · 4 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Collection Incident Notice Builder.

  1. 01

    Determine recipients

    This capability identifies the specific stakeholders who need to be notified based on the incident type and the status of the item.

  2. 02

    Generate notice draft

    This capability produces the formal written text for an incident notice using your provided observations and established rules.

  3. 03

    Identify missing facts

    This capability analyzes your provided data to find any information gaps that would prevent a standard notice from being completed.

  4. 04

    Suggest record actions

    This capability lists the immediate procedural steps you should take, whether in your collection management system or physically with the item.

Real work

What teams actually run

01

Environmental Damage

When moisture or temperature fluctuations are detected, use the MCP to draft a notice and get a list of immediate containment steps.

02

Pest Infestations

Use the capability to identify which staff to notify and how to physically isolate the affected items.

03

Data Integrity Issues

When a record is found to be incorrect, use the capability to determine the necessary updates in your management system.

04

Routine Audits

Use the capability to ensure that any minor discrepancies found during audits are documented through the proper channels.

One connector, every AI

Collection Incident Notice Builder 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.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

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

You don't need a client to put Collection Incident Notice Builder 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

771ms average. Fast in production.

Collection Incident Notice Builder is checked daily against the live service.

Daily averagePeak 771ms
Oct 11Today
Fastest day
771ms
Slowest day
771ms
14-day trend
Stable0%

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 Collection Incident Notice Builder, so you can see the experience inside your AI.

It does not authenticate your account with Collection Incident Notice Builder. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Collection Incident Notice Builder Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_cpxVbS45KaPJKCWdjdhUXs7vCSyxK5OMWJrhsRpD/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 — Collection Incident Notice Builder capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "collection-incident-notice-builder-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_cpxVbS45KaPJKCWdjdhUXs7vCSyxK5OMWJrhsRpD/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? Set up Collection Incident Notice Builder in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Collection Incident Notice Builder owners hand off.

This MCP is built for professionals managing physical collections who need to standardize how they report and respond to issues.

  • 01

    Museum Curators

    Use it to draft formal documentation when items are found to be damaged or misplaced.

  • 02

    Archivists

    Hand off incident details to the AI to ensure all stakeholders are notified per protocol.

  • 03

    Collections Managers

    Use the capability to generate immediate action lists for pest or environmental issues.

FAQ

Questions Collection Incident Notice Builder owners ask.

  • 01

    What kind of AI clients can I use with this MCP?

    You can use any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 02

    Do I need to host the MCP myself?

    No, Vinkius hosts and manages the MCP for you. You just connect your client and start working.

  • 03

    Can this MCP help with physical handling of items?

    Yes, the suggest_record_actions capability provides specific procedural steps for both digital records and physical handling, such as isolating items.

  • 04

    How does the capability know who to notify?

    The determine_recipients capability identifies the correct stakeholders based on the specific type of incident and the status of the item.

  • 05

    Will it help me if my incident report is incomplete?

    Yes, the identify_missing_facts capability analyzes your data to tell you exactly what information is still needed to complete a standard notice.

Explore

More in Workflow Automation

Suggestions

Connect Collection Incident Notice Builder to Claude, Cursor, ChatGPT & more