Vinktar

Name: Vinktar
Author: com.vinktar

MCP serverMCP

Error tracking for small teams and their coding agents.

by com.vinktarrepository ↗homepage ↗v1.0.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"vinktar","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability (some checks stopped at authentication)35/35 checks ok

Some successful checks reached the service and some stopped at an authentication response; figures combine both.

Tools observed via MCP handshake

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
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
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. Pass
create_watch — Watch something and tell the workspace's owners and admins when it happens. Subjects: issues (the whole error stream: new_issue, regression, spike, occurrences,
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)
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 Vinkta
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 p
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"
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 e
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, browse
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 endpo
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 eac
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 ma
get_watch — Read watches and what they said. Pass watchId for one watch (a fix watch reports its state: awaiting_release, watching, recurred, no_recurrence, not_enough_evid
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_boar
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 (on
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. D
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
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 dropp
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. Us
query_trends — Metrics over time: event counts, unique users or sessions, the sum, average or p95 of a numeric property, optionally split by one breakdown and compared to the
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
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 acti
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 p
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 l
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_
watch_issue — 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
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 er

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.vinktar/mcp

first seen 10 d ago · fetched 22 h agoopen ↗

Field history (10 recent events)

22 h ago · declared · summary → "Error tracking for small teams and their coding agents."
22 h ago · declared · description → "Error tracking for small teams and their coding agents."
22 h ago · declared · version → "1.0.1"
10 d ago · declared · homepageUrl → "https://vinktar.com/docs/mcp"
10 d ago · declared · repoUrl → "https://github.com/vinktarhq/agent"
10 d ago · declared · summary → "Product analytics and error tracking your coding agent can use."
10 d ago · declared · protocols → ["mcp"]
10 d ago · declared · version → "1.0.0"
10 d ago · declared · description → "Product analytics and error tracking your coding agent can use."
10 d ago · declared · publisherName → "com.vinktar"

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	36 ms	server vinktar 1.0.0 · protocol 2025-06-18 · 28 tools
13 h ago	mcp initialize	ok	200	61 ms	server vinktar 1.0.0 · protocol 2025-06-18 · 28 tools
19 h ago	mcp initialize	ok	200	62 ms	server vinktar 1.0.0 · protocol 2025-06-18 · 28 tools
26 h ago	mcp initialize	ok	200	168 ms	server vinktar 1.0.0 · protocol 2025-06-18 · 28 tools
32 h ago	mcp initialize	ok	200	35 ms	server vinktar 1.0.0 · protocol 2025-06-18 · 28 tools
2 d ago	mcp initialize	ok	200	37 ms	server vinktar 1.0.0 · protocol 2025-06-18 · 28 tools
2 d ago	mcp initialize	ok	200	37 ms	server vinktar 1.0.0 · protocol 2025-06-18 · 28 tools
2 d ago	mcp initialize	ok	200	33 ms	server vinktar 1.0.0 · protocol 2025-06-18 · 28 tools
3 d ago	mcp initialize	ok	200	36 ms	server vinktar 1.0.0 · protocol 2025-06-18 · 28 tools
3 d ago	mcp initialize	ok	401	60 ms	auth required

Vinktar

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from