Credential isolation for AI agents: placeholder secrets, policy checks, optional human approval.
Connect Remote server
claude mcp add --transport http tap https://mcp.tap.human.tech/mcp --header "X-TAP-Key: <X_TAP_KEY>"
{
"mcpServers": {
"tap": {
"url": "https://mcp.tap.human.tech/mcp",
"headers": {
"X-TAP-Key": "<X_TAP_KEY>"
}
}
}
}
{
"servers": {
"tap": {
"type": "http",
"url": "https://mcp.tap.human.tech/mcp",
"headers": {
"X-TAP-Key": "<X_TAP_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.tap.human.tech/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
X-TAP-KeyRequired, secret | TAP agent API key (create one at tap.human.tech) |
Details
| Endpoint | https://mcp.tap.human.tech/mcp (Streamable HTTP) |
| First published | 24 Jul 2026 |
| Last updated | 24 Jul 2026 |
| Registry name | tech.human/tap |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
