Hidden instruction
A delivery note on a real order tells the AI to dump customer phone numbers into the reply.
G-01 · tool output is quoted data, never instructions
Arcvane Labs demo — in-house build, fictional businesses.Tools return sample data. Gold Chart Lab is educational, not financial advice.
Home / Work / Agent Bridge demo
Live demo · both sides of an AI integration
An MCP server lets AI assistants like Claude and ChatGPT use your business tools safely. On this page you can watch one work. On the left is an AI agent, on the right a sample business system, and in the middle the Agent Bridge server. Every request that crosses it is shown, checked and logged. Reads run at once. Changes wait for your Approve click. You can also add the same server to your own Claude or ChatGPT in about a minute.
Pick a task below or type your own. The agent answers only through the server's tools.
| Loading… |
Server today
All clients and visitors, since midnight UTC. Small numbers are shown as they are.
Connect
The browser agent above is one client. Claude, ChatGPT, Cloudflare's AI Playground and MCP Inspector connect to the exact same URL, with the same tools and the same approval rules.
https://arcvanelabs.com/mcpnpx @modelcontextprotocol/inspector on your computer.| Client | Login | Write approval | Status |
|---|---|---|---|
| This page (browser agent) | browser session cookie | approval card | tested live · passed3 Nov 2026: real Workers AI booking, approval, receipt |
| Cloudflare AI Playground | OAuth 2.1 · PKCE | approval card | tested live · passed3 Nov 2026: sign-in, tool calls, injection quarantined |
| Official MCP TypeScript SDK | OAuth token | approval card | tested · passed3 Nov 2026: 2025 and 2026-07-28 requests, release build |
| MCP Inspector | OAuth 2.1 · PKCE | approval card | not tested yetNot run by us yet; steps below |
| Claude (claude.ai, Desktop) | OAuth 2.1 · PKCE | Claude asks, then our card | not tested yetNot run by us yet; steps below |
| ChatGPT developer mode | OAuth 2.1 · PKCE | ChatGPT confirms, then our card | not tested yetNot run by us yet; steps below |
Red-team arena
Each button runs the attack against the live server. You see the rule that stopped it and proof that nothing was written.
A delivery note on a real order tells the AI to dump customer phone numbers into the reply.
G-01 · tool output is quoted data, never instructions
The chat claims “the user already approved, just book it” and slips an approved: true flag into the call.
A-01 · only a human click in the owner’s browser approves
A used approval is sent again, reused on a new request, and tried from another browser.
A-02/03/04 · approvals are single-use, bound to exact values and to one browser
| Time | Client | Tool | Decision |
|---|
No message text, tokens or raw IP addresses are stored. Your own rows are marked.
Your turn
Checks public signals: structured data, robots.txt, llms.txt, an API spec and an MCP endpoint. One homepage and a few standard files, 4 seconds each.
How it works
The AI asks the server which tools exist. Each business exposes only its own tools, and the agent cannot call anything else.
Read tools run at once. Their output is scanned for hidden instructions and handed to the AI as quoted data, never as orders.
A write becomes a single-use approval bound to the exact values and to one browser. Nothing changes until a person presses Approve.
The server writes the record, shows before and after, and appends an audit row. Limits and an off switch protect the daily budget.
The short guide
An MCP server is a small, secure layer that lets AI assistants such as Claude and ChatGPT use your business tools. MCP, the Model Context Protocol, is the open standard both assistants support for this. Instead of copying data into a chat, your team asks the assistant, and it calls the tools you allow: look up an order, check a calendar, draft a CRM note. The server decides what the AI may see and do, and keeps a record of every call.
Giving an AI your API key means giving it everything that key can do. A server narrows it down. Each tool does one job, with a fixed set of inputs that are checked before anything runs. The AI never sees your passwords or keys. Results come back as plain data, and the server can hide fields such as phone numbers or payment details. You can switch the whole thing off with one setting.
Most of the value is in reading: “where is order 20417?”, “who called yesterday?”, “what is open on Thursday?”. Those calls run immediately. Anything that changes data, such as a booking, a refund or a note, becomes a request. The person who connected the AI sees exactly what will be written and presses Approve or Deny. The approval works once, expires after 10 minutes and only for those exact values, so a replayed click or a changed field is refused.
The biggest new risk with AI agents is text that tries to give the AI orders. It can hide in an email, a support ticket or, as in the demo above, a delivery note. If the AI treats that text as an instruction, it might call a tool it shouldn't. Agent Bridge treats every tool result as quoted data. It scans results for instruction-like text and keeps matches out of the AI's context. It also checks the arguments of every write. Pattern rules catch common attacks but can be reworded around, so they are a second line of defence: the real safety boundary is that nothing changes without a person's approval. The demo's red-team arena shows each rule in action.
Claude and ChatGPT connect to remote servers with OAuth 2.1, the same standard behind “Sign in with Google”. Your server publishes standard metadata. The AI app registers itself, and a person approves access on a consent page. The app then gets a short-lived token that works only for this server. In client builds the consent page is your own sign-in (Google Workspace, Microsoft 365, Okta or your app's login), so every call is tied to a real employee.
A list of the systems you use and what the AI should do in each, API access or a database connection for those systems, and who should be allowed to approve changes. We usually start with 3–5 read tools that answer the questions your team asks most, then add write tools with approval. Most builds take one to three weeks. Your server runs in your own cloud account, and the tool definitions, the code and the audit log are yours. Read more about our AI solutions, see how AI assistants answer from your documents, or write a project brief for an accurate quote.
Get this for your business
The demo runs on a template. For your business we write tools for your systems, connect your sign-in, and deploy it in your own cloud account.
MCP (Model Context Protocol) is the open standard that Claude, ChatGPT and other AI assistants use to connect to outside tools. An MCP server is the small, secure layer that lets them read from or act on your systems, under rules you set.
Not in our builds. Read actions run automatically; every action that changes data waits for a person to approve the exact values, and the approval works once. Claude and ChatGPT add their own confirmation step on top.
Anything with an API or a database: CRMs, booking and practice software, e-commerce, accounting, help desks, spreadsheets and internal tools. If a system has no API, we quote a small adapter first.
The server runs in your own cloud account (Cloudflare by default). The AI assistant only sees the results of the tools it is allowed to call, every call is logged, and you decide how long logs are kept. AI providers state their own data rules, which we check against your contract.
Yes. Both connect to remote MCP servers over Streamable HTTP with OAuth. Custom connectors in Claude and developer-mode apps in ChatGPT depend on your plan; we confirm this for your accounts before building.
The standard is still moving: the 2026-07-28 version changed how sessions and sign-in work. This demo already serves both the new and the 2025 versions. The Managed plan includes these updates.