Tap MCP server
Checked 2026-09-07. Alive: yes. Handshake: verified.
Category: browser-automation. API and field schema.
Facts
| id | leonting1010--tap |
| name | Tap |
| registry_name | io.github.LeonTing1010/tap |
| repo_url | https://github.com/LeonTing1010/tap |
| endpoint_url | https://mcp.taprun.dev/mcp |
| transport | mixed |
| alive | yes |
| liveness_reason | not available |
| check_reachable | yes |
| check_recent_commit | yes |
| check_installable | yes |
| handshake_status | verified |
| handshake_checked_at | 2026-09-07T18:07:15Z |
| handshake_protocol_version | 2024-11-05 |
| handshake_auth_hint | not available |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | none |
| handshake_latency_ms | 1058 |
| handshake_tools_state | listed |
| handshake_tool_count | 4 |
| maintenance_status | active |
| last_commit_at | 2026-08-09T07:41:04Z |
| category | browser-automation |
| license_spdx | MIT |
How to install or connect
Connect your MCP client to https://mcp.taprun.dev/mcp.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.