Which Perplexity app supports this?

The Perplexity app for Mac. MCP connectors live in the Mac app's settings; the web and mobile apps don't offer the Connectors panel today.

If I connect Business Interruption Claim Log to Perplexity, can I use the same connection in Claude or ChatGPT later?

Yes, and that's the point: the connection is yours, not Perplexity's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and Business Interruption Claim Log is already there.

Do I need to hand my Business Interruption Claim Log password to Perplexity?

Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Perplexity only ever sees the link, and you can remove it whenever you want.

What can I actually ask Perplexity to do with Business Interruption Claim Log?

Whatever the Connector covers: check data, run actions and bring answers back into the thread. The Connector page lists every capability your AI gains, with real examples you can copy.

Perplexity doesn't show the Connector. What do I check?

Make sure the connector shows Running in the Connectors list and that it's switched on under Sources on the homepage, then confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.

Can I remove the access later?

Anytime. Remove the connector in Perplexity's Connectors settings and it's out of your threads. Your Vinkius account keeps the connection and its history either way, ready for the next AI.

How to give Perplexity access to Business Interruption Claim Log

Set up in minutes on your Mac. From then on, Perplexity gets things done for you: Business Interruption Claim Log becomes one of its Sources, ready in every thread.

Ask AI about this guide

Business Interruption Claim Log Connector

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

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

Connecting Business Interruption Claim Log to Perplexity

A few minutes, in the Perplexity Mac app

1In the Perplexity Mac app, open Account, choose Connectors, and click Add Connector.
2In the Simple tab, choose MCP Connector, name it, and add the bridge command with your Business Interruption Claim Log link: npx mcp-remote <your link>. The link above is the URL.
3Click Save and check it shows Running, then turn the connector on under Sources on the homepage. Business Interruption Claim Log is now part of your Perplexity.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "business-interruption-claim-log-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_Rnt0rMMa0m27NlTNVrsCu13fo8dG5NNFdRkFEke1/mcp"
    }
  }
}

Perplexity + Business Interruption Claim Log

One thread. Your Business Interruption Claim Log, live inside Perplexity.

Real prompts, answered with live data. This is the kind of conversation you will have in Perplexity once the connector is in.

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

These prompts ship with the Business Interruption Claim Log Connector. Once yours is connected, they work in your threads.

The full capability set, the prompts and the observed latency live on the Business Interruption Claim Log Connector page.

Mission Control

See everything your Perplexity agents do in Business Interruption Claim Log.

When Perplexity runs a tool in Business Interruption Claim Log, it happens on Perplexity's side: you see the answer, but not the request itself, what data it carried, or whether a rule was broken.

Now every move lands on your screen.

Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.

AI Briefing

Upgrade to unlock

Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.

Requests

Total in this period

Avg Latency

API 88ms · Overhead 54ms

Vinkius Reliability

Agent 280 · Upstream 47 · Vinkius 15

Tokens

AI tokens processed

DLP Protected

Sensitive data redacted

Cost Saved

FinOps truncations applied

AI Agents Activities

last 30 days

30d agotoday

Request Volume & Latency

requests latency

Every request your Perplexity agents make through Business Interruption Claim Log is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your Business Interruption Claim Log workflows.

What sets us apart

It's not just the Connector that stays safe. Everything your agents do through it is.

Connecting Business Interruption Claim Log to your AI is step one. But an open line between your agents and Business Interruption Claim Log is only half the story: without protection, every action they take runs unguarded.

That's why protection doesn't stop at the door.

Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.

Tamper Proof Activity Log

Every request your agents make in Business Interruption Claim Log is recorded and signed, so any change to the history becomes detectable.

Automatic Key Rotation

We rotate security keys every 24 hours. Your Business Interruption Claim Log connection stays protected without any manual work.

Spending Protection

We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your Business Interruption Claim Log actions never surprise you.

Isolated Sandbox

Every execution through Business Interruption Claim Log runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.

Security Event Streaming

Security events flow to Splunk, Datadog or your own webhook, so Business Interruption Claim Log activity lands in the tools you already rely on.

Instant Resume

Idle connections resume in 3 to 5 ms while preserving their state, keeping your Perplexity threads responsive.

Malicious File Protection

We detect compressed files designed to exhaust system resources and block them before they ever reach Business Interruption Claim Log.

Credential Validation

We test your Business Interruption Claim Log credentials before saving them. Invalid credentials are rejected instead of being stored.

Separate Usage Limits

Usage stays isolated per account, so activity in one connection never consumes another account's allowance.

One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.

These guarantees are not add-ons: they are the infrastructure every Business Interruption Claim Log connection runs on. Read how our infrastructure protects everything your Perplexity agents do, end to end.

Inside Vinkius

Get Business Interruption Claim Log ready for your AI. It's easy.

You choose Business Interruption Claim Log from the Vinkius Catalog and get one connection link. That's it.

You choose Business Interruption Claim Log
You find Business Interruption Claim Log in the Catalog and install the Connector with one click.
Business Interruption Claim Log
Active
Enable Connector
Activating…
You add the connector in Perplexity
Vinkius gives you one connection link. In the Perplexity Mac app, you add an MCP Connector under Account and Connectors, bridge it with npx mcp-remote and your link, save, and switch it on under Sources.
Token generated successfully
MCP Connection URL
https://edge.vinkius.com/vk_preview_Rnt0rMMa0m27NlTNVrsCu13fo8dG5NNFdRkFEke1/mcp
Connection Token
vk_live_••••••••
Go to Dashboard

Set it up once. Use Business Interruption Claim Log with the AI you already use.

FAQ

Perplexity access questions.

01
Which Perplexity app supports this?
The Perplexity app for Mac. MCP connectors live in the Mac app's settings; the web and mobile apps don't offer the Connectors panel today.
02
If I connect Business Interruption Claim Log to Perplexity, can I use the same connection in Claude or ChatGPT later?
Yes, and that's the point: the connection is yours, not Perplexity's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and Business Interruption Claim Log is already there.
03
Do I need to hand my Business Interruption Claim Log password to Perplexity?
Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Perplexity only ever sees the link, and you can remove it whenever you want.
04
What can I actually ask Perplexity to do with Business Interruption Claim Log?
Whatever the Connector covers: check data, run actions and bring answers back into the thread. The Connector page lists every capability your AI gains, with real examples you can copy.
05
Perplexity doesn't show the Connector. What do I check?
Make sure the connector shows Running in the Connectors list and that it's switched on under Sources on the homepage, then confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.
06
Can I remove the access later?
Anytime. Remove the connector in Perplexity's Connectors settings and it's out of your threads. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about Business Interruption Claim Log? The Connector page answers them. See everything the Business Interruption Claim Log Connector can do

About the Connector

What Business Interruption Claim Log adds to your AI.

Once you connect it, your AI gains 4 capabilities: the exact actions it can take in Business Interruption Claim Log when you ask. The Connector page lists every one of them in detail, alongside the latency we measure in production and prompts worth trying first.

See everything the Business Interruption Claim Log Connector can do