UserTapes MCP server
online · 100% uptimeio.github.mcdca/usertapes-mcp·v1.0.1Query real user session replay data: tapes, transcripts, error/rage-click filters, alerts.
0 stars
Reviews
Write oneNobody has reviewed UserTapes yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
UserTapes tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 518ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityauth enforced (unknown)9/15
- Maintenancelast push 52 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How UserTapes compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 589 ms
- faster than 24% of 30,031 servers
Install UserTapes in Claude Code, Cursor or VS Code
claude mcp add --transport http usertapes-mcp https://usertapes.com/mcp
What the publisher says
From the UserTapes repository's README, as published. We do not edit it. Read it on GitHub
UserTapes MCP Server
UserTapes is a session replay tool. This is its Model Context Protocol server: a hosted, stateless JSON-RPC endpoint that lets any MCP client — Claude Code, Claude Desktop, Cursor, or your own agent — query what real users did on your site.
This repo does not contain the server's application source (that lives in the main UserTapes codebase). It exists to document and register the public connection details: the endpoint, its tools, and how to authenticate.
Why
Your coding agent can read your repository, your git history, and your test output. None of that describes what a real person actually did when something broke. UserTapes derives a text transcript from every recorded session — clicks, navigation, errors, rage clicks — so an agent can query sessions the same way it queries anything else, instead of you exporting a video and pasting it into a prompt.
Connecting
The server is one HTTP endpoint speaking stateless JSON-RPC 2.0 over Streamable HTTP (protocol revision 2025-06-18). Get a token from your account's Agent access page, then add:
{
"mcpServers": {
"usertapes": {
"url": "https://usertapes.com/mcp",
"headers": { "Authorization": "Bearer YOUR_MCP_TOKEN" }
}
}
}No package install, no local process — the client talks to https://usertapes.com/mcp directly.
Tools
The MCP token is a distinct, revocable, read-scoped credential — separate from a site's ingest-only tracking token. Its only write surface is alerts; it cannot delete a recording, change a site, or touch billing.
Docs
- MCP server docs — endpoint, auth, connection config, full tool reference
- MCP agent access — feature overview
- Session replay over MCP — full protocol details and tool schema
License
MIT — see LICENSE. (This repo is documentation and a registry manifest; the UserTapes application itself is closed source.)
Nothing above is checked by us. What we check is on the safety report.
UserTapes: common questions
- Is UserTapes MCP server safe?
- Mostly: it is graded B (82/100). Read the UserTapes safety report
- How do I install UserTapes?
- It runs remotely at usertapes.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does UserTapes need an API key?
- Yes. The registry entry asks for
Authorization. - Is UserTapes maintained?
- The last commit was 93 days ago (2026-08-03). The latest release is v1.0.1.
- Is UserTapes up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does UserTapes compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 589 ms (faster than 24% of 30,031 servers). Full comparison.