Skip to main content
ClaudeWave

Credential isolation for AI agents — stop leaking secrets to your agents. TAP is a credential proxy: agents never see secret values; optional human approval on sensitive calls. By human.tech (Apache-2.0).

MCP ServersOfficial Registry11 stars0 forksRustApache-2.0Updated yesterday
Install in Claude Code / Claude Desktop
Method: Manual · tap-oss
Claude Code CLI
git clone https://github.com/holonym-foundation/tap-oss
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "tap-oss": {
      "command": "tap-oss"
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Install the binary first: cargo install tap-oss (or build from https://github.com/holonym-foundation/tap-oss).
Use cases

MCP Servers overview

# 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](https://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](https://docs.tap.human.tech/security), and each
hosted release's enclave measurement is published in [`measurements/`](measurements/).
Hosted deployment and operational infrastructure are maintained separately from this repository.

## Security

See [`SECURITY.md`](SECURITY.md) to report a vulnerability.

## License

[Apache-2.0](LICENSE): 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

```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
```
agent-securityai-agentscredentialsllm-securitymcpproxysecrets-management

What people ask about tap-oss

What is holonym-foundation/tap-oss?

+

holonym-foundation/tap-oss is mcp servers for the Claude AI ecosystem. Credential isolation for AI agents — stop leaking secrets to your agents. TAP is a credential proxy: agents never see secret values; optional human approval on sensitive calls. By human.tech (Apache-2.0). It has 11 GitHub stars and was last updated yesterday.

How do I install tap-oss?

+

You can install tap-oss by cloning the repository (https://github.com/holonym-foundation/tap-oss) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is holonym-foundation/tap-oss safe to use?

+

holonym-foundation/tap-oss has not been audited yet by our security agent. Review the original repository on GitHub before using it in production.

Who maintains holonym-foundation/tap-oss?

+

holonym-foundation/tap-oss is maintained by holonym-foundation. The last recorded GitHub activity is from yesterday, with 0 open issues.

Are there alternatives to tap-oss?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy tap-oss to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: holonym-foundation/tap-oss
[![Featured on ClaudeWave](https://claudewave.com/api/badge/holonym-foundation-tap-oss)](https://claudewave.com/repo/holonym-foundation-tap-oss)
<a href="https://claudewave.com/repo/holonym-foundation-tap-oss"><img src="https://claudewave.com/api/badge/holonym-foundation-tap-oss" alt="Featured on ClaudeWave: holonym-foundation/tap-oss" width="320" height="64" /></a>

More MCP Servers

tap-oss alternatives