Tap
REMOTE · MCP.TAPRUN.DEV · 3 COMPONENTS · SCANNED SEP 20
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 213 tokens (~35/item across 6 items; 4 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Tap MCP server?
Tap is a hosted endpoint at https://mcp.taprun.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.taprun.dev
claude mcp add --transport http leonting1010-tap 'https://mcp.taprun.dev/mcp'
{
"mcpServers": {
"leonting1010-tap": {
"url": "https://mcp.taprun.dev/mcp"
}
}
} {
"servers": {
"leonting1010-tap": {
"type": "http",
"url": "https://mcp.taprun.dev/mcp"
}
}
} [mcp_servers.leonting1010-tap] url = "https://mcp.taprun.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"leonting1010-tap": {
"type": "remote",
"url": "https://mcp.taprun.dev/mcp",
"enabled": true
}
}
} openclaw mcp add leonting1010-tap --url 'https://mcp.taprun.dev/mcp' --transport streamable-http
mcp_servers:
leonting1010-tap:
url: "https://mcp.taprun.dev/mcp" {
"McpServers": {
"leonting1010-tap": {
"Transport": "http",
"Url": "https://mcp.taprun.dev/mcp"
}
}
} assistant mcp add leonting1010-tap -t streamable-http -u 'https://mcp.taprun.dev/mcp'
{
"mcpServers": {
"leonting1010-tap": {
"type": "http",
"url": "https://mcp.taprun.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.taprun.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=taprun.dev | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b12b2f5ce7d929d00e4c4820bd755c20 |
| SANs: taprun.dev, mcp.taprun.dev, *.mcp.taprun.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.taprun.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| taprun.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.taprun.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.taprun.dev/mcp | HTTPS enforced | 301 | https://mcp.taprun.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
capture ~33
Create a tap from URL × intent (local install only).
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
mark ~15
Resolve uncertain intent (local install only).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run ~44
Execute a saved tap. On this edge demo, runs the tab-free demo taps. ref = demo/<name>.
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | – | – |
| ref | string | yes | – |
No output schema declared.
No examples provided.
verify ~30
Read-only substrate check (local install only).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| site | string | – | – |
No output schema declared.
No examples provided.
What is the Tap MCP server?
Tap is an MCP server listed in the public MCP registry as io.github.LeonTing1010/tap. Browser MCP for logged-in tasks. Uses your Chrome, credentials stay local. Zero-token replay. This page covers its hosted endpoint (https://mcp.taprun.dev/mcp).
Is the Tap MCP server safe to use?
Tap scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tap MCP server expose?
Tap exposes 4 tools: capture, verify, mark, run. Their descriptions and schemas cost roughly 122 tokens of context every time the server is loaded.
Does the Tap MCP server require authentication?
No. We connected to Tap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tap MCP server still maintained?
Tap is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.