Developer · Remote MCP server
Eyepup
Agentic visitor analytics - five tools that hand the next CRO fix to your coding agent.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.edholofy/eyepup- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-05-05
- Updated
- 2026-05-05
- Publisher
- edholofy (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/edholofy) · how
- Website
- eyepup.com/mcp-analytics
- Repository
- github.com/edholofy/agentic-analytics (folder mcp)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://eyepup.com/mcp | None |
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 200)
- Handshake
- mcp-typescript server on vercel 0.1.0 · protocol 2025-06-18
- Tools discovered
- Not listed - timeout: no answer within 15 s
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | eyepup-mcp | 0.1.1 | stdio |
How to connect Eyepup
Eyepup is a remote MCP server: there is nothing to install. Its endpoint is https://eyepup.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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: eyepup-mcp version 0.1.1. 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 eyepup-mcp@0.1.1. It reads the environment variable EYEPUP_API_TOKEN (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"eyepup": {
"command": "npx",
"args": [
"-y",
"eyepup-mcp@0.1.1"
],
"env": {
"EYEPUP_API_TOKEN": "<secret>"
}
}
}
}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 developer servers
| Server | Runs |
|---|---|
| ExpoYour Expo and EAS project in natural language: up to date SDK docs, cloud builds (status, logs, trig. | Remote · HTTPLive check: ✓ handshake |
| ExposureGuardDomain security scanning for AI agents. A-F grades, 8 checks, fix snippets. | Local · stdio |
| extensiondev MCPBuild, run, inspect, and publish browser extensions from any MCP client. 31 tools, 11 browsers. | Local · stdio |
| EyebrowseStealthy, LLM-drivable browser engine - a Python library + 85-tool MCP server on stealth Chromium. | Local · stdio |
| Ezoic Setup AssistantEzoic ads implementation assistant: integration docs, SDKs, and working, copyable setup code. | Remote · HTTPLive check: ✓ handshake |
| F5 Distributed Cloud Terraform ProviderF5 Distributed Cloud Terraform provider docs, 270+ OpenAPI specs, and subscription info for AI. | Local · stdio |
| Fable ModeMechanical write gates, evidence receipts, and adversarial review for AI coding agents. | Local · stdio |
| Fabric AtelierAI-powered content processing with 226 Fabric patterns for writing, analysis, and code generation. | Local · stdio |