Vinktar is an MCP server with 31 tools an agent can call, among them add_panel, browse_events, check_fix. It answers at https://mcp.vinktar.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.
Product analytics and error tracking your coding agent can use.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
add_panel | Add a panel to a board. Each panel answers one question and reads at a glance: a number, a line or a bar. Build it from the structured types; `sql` is the last resort. Choose in this order: `funnel` for conversion through ordered events (vi |
browse_events | Raw events, newest first, under simple filters: event names, one user (distinctId), page search, property filters or a VinktarQL WHERE expression. Use it to see what one user did, or to inspect real payloads. Pass `eventId` instead to get t Inputs: project, projects, eventId, names, distinctId, search |
check_fix | After a fix for an issue ships, start a server-side check of whether it comes back: occurrences on the fix release (or the next release seen) and later, against how many sessions reached that release, over a horizon of up to 14 days. It kee Inputs: issueId, release, environment, horizonDays, minExposure |
create_alert | Create an alert: a query (source events, errors or sql; measure count or unique_users; filters; an optional groupBy; a window in minutes), a condition (above or below a threshold, or changed by a percent against the window before, a week ea Inputs: project, projects, name, source, measure, event |
create_board | Create an empty board in the workspace, to leave the user a view of what you found; fill it with add_panel, where each panel says which projects it reads. First decide what kind of board the request is, from the decision the user wants to m Inputs: name, kind, project, projects, description, expiresInDays |
define_event | Define an event in the project's tracking plan: what it means, its role, the properties it carries (type, unit, whether every send must include it, an example) and where the code sends it. Call it in the same step as adding or changing a tr Inputs: project, event, description, role, code_location, properties |
delete_board | Delete a board with its panels. Only when the user asked for it, or agreed when you proposed it; name the board before you do. A person can restore it in Vinktar from the boards page for 30 days. Inputs: dashboardId |
delete_panel | Remove a panel from its board. Only when the user asked for it, or agreed when you proposed it; say which panel before you do. The panel id is in get_board. A person can restore it in Vinktar from the boards page for 30 days. Inputs: panelId |
get_alert | Read alerts and what they said. Pass alertId for one alert: its query and condition, whether it is on or snoozed, what its last check read per series, who hears it and what it said recently. issueId gives that issue's latest fix check (awai Inputs: alertId, issueId, project |
get_board | Read a board: every panel computed over a window with the change against the previous period, as headline numbers. The quickest way to answer "how are we doing" in the terms the team already tracks. Each panel shows its id, for update_panel Inputs: dashboardId, last, from, to |
get_install_guide | The step-by-step guide for setting Vinktar up in the app you are working in: which SDK fits the stack (with current versions), the recommended file layout and environment variables, defining the tracking plan as you add events, proving it w Inputs: section |
get_issue | Everything needed to debug one error issue: what it is, its status and history, how often and for whom it happens in the window (by release, environment, browser, URL, tag), the latest occurrence's stack trace (source-mapped when available, Inputs: issueId, last, from, to |
get_project_keys | The keys installing Vinktar needs: the project's public write key (VINKTAR_KEY) with the ingest host, the Sentry-compatible DSN and the Bugsnag-compatible endpoints, and whether a source-map upload key (VINKTAR_CLI_KEY, a secret) exists, wi Inputs: project |
get_schema | What a project tracks (or several, with `projects`, each under its own heading): event names with their volume over the last 30 days, the payload properties each event carries, user trait keys, and the columns and functions VinktarQL (run_s Inputs: project, projects, event, propertyKey, propertyScope, search |
get_setup_status | Check a project's Vinktar install from the data that actually arrived: events and errors received, users identified, releases and environments tagged, source maps for the latest release, items the SDK dropped, and key events described. Each Inputs: project |
get_start_status | Whether events and errors have arrived for a project started with start_project, by its write key, and whether the person has claimed it yet. Call it after installing the SDK and sending a first event. Projects someone already claimed answe Inputs: key |
list_boards | The boards whose panels read from a project, or from any of several with `projects`. A board shows what the team already decided matters; read one with get_board. Inputs: project, projects |
list_issue_occurrences | Recent individual occurrences of one issue, newest first: when, which user and session, release, environment, page, browser and OS. Use it to spot a pattern (one browser, one release, one customer) or to pick a user or session to follow in Inputs: issueId, limit, cursor |
list_issues | Error-tracking issues (errors grouped by fingerprint) for a project, or across several with `projects`, with occurrences and affected users inside the window. Default: open issues (unresolved + regressed) sorted by occurrences over the last Inputs: project, projects, status, level, environment, release |
list_projects | List the Vinktar projects this connection can read (a project is one app or site sending events and errors), with the workspace plan and what this connection is allowed to do. Call this first when you do not know the project handle. |
query_funnel | Conversion through an ordered sequence of events (e.g. view_pricing → start_checkout → purchase): how many entered, how many reached each step, where they dropped, how long converting took, optionally by segment. |
query_retention | Cohort retention: users who did targetEvent in a period form a cohort, and the table shows what share of each cohort did returningEvent in each later period. Use it for "do people come back" and "did retention improve after the change". Inputs: project, projects, targetEvent, returningEvent, period, periods |
query_trends | Metrics over time: event counts, unique users or sessions, the sum, average or p95 of a numeric property, optionally split by a property (one breakdown for every series, or each series by its own) and compared to the previous period. The wo |
run_sql | Run a read-only VinktarQL SELECT over the project's `events` table, for anything query_trends, query_funnel and query_retention cannot express; start with those, since what they run is what a board panel should be. A ClickHouse-flavoured su Inputs: project, projects, query, limit, cursor |
set_project_notes | Write the project's notes for AI agents: what the product does and for whom, the flows that matter (signup, activation, the paid action), what counts as an active user, and anything that makes the data easy to misread. Write them from the c Inputs: project, notes |
start_project | Before the person has signed in to Vinktar: start a project for their app now, so setup can run and data can arrive before anyone makes an account. Returns the project's write key (public, safe in browser code) and a claim link that only th Inputs: name, platform |
update_alert | Change an alert from get_alert: any part of its query, condition, timing, recipients (workspace members) and channels (saved ids or "#name" in the connected Slack). Or hold its news with snoozeMinutes (0 ends a snooze; a week at most). Swit Inputs: alertId, snoozeMinutes, name, source, measure, event |
update_board | Rename a board, rewrite the line under its title, change when it deletes itself, or lay its panels out. A board is a grid: every row spans the full width, its panels share it (one to four) at one height, equally unless you give widths. Pass Inputs: dashboardId, name, description, expiresInDays, rows, arrange |
update_issue | Change an error issue's status or assignee: resolve it (optionally in the release that ships the fix, or in the next release when it has not shipped yet, so a later occurrence reopens it as a regression), ignore it, reopen it, or assign it Inputs: issueId, status, resolvedInRelease, resolvedInNextRelease, environment, assignee |
update_panel | Change a panel on a board: its title, how it draws, its number format or what it shows. Pass only what changes; the rest stays as it is. The panel id is in get_board. To turn it into another type, pass `type` with the full spec for it, the |
whats_changed | Start here. One project's window, or several pooled with `projects` (every row then names its project), compared with the one before it, across analytics and errors: traffic (events, active users, sessions), the events that rose, fell, appe Inputs: project, projects, last |
Every block below points at https://mcp.vinktar.com/mcp. Pick your client and copy.
claude mcp add --transport http vinktar https://mcp.vinktar.com/mcp
{
"mcpServers": {
"vinktar": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.vinktar.com/mcp"]
}
}
}{
"mcpServers": {
"vinktar": {
"url": "https://mcp.vinktar.com/mcp"
}
}
}{
"servers": {
"vinktar": {
"type": "http",
"url": "https://mcp.vinktar.com/mcp"
}
}
}{
"context_servers": {
"vinktar": {
"url": "https://mcp.vinktar.com/mcp"
}
}
}{
"mcpServers": {
"vinktar": {
"serverUrl": "https://mcp.vinktar.com/mcp"
}
}
}{
"mcpServers": {
"vinktar": {
"url": "https://mcp.vinktar.com/mcp"
}
}
}name: Vinktar
version: 0.0.1
schema: v1
mcpServers:
- name: Vinktar
type: streamable-http
url: https://mcp.vinktar.com/mcp{
"mcpServers": {
"vinktar": {
"httpUrl": "https://mcp.vinktar.com/mcp"
}
}
}{
"mcpServers": {
"vinktar": {
"type": "http",
"url": "https://mcp.vinktar.com/mcp"
}
}
}{
"mcpServers": {
"vinktar": {
"url": "https://mcp.vinktar.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.vinktar.com%2Fmcp&type=streamable_http&id=vinktar&name=Vinktar
It answered our last check on 15 November 2026 in 123 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by vinktar.com and served from mcp.vinktar.com, the vendor's own domain: https://mcp.vinktar.com/mcp.
31, as returned by the server's own tools/list on 18 November 2026: add_panel, browse_events, check_fix, create_alert, create_board, define_event, delete_board, delete_panel, and 23 more.
It answered our last check on 15 November 2026 in 123 ms. Over 4 checks since 29 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.vinktar.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.vinktar. Endpoint host: mcp.vinktar.com. ARD identifier: urn:air:com.vinktar:mcp:mcp.
First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.