Developer · Remote MCP server
Vinktar
Product analytics and error tracking your coding agent can use.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.vinktar/mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-29
- Updated
- 2026-09-29
- Publisher
- com.vinktar
- Namespace
- Namespace verified by the MCP Registry via the domain vinktar.com · how
- Website
- vinktar.com/docs/mcp
- Repository
- github.com/vinktarhq/agent
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.vinktar.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 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
How to connect Vinktar
Vinktar is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.vinktar.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.
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 |
|---|---|
| ViewportWitness by Apex LabsAgent website testing: browser QA, visual regression, Markdown extraction, and security checks. | Remote · HTTPLive check: ✓ handshake |
| VigíaWhat breaks between versions, per-version vulnerabilities, compatible versions: npm/PyPI facts. | Remote · HTTPLive check: ✓ handshake |
| VigilisGate AI-written tests: heal safe drift, refuse to hide real bugs, sign a verifiable receipt. | Local · stdio |
| Vim MCPConnect Claude Code to Vim/Neovim - query state, execute commands, search help, record macros. | Local · stdio |
| VinvVinv runs, tests, and finds issues in your services - with zero code changes. | Local · stdio |
| Virtual FilesystemPostgreSQL-backed virtual filesystem for agents: session isolation, shared stores, POSIX ops, RLS. | Local · stdio |
| Visily UI DesignUI design from prompts, screenshots, and URLs for AI coding agents and theme tokens. | Remote · HTTPLive check: sign-in required |
| vivacProvenance tree for coding agents: where you are, why, and what was already decided. | Local · stdio |