MCP servercom.vinktar/mcp
Error tracking for small teams and their coding agents.
Overview
Score?
UNRATED 0.728
of what a free look can see, on 22 looks
Looks
32
last 19 hr ago
Tools
31
changed 6 days ago
More info
URL
mcp.vinktar.com/mcp
streamable-http
Says it is
vinktar 1.0.0
protocol 2025-06-18
In the record since
49 days ago
Among servers32,724 with a card
0median 0.546 · this server 0.728 · highest on record 0.8351
Toolsfrom sha256:611f4e7334…b2973c · +0 −0 6 days ago
| Tool | Schema |
|---|---|
| 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 th |
input · no output |
| 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, |
input · no output |
| 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 r |
input · no output |
| 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, |
input · no output |
| 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 |
input · no output |
| 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 s |
input · no output |
| 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 pa |
input · no output |
| 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 |
input · no output |
| 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 |
input · no output |
| 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 te |
input · no output |
| 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 |
input · no output |
| 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 la |
input · no output |
| 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 |
input · no output |
| 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, use |
input · no output |
| 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 re |
input · no output |
| 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 s |
input · no output |
| 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. |
input · no output |
| 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 relea |
input · no output |
| 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 |
input · no output |
| 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 |
input · no output |
| 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 convert |
input · no output |
| 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 |
input · no output |
| 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 se |
input · no output |
| 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 ru |
input · no output |
| 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 anythin |
input · no output |
| 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 |
input · no output |
| 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 new |
input · no output |
| 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 |
input · no output |
| 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 reop |
input · no output |
| 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 in |
input · no output |
| 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 (event |
input · no output |
Verify it yourself
npx teppi-check https://mcp.vinktar.com/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M3RGDM2NJT8MZ0Q9Y222PCT4