English Français العربية

TAP

Official registry Security

Credential isolation for AI agents: placeholder secrets, policy checks, optional human approval.

Source code Website Documentation

What can you do with TAP?

  • auditing request routing and connector behavior
  • debugging failed requests
  • understanding approval flows
  • improving connector-side request shaping
  • contributing fixes to the core TAP experience

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http tap 'https://mcp.tap.human.tech/mcp' --header 'X-TAP-Key: <TAP agent API key (create one at tap.human.tech)>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "tap": {
            "type": "http",
            "url": "https://mcp.tap.human.tech/mcp",
            "headers": {
                "X-TAP-Key": "<TAP agent API key (create one at tap.human.tech)>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Tool Authorization Protocol (TAP)
  2. Start Here
  3. Included
  4. Not Included
  5. Security
  6. License
  7. Contributing
  8. Testing

Tool Authorization Protocol (TAP)

Credential isolation, approval gating, and connector routing for AI agents.

This repository contains the code that is most useful for:

  • auditing request routing and connector behavior
  • debugging failed requests
  • understanding approval flows
  • improving connector-side request shaping
  • contributing fixes to the core TAP experience

[!WARNING] Self-hosting means you own the security of your credentials and signing keys. TAP keeps secrets out of your agents, but running it yourself puts the host hardening, key isolation, and correct policy-engine operation on you. It's a path for teams that are well versed in security. For everyone else the hosted version is strongly recommended: credentials sit in a hardware enclave we can't read into, with no ops to run. Start free at tap.human.tech.

Start Here

  • crates/tap-proxy/src/routing.rs — how TAP resolves connector target shapes
  • crates/tap-proxy/src/placeholder.rs — credential substitution and position validation
  • crates/tap-proxy/src/policy.rs — approval policy enforcement
  • docs/ — full documentation including self-hosting guide

Included

  • core proxy and storage crates
  • Telegram and Matrix approval bots
  • remote MCP server (tap-mcp)
  • CLI
  • docs (self-hosting, API reference, credential setup)

Not Included

  • enclave deployment glue (CCE policy generation, release-policy automation, ARM templates, env config)
  • production workflows and secret bootstrapping
  • managed hosting operations glue
  • the hosted dashboard UI source (a placeholder is shipped so the proxy compiles)

The enclave key-management source is included (key_provider_enclave.rs, kms_azure.rs, skr.rs) — it's the custody model documented at docs.tap.human.tech/security, and each hosted release's enclave measurement is published in measurements/. Hosted deployment and operational infrastructure are maintained separately from this repository.

Security

See SECURITY.md to report a vulnerability.

License

Apache-2.0: free to use, read, modify, and self-host. This repo is the open-source TAP runtime (tap-core, tap-proxy, tap-bot, tap-cli, tap-mcp). The hosted dashboard and managed-service deployment glue are proprietary and live in a separate private repo.

Contributing

See CONTRIBUTING.md.

Testing

# Needs Postgres (default postgres://tap:tap@localhost:5434/tap, override with
# POSTGRES_DATABASE_URL). Isolated suites parallelize; env-mutating unit tests stay serial.
cargo test -p tap-core
cargo test -p tap-proxy --test integration --test e2e
cargo test -p tap-proxy -p tap-bot -p tap-cli --lib --bins -- --test-threads=1

Frequently asked questions

What is TAP?

Credential isolation for AI agents: placeholder secrets, policy checks, optional human approval.

How do I install TAP?

It runs as a remote server. In Claude Code: claude mcp add --transport http tap 'https://mcp.tap.human.tech/mcp' --header 'X-TAP-Key: <TAP agent API key (create one at tap.human.tech)>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does TAP need an API key?

Yes. It expects X-TAP-Key, which you set in its configuration.

Is TAP open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains TAP?

It is published by holonym-foundation. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.