Other · Remote MCP server
Webeyez
Session replays, JS errors, funnel drop-offs and revenue-loss diagnostics.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.webeyez/webeyez- Version
- 1.0.12
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-02
- Updated
- 2026-09-02
- Publisher
- com.webeyez
- Namespace
- Namespace verified by the MCP Registry via the domain webeyez.com · how
- Website
- webeyez.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.app.webeyez.com/mcp | Authorization (secret), x-api-key (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @webeyez/mcp-server | 1.0.12 | stdio |
How to connect Webeyez
Webeyez is a remote MCP server: there is nothing to install. Its endpoint is https://api.app.webeyez.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares HTTP headers for the connection: Authorization (secret) and x-api-key (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set them with the server's URL.
It can also run locally from a Node.js package published to the npm registry: @webeyez/mcp-server version 1.0.12. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @webeyez/mcp-server@1.0.12.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"webeyez": {
"command": "npx",
"args": [
"-y",
"@webeyez/mcp-server@1.0.12"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| WebanalyzerFree website analyzer: score any public URL 0-100 across 8 quality dimensions. No auth. | Remote · HTTPLive check: ✓ handshake |
| WebAnatomyHelp your AI improve landing pages, grounded in 3,500+ scored sections and 500 real pages. | Remote · HTTPLive check: sign-in required |
| WebAskBuild surveys, read answers and make reports in WebAsk from an AI assistant. | Remote · HTTPLive check: sign-in required |
| Webcake LandingBuild, validate, and persist Webcake landing-page source JSON: element schemas plus AI usage hints. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Webfont License AuditThe 12 licence questions a foundry audit letter asks, run against your CSS. | Local · stdio |
| WebinarIgnition71 AI tools for WordPress webinars: 28 read-only, nothing changes without your OK. | Remote · HTTPLive check: ✓ handshake |
| WebLoom86 tools: drive YOUR real Chrome via CDP + browse/install/publish Threads in chat. webloom.run. | Local · stdio |
| WebMCP EvalEvaluate one public URL for WebMCP readiness: intent, tools observed, recommended, do-not-expose. | Remote · HTTPLive check: sign-in required |