tech.human/tap Model Context Protocol (MCP) Server

This MCP server provides credential isolation for AI agents using placeholder secrets, policy checks, optional human approval, and connector routing. It focuses on auditing request routing and connector behavior, debugging failed requests, and understanding approval flows for the TAP experience.

🛠️ Key Features

Credential isolation for AI agents
Placeholder secrets to prevent sharing sensitive data with agents
Policy checks
Optional human approval gating
Connector routing for requests

🚀 Use Cases

Auditing request routing and connector behavior
Debugging failed requests
Understanding approval flows
Improving connector-side request shaping
Contributing fixes to the core TAP experience

⚡ Developer Benefits

Easier debugging of routing and connector behavior
Clear insight into approval flow behavior
Helps trace and shape connector-side requests during fixes

⚠️ Limitations

Self-hosting requires responsibility for security of credentials and signing keys
Documentation notes that TAP keeps secrets out of agents, but host hardening and correct policy handling are still required

Related Topics

agent-security, ai-agents, credentials, llm-security, mcp, proxy, secrets-management

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.

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.

Testing

bash

# 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

Install

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.tap.human.tech/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "tap": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.tap.human.tech/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

TAP

tech.human/tap Model Context Protocol (MCP) Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Related Topics

Topics

Tool Authorization Protocol (TAP)

Start Here

Included

Not Included

Security

License

Contributing

Testing

Install

Remote endpoint

Related servers