Platform · MCP gateway

Four tools, not twenty-four. Every MCP call governed.

MCP servers expose everything. An agent needs a fraction. TapPass understands each tool, grants only what a job needs, and puts a person on the calls that matter.

✓No credit card needed

4 servers · 24 toolsfor this job
Eoget_invoiceExact Online · read invoice✓
Eolook_up_supplierExact Online · read records✓
Kbcreate_paymentKBC Business · move money✓
M3send_mailMicrosoft 365 Mail · send email✓
Zedelete_ticketZendesk · not needed
Eoexport_ledgerExact Online · not needed
Virtual server Procurement tools /mcp/v/procurement
get_invoicelook_up_suppliercreate_paymentsend_mail
Granted to Procurement agent · 4 of 24 tools
01Classified by intent

Add a server. Your rules already apply.

TapPass reads every tool a server offers and classifies what it does: read, write, send outside, delete, pay. Your rules are written against those intents, so a new server needs no new policy. A person confirms each classification, and a changed tool waits for review.

ToolIntentStatus
exact.get_invoiceread invoiceConfirmed
exact.look_up_supplierread recordsConfirmed
kbc.create_paymentmove moneyConfirmed
m365.send_mailsend emailChanged · in review
zendesk.delete_ticketdeleteCandidate · confirm
02Least privilege for agents

The right tools, for the right agent.

Scope by team, project or personEvery tool is granted to exactly who needs it. Nothing more, nothing standing.
Compose virtual serversPick tools from several servers and expose only those, as one server built for one job.
A person on risky callsPayments, deletes and exports wait for a named approver, signed with a passkey.
No silent changesWhen a server changes a tool, it waits for review before any agent uses it.
Watch, then proposeTapPass watches real traffic and drafts the least-privilege grant. You approve it.
Every call on the recordWhich agent called which tool, for whom, with which arguments, and what was decided.
03Connect

One entry in your MCP config. That is it.

Claude Code, Cursor, VS Code or your own agent: point the client at TapPass, or at one virtual server. Tool calls are governed before they reach the servers behind it.

mcp.json
{
  "mcpServers": {
    "tappass-procurement": {
      "url": "https://<your-tappass>/mcp/v/procurement",
      "headers": {
        "Authorization": "Bearer ${TAPPASS_KEY}"
      }
    }
  }
}
The Procurement agent sees 4 of 24 tools. Nothing else exists for it.
04In the product

Every server, every tool. In one place.

TapPass connected systems: MCP servers and their tools for Vandaele Logistics
Next: the Verdict APIAsk before an agent acts. Enforce in your own code.
Questions

Straight answers about MCP.

Something else on your mind? Talk to our team.

Our MCP server already has authentication. Why add this?

Server authentication answers who connected, not which tool this agent may call for this job. TapPass permissions individual tools per agent, holds the risky ones for a person and records every call, across every MCP server, from one place.

What is a virtual MCP server?

A server you compose from tools on several real servers, for one job. The agent connects to it and sees only those tools.

How does TapPass know what a tool does?

It reads each tool definition and classifies it by intent, such as reading, sending outside, deleting or moving money. A person confirms the classification before it counts.

Will per-tool control slow teams down?

No. TapPass watches real traffic first, then drafts the least-privilege grant. Teams get exactly what they use, without a ticket queue.

What if a server changes its tools?

A changed tool waits for review before any agent can use it again, so nothing changes silently.

Four tools, not twenty-four. Start with the servers you have.

Connect one agent and see every call TapPass would have held, stopped or routed elsewhere. Nothing is blocked while you learn.

✓ Free for one person✓ No credit cardBacked by Start it @KBCVLAIO✓ EU hosted✓ Built in Belgium✓ Your own model keys✓ Encrypted at rest and in transit✓ DPA on request