
OFAC SLS Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_TszmHms9sUMPFFpa76scK5iViJAg35Vph1m7PIJi/mcpConnecting OFAC SLS to VS Code
About a minute, in VS Code
- 1Run MCP: Add Server from the Command Palette (or create .vscode/mcp.json in your project).
- 2Add a server named OFAC SLS with type http and your link as the url. The link above is the URL.
- 3Save and ask something real in Copilot Chat. OFAC SLS is now part of VS Code.
{
"mcpServers": {
"ofac-sanctions-service-mcp": {
"url": "https://edge.vinkius.com/vk_preview_TszmHms9sUMPFFpa76scK5iViJAg35Vph1m7PIJi/mcp"
}
}
}VS Code + OFAC SLS
One chat. Your OFAC SLS, live inside VS Code.
Real prompts, answered with live data. This is the kind of session you will have in VS Code once the server is in.
Waiting for input…
Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.
These prompts ship with the OFAC SLS Connector. Once yours is connected, they work in your sessions.
The full capability set, the prompts and the observed latency live on the OFAC SLS Connector page.
Mission Control
See everything your VS Code agents do in OFAC SLS.
When VS Code runs a tool in OFAC SLS, it happens in your editor: you see the result, 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.
Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.
AI Agents Activities
last 30 daysRequest Volume & Latency
requests latencyEvery request your VS Code agents make through OFAC SLS is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your OFAC SLS workflows.
What sets us apart
It's not just the Connector that stays safe. Everything your agents do through it is.
Connecting OFAC SLS to your AI is step one. But an open line between your agents and OFAC SLS 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 OFAC SLS is recorded and signed, so any change to the history becomes detectable.
Automatic Key Rotation
We rotate security keys every 24 hours. Your OFAC SLS 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 OFAC SLS actions never surprise you.
Isolated Sandbox
Every execution through OFAC SLS 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 OFAC SLS 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 VS Code sessions responsive.
Malicious File Protection
We detect compressed files designed to exhaust system resources and block them before they ever reach OFAC SLS.
Credential Validation
We test your OFAC SLS 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 OFAC SLS connection runs on. Read how our infrastructure protects everything your VS Code agents do, end to end.
Inside Vinkius
Get OFAC SLS ready for your AI. It's easy.
You choose OFAC SLS from the Vinkius Catalog, sign in to your OFAC SLS account, and get one connection link. That's it.
You choose OFAC SLS
You find OFAC SLS in the Catalog and install the Connector with one click.
OFAC SLS
Active
Enable ConnectorActivating…You sign in
You connect your OFAC SLS account and choose what you want your AI to access. Your credentials stay encrypted and separate from your AI.
Configure Credentials
Configure credentials for {{connectorName}}
RequiredEncryptedSave & ContinueYou add the link in VS Code
Vinkius gives you one connection link. In VS Code, you run MCP: Add Server or add an entry in .vscode/mcp.json with your link as the url, and the connection is ready.
Token generated successfully
MCP Connection URL
https://edge.vinkius.com/vk_preview_TszmHms9sUMPFFpa76scK5iViJAg35Vph1m7PIJi/mcpGo to DashboardConnection Token
vk_live_••••••••
Set it up once. Use OFAC SLS with the AI you already use.
FAQ
VS Code access questions.
- 01
Which VS Code feature does this use?
The MCP support built into VS Code: run MCP: Add Server from the Command Palette, or use .vscode/mcp.json (workspace) and the user profile config, with type http and the url field for remote servers.
- 02
If I connect OFAC SLS to Gemini, can I use the same connection in Claude or ChatGPT later?
Yes, and that's the point: the connection is yours, not Gemini'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 OFAC SLS is already there.
- 03
Do I need to hand my OFAC SLS password to Gemini?
Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Gemini only ever sees the link, and you can remove it whenever you want.
- 04
What can I actually ask Gemini to do with OFAC SLS?
Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.
- 05
Gemini doesn't show the Connector. What do I check?
Make sure the server appears in your MCP list and the url was pasted exactly as copied, then confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.
- 06
Can I remove the access later?
Remove the server from your mcp.json (or run MCP: Open User Configuration to edit it) and it's out of your sessions. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about OFAC SLS? The Connector page answers them. See everything the OFAC SLS Connector can do
About the Connector
What OFAC SLS adds to your AI.
Once you connect it, your AI gains 10 capabilities: the exact actions it can take in OFAC SLS 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 OFAC SLS Connector can do