What kind of decisions can this MCP make?

The engine produces four specific outcomes: Approve, Decline, Conditional Access, or Request-Information.

How does it handle donor restrictions?

It uses a specific capability to check every request against the private agreements and conditions established by the collection's donor.

Can I use this with Claude or Cursor?

Yes, you can connect this MCP to any MCP-compatible client including Claude, Cursor, and Windsurf.

Does it check legal constraints?

Yes, it evaluates item restrictions to ensure the requested interaction complies with legal and physical constraints.

What is the main purpose of this MCP?

It is a decision-support engine designed to automate the reconciliation of requester identities against item restrictions and institutional policies.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Collection Access Decision Engine 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. Automate compliance checks for sensitive archival and library collections.

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.

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 Access Decision Engine.

01
Analyze request eligibility tool
This capability determines if a requester's profile matches your broad institutional access policies and any specific exception rules.
02
Check donor compliance tool
Use this to ensure a request doesn't break any private agreements made with a collection's donor.
03
Evaluate item restrictions tool
This capability checks the physical or legal constraints of a specific item to see if the requested interaction is allowed.
04
Synthesize final decision tool
This capability aggregates all previous checks into one actionable decision with clear next steps.

Real work

What teams actually run

Researcher Access Requests

Evaluate if a researcher can use or reproduce specific archival items.

Donor Agreement Enforcement

Verify that access requests do not violate specific conditions set by donors.

Student Eligibility Checks

Confirm that students meet the necessary requirements to view restricted archives.

Commercial Usage Review

Determine if commercial entities are permitted to interact with specific collections.

One connector, every AI

Collection Access Decision Engine 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 Collection Access Decision Engine 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 Collection Access Decision Engine, so you can see the experience inside your AI.

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

Collection Access Decision Engine Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_wInTGVl3o2fiBOvYnn1O4cRX40e506evEH5jPUq4/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 — Collection Access Decision Engine capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "collection-access-decision-engine-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_wInTGVl3o2fiBOvYnn1O4cRX40e506evEH5jPUq4/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 Access Decision Engine in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Collection Access Decision Engine owners hand off.

This MCP is built for institutions managing sensitive, restricted, or donor-funded collections.

01
Archivists
They hand off the task of checking requester credentials against complex donor rules.
02
Librarians
They use the engine to validate access requests for restricted library materials.
03
Compliance Officers
They rely on the capability to ensure all access decisions follow legal and institutional mandates.

FAQ

Questions Collection Access Decision Engine owners ask.

01
What kind of decisions can this MCP make?
The engine produces four specific outcomes: Approve, Decline, Conditional Access, or Request-Information.
02
How does it handle donor restrictions?
It uses a specific capability to check every request against the private agreements and conditions established by the collection's donor.
03
Can I use this with Claude or Cursor?
Yes, you can connect this MCP to any MCP-compatible client including Claude, Cursor, and Windsurf.
04
Does it check legal constraints?
Yes, it evaluates item restrictions to ensure the requested interaction complies with legal and physical constraints.
05
What is the main purpose of this MCP?
It is a decision-support engine designed to automate the reconciliation of requester identities against item restrictions and institutional policies.

Explore

More in Compliance

Connect Collection Access Decision Engine to Claude, Cursor, ChatGPT & more

Connect Collection Access Decision Engine to your AI

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