Vinktar
Error tracking for small teams and their coding agents
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: analyze campaign performance.Similar tools
Listed for the same task: analyze campaign performanceReviews
No review yet. Used Vinktar? Be the first to help others choose.What it does
Vinktar is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to 2 capabilities: data analysis and debugging. That makes it a candidate for tasks such as analyze campaign performance or analyze customer feedback.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://mcp.vinktar.com/mcpstreamable-http
In Claude Code: claude mcp add --transport http vinktar https://mcp.vinktar.com/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"vinktar": {
"url": "https://mcp.vinktar.com/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE Vinktar answered an MCP connection on 15 Nov 2026 and introduced itself as vinktar 1.0.0 (MCP protocol 2025-06-18).
31 tools offered to AI assistants
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 (vibrowse_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 tcheck_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 keecreate_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 eacreate_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 mdefine_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 trdelete_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.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.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 (awaiget_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_panelget_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 wget_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,
Show 19 more
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, wiget_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_sget_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. Eachlist_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.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 inlist_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 lastlist_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".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 worun_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 suset_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 cupdate_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). Switupdate_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. Passupdate_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 itupdate_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, thewhats_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, appestart_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 thget_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
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://mcp.vinktar.com/mcp | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Version | 1.0.1 | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Website | https://vinktar.com/docs/mcp | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Repository | https://github.com/vinktarhq/agent | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 20h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 20h ago |
Change history
- VERSION07 Oct 20261.0.0 → 1.0.1
- NEW29 Sept 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Vinktar still online?
Free alerts · no account▲ 0Do you run Vinktar? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Vinktar
How do I connect Vinktar?
Use the hosted endpoint https://mcp.vinktar.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Vinktar offer?
When Electra Index connected on 15 Nov 2026, it listed 31 tools: add_panel, browse_events, check_fix, create_alert, create_board, define_event, delete_board, delete_panel and more. The full list is in "Live check" above.
Is Vinktar online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.
What can I use Vinktar for?
Based on its description, it is most relevant to: analyze campaign performance, analyze customer feedback, analyze financial documents, analyze patents.