mcp-vinktar-com-mcp
https://mcp.vinktar.com/mcp
active Production-safe Score 94/100 http no auth
At a glance
| Endpoint | https://mcp.vinktar.com/mcp |
|---|---|
| Source | https://github.com/vinktarhq/agent |
| Transport | http |
| Tools | 31 |
| Auth | none |
| First seen | 2026-10-07 22:44:48 |
| Last checked | 2026-11-17 21:53:23 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 390 / 617 ms |
| Last successful check | 2026-11-17 21:53:23 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (31)
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 typesbrowse_events— Raw events, newest first, under simple filters: event names, one user (distinctId), page search, property filters or a VinktarQL WHERE exprecheck_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 seencreate_alert— Create an alert: a query (source events, errors or sql; measure count or unique_users; filters; an optional groupBy; a window in minutes), acreate_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 projdefine_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 incldelete_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 candelete_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 idget_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 pget_board— Read a board: every panel computed over a window with the change against the previous period, as headline numbers. The quickest way to answeget_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 recommendget_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,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 Bugsget_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 paget_setup_status— Check a project's Vinktar install from the data that actually arrived: events and errors received, users identified, releases and environmenlist_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; relist_issue_occurrences— Recent individual occurrences of one issue, newest first: when, which user and session, release, environment, page, browser and OS. Use it tlist_issues— Error-tracking issues (errors grouped by fingerprint) for a project, or across several with `projects`, with occurrences and affected userslist_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 whaquery_funnel— Conversion through an ordered sequence of events (e.g. view_pricing → start_checkout → purchase): how many entered, how many reached each stquery_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 equery_trends— Metrics over time: event counts, unique users or sessions, the sum, average or p95 of a numeric property, optionally split by a property (onrun_sql— Run a read-only VinktarQL SELECT over the project's `events` table, for anything query_trends, query_funnel and query_retention cannot expreset_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), whupdate_alert— Change an alert from get_alert: any part of its query, condition, timing, recipients (workspace members) and channels (saved ids or "#name"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 tupdate_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 notupdate_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. 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, acrstart_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 aget_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
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:53:23 | ✓ | ✓ | 299 ms | 94 | active |
| 2026-11-17 21:38:19 | ✓ | ✓ | 482 ms | 90 | active |
| 2026-11-17 21:22:59 | ✓ | ✓ | 458 ms | 90 | active |
| 2026-11-17 21:07:44 | ✓ | ✓ | 425 ms | 90 | active |
| 2026-11-17 20:52:41 | ✓ | ✓ | 461 ms | 90 | active |
| 2026-11-17 20:37:38 | ✓ | ✓ | 302 ms | 90 | active |
| 2026-11-17 20:22:30 | ✓ | ✓ | 385 ms | 90 | active |
| 2026-11-17 20:07:26 | ✓ | ✓ | 329 ms | 90 | active |
| 2026-11-17 19:51:39 | ✓ | ✓ | 309 ms | 90 | active |
| 2026-11-17 19:36:32 | ✓ | ✓ | 357 ms | 90 | active |
| 2026-11-17 19:21:20 | ✓ | ✓ | 451 ms | 90 | active |
| 2026-11-17 19:06:06 | ✓ | ✓ | 297 ms | 94 | active |
| 2026-11-17 18:50:55 | ✓ | ✓ | 297 ms | 94 | active |
| 2026-11-17 18:35:45 | ✓ | ✓ | 316 ms | 90 | active |
| 2026-11-17 18:20:44 | ✓ | ✓ | 454 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.vinktar.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-vinktar-com-mcp # JSON