Vinktar MCP server
com.vinktar/mcpvinktar.comstreamable-httpv1.0.1Scanned
Error tracking for small teams and their coding agents.
31 tools: 9 can delete or cancel things, 1 do something that can't be undone, 5 change things and 16 only read.
- Reads private data · 5
- Reads text others write · 4
- Can send data out · 2
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
9 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Vinktar MCP server can do
The Vinktar MCP server is published by vinktar.com, a domain the MCP Registry verified. It has 31 tools. It can delete or cancel things (9 tools: create_board, define_event, delete_board, delete_panel and 5 more), do things that cannot be undone, such as sending, paying or publishing (create_alert) and create or change data (5 tools: add_panel, check_fix, run_sql, whats_changed and 1 more). 16 tools only read.
5 tools read private data (get_install_guide, get_issue, get_project_keys and 2 more); 4 tools bring in text other people can write (browse_events, get_issue, list_issue_occurrences and 1 more); 2 tools can send data out of your system (create_alert and update_issue). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 3 findings (long-description and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
31 tools
Deletes or cancels 9Claude Code: deny
create_boardCreate 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.No findings
Why it is in this group
- The name "create_board" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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 make with it: "launch" when one feature or release just shipped: is it used, by whom, does it convert, did it break anything; "conversion" when a funnel someone cares about: where people drop and which segment converts; "growth" when the business at a glance: new people, active people, conversions and money over time; "engagement" when how much and how often people use the product, and whether they come back; "revenue" when money: how much, from whom, and the path to paying; "acquisition" when where people come from and which channels bring the ones who sign up; "reliability" when what is breaking and whether it hurts the flows that matter; "custom" when none of the above: a board shaped around one specific question. The result is a plan for that kind, filled in with the project's own signup, activation, conversion and revenue events: follow it, dropping what the user did not ask about. If the request fits none, ask the user what the board is for before building. Pass `expiresInDays` for a board built for one launch, so it deletes itself afterwards instead of staying forever. Only do this when the user asked for a board or agreed to one.
Annotations the server declares
- title: Create board
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
define_eventDefine 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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 track() call, before any data arrives; and for existing events once you have read the code that sends them. It takes effect at once, labelled as written by an agent, and the team can correct it in Vinktar. get_setup_status then reports defined events that never arrive and sends missing a required property. Conventions (get_install_guide with section "conventions" has them all): new event names and property keys are snake_case, object then past-tense action (signed_up, report_exported); a description is one sentence of at most 100 characters and a longer one is refused; an event already shipping under another spelling is defined as it is sent, never renamed unasked. Do not overwrite a description the team wrote unless the user asks. Setup call: never counted.
Annotations the server declares
- title: Define event
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
delete_boardDelete a board with its panels.No findings
Why it is in this group
- The name "delete_board" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Delete board
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
delete_panelRemove a panel from its board.No findings
Why it is in this group
- The name "delete_panel" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Delete panel
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
set_project_notesWrite 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…No findings
Why it is in this group
- The name "set_project_notes" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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 codebase during setup, in plain sentences, up to 2,000 characters; they replace the current notes, so read them in get_schema first and keep what the team wrote. Every later agent reads them before the data. Setup call: never counted.
Annotations the server declares
- title: Set project notes
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
update_alertChange 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).No findings
Why it is in this group
- The name "update_alert" says "update": a word for a change.
- The input addresses people (input.recipients): what it sends cannot be taken back.
- The input takes a statement or command to run (input.sql), which can change anything it can reach.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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). Switching an alert off or deleting it is a person's, in Vinktar. Only change an alert when the user asked.
Annotations the server declares
- title: Update alert
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
update_boardRename a board, rewrite the line under its title, change when it deletes itself, or lay its panels out.No findings
Why it is in this group
- The name "update_board" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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 `rows` to set the layout outright, top to bottom, as rows of panel ids from get_board; panels you leave out keep their order after them. Or pass `arrange` to straighten the rows as they read now. Pass only what changes. Panels are changed with update_panel and delete_panel.
Annotations the server declares
- title: Update board
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
update_issueChange 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…Can send data outNo findings
Why it is in this group
- The name "update_issue" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "update_issue" says "update" and "issue": it writes something other people read.
Description, as the server wrote it 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 to a teammate. Only act on an issue when the user asked you to.
Annotations the server declares
- title: Update issue
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
update_panelChange a panel on a board: its title, how it draws, its number format or what it shows.No findings
Why it is in this group
- The name "update_panel" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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 same fields as add_panel. A changed panel is run and held to the same rules as add_panel before it is saved (structured types before SQL, one question per panel, the board's time range), and one that breaks them is refused with nothing changed.
Annotations the server declares
- title: Update panel
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Can't be undone 1Claude Code: ask
create_alertCreate 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, …Can send data outNo findings
Why it is in this group
- The name "create_alert" says "create": a word for a change.
- The input addresses people (input.recipients): what it sends cannot be taken back.
- The input takes a statement or command to run (input.sql), which can change anything it can reach.
What it can reach
- outboundThe input takes a destination (input.recipients): what the tool writes goes there.
Description, as the server wrote it 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 earlier or the trailing week) and who hears it (recipients among members, saved channels, the team by default). Each series is judged on its own and a series that fired stays quiet for one window. Examples: new issues = source errors, lifecycle first_seen, condition above, threshold 0. Users affected = source errors, measure unique_users, windowMinutes 60, above 100. Signups dropped = source events, event signup, condition changed, changeDirection down, changePercent 50, compare week. Orders stopped = source events, event order_placed, below 1. You cannot name a webhook, a URL or an outside address: a person adds those in Vinktar. Only create an alert when the user asked for one.
Annotations the server declares
- title: Create alert
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 5Claude Code: ask
add_panelAdd a panel to a board.1 finding
Why it is in this group
- The name "add_panel" says "add": a word for a change.
Findings
- Info
The description is 2,175 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...er they should read; to change the rows afterwards, use update_board with `rows`."
Description, as the server wrote it 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 (viewed pricing → started checkout → paid), with a breakdown for conversion per segment (per shop, per plan): always a funnel, never a query or trend lines per step. `retention` for whether people come back. `trends` for everything that counts or sums events: `chart` "scalar" for one number (revenue, installs, failed charges; several numbers are several scalar panels, never one wide table), "line" for a metric over time, "bar" to compare segments over time, "hbar" to rank them, "share" for parts of a whole, "heatmap" for when in the week; set `display.format` to "currency" for money and "percent" for a rate. A series can carry its own `breakdown`, so one panel shows signups by plan beside checkouts by country; reach for that before SQL. A table only when the rows themselves are the point (the operations or shops to look at), with at most four columns. `issues` for the top errors, `text` for a heading over a row of panels: a single "## Heading" line renders as a slim section title. `sql` only when none of those can show it (a ratio between two measures), with at most four columns, the board's range as `{from}`/`{to}` rather than now(), and `sqlReason` saying why. A funnel and retention count the project's identified users: if the people in the question are not them, say so in a text panel instead. The spec is exactly what query_trends, query_funnel, query_retention or run_sql just ran (same field names), so check the numbers with that tool first. The panel is run once before it is saved: one that fails or breaks these rules is refused and nothing is saved, so follow the message and call again. The board is a grid: a panel joins the last row when it is the same kind and there is room (numbers up to four to a row, charts two, a table or text on its own), and every row shares its width equally at one height. Add panels in the order they should read; to change the rows afterwards, use update_board with `rows`.
Annotations the server declares
- title: Add panel
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
check_fixAfter 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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 keeps running after this session. Read the result later with get_alert and the issueId. The result is never "fixed": it is recurred, no recurrence in N sessions, or not enough evidence.
Annotations the server declares
- title: Check fix
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
run_sqlRun 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…1 finding
Why it is in this group
- The name "run_sql" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "run_sql" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_sql" says "run": a word for a change.
Description, as the server wrote it 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 subset: WHERE, GROUP BY, HAVING, ORDER BY, LIMIT, DISTINCT, IN, LIKE and allowlisted functions (count, uniq, sum, avg, quantile, countIf, toStartOfDay…); no joins, subqueries, CTEs or INTERVAL, so filter time as `timestamp > now() - 86400 * 7`. Payload properties are `properties.<key>`, user traits `user.<key>`. Tenant scoping and plan retention are applied automatically. Call get_schema first for columns, functions and property names, and aggregate in SQL rather than paging through raw rows.
Annotations the server declares
- title: Run sql
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
start_projectBefore 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.No findings
Why it is in this group
- The name "start_project" says "start": a word for a change.
Description, as the server wrote it 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 the person should open: it signs them in, or makes them an account, and keeps the project with its data. Unclaimed, the project takes up to 10,000 events and is deleted with its data after 7 days. Only call it when the person has not signed in and the other tools ask for sign-in; once signed in, use list_projects and get_project_keys instead.
Annotations the server declares
- title: Start a project without an account
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whats_changedStart here.1 finding
Why it is in this group
- The description's first verb is "start": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "whats_changed" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.
Description, as the server wrote it 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, appeared or stopped, error volume, new, regressed and fastest-growing issues, and the releases that shipped, and what the project's alerts said. Each row names the tool to go deeper.
Annotations the server declares
- title: What changed
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 16Show 16 read-only tools
browse_eventsRaw events, newest first, under simple filters: event names, one user (distinctId), page search, property filters or a VinktarQL WHERE expression.Reads text others writeNo findings
Why it is in this group
- The name "browse_events" says "browse": a word for reading.
What it can reach
- untrusted-inputThe name "browse_events" says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it 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 that one event in full, every column and the whole payload. Windows longer than 30 days are narrowed to their last 30. For counts, use query_trends or run_sql instead of paging.
Annotations the server declares
- title: Browse events
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_alertRead alerts and what they said.No findings
Why it is in this group
- The name "get_alert" says "get": a word for reading.
Description, as the server wrote it 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 (awaiting_release, watching, recurred, no_recurrence, not_enough_evidence or stopped, with exposure and recurrences on the fix release). Neither lists every alert in the project, what fired in the last 24 hours, and the saved channels an alert can post to.
Annotations the server declares
- title: Get alert
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_boardRead a board: every panel computed over a window with the change against the previous period, as headline numbers.No findings
Why it is in this group
- The name "get_board" says "get": a word for reading.
Description, as the server wrote it 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 and delete_panel.
Annotations the server declares
- title: Get board
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_install_guideThe 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…Reads private dataNo findings
Why it is in this group
- The name "get_install_guide" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it 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 with get_setup_status, and the handover telling the person where each variable goes. Call this first when asked to install, set up or audit Vinktar, and follow it. It ends with Vinktar's conventions (event and property naming, descriptions, how an event changes, releases and environments, identifying users and connecting the browser visit to the server); pass section "conventions" for those alone before adding or changing a track() call in an app that is already set up. It answers before sign-in too, and then starts with where the person signs in from each app. Setup call: never counted.
Annotations the server declares
- title: Get install guide
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_issueEverything 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…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_issue" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
- untrusted-inputThe name "get_issue" says "get" and "issue": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
Description, as the server wrote it 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, each in-app frame linking to its file in the repository once the project's repository URL is set), breadcrumbs and request, and the product events that user sent in the 30 minutes before it.
Annotations the server declares
- title: Get issue
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_project_keysThe 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 …Reads private dataNo findings
Why it is in this group
- The name "get_project_keys" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "secret": it reads secrets.
Description, as the server wrote it 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, with where a person creates one. The secret is never returned: tell the person to add it as a CI secret. Needs a read and write connection. Setup call: never counted.
Annotations the server declares
- title: Get project keys
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_schemaWhat 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…Reads private dataNo findings
Why it is in this group
- The name "get_schema" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "sql": it reads databases.
Description, as the server wrote it 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_sql) accepts. Call before any query so names are real. Pass `event` to see every property of one event, or `propertyKey` to see that property's most common values, which is how you find the exact spelling of one before filtering on it.
Annotations the server declares
- title: Get schema
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_setup_statusCheck 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…No findings
Why it is in this group
- The name "get_setup_status" says "get": a word for reading.
Description, as the server wrote it 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 gap comes with the next step. Call it after installing, and again after each fix, until nothing is left to do. Setup call: never counted against the agent allowance.
Annotations the server declares
- title: Get setup status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_start_statusWhether events and errors have arrived for a project started with start_project, by its write key, and whether the person has claimed it yet.No findings
Why it is in this group
- The name "get_start_status" says "get": a word for reading.
Description, as the server wrote it 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 answer only after sign-in, through get_setup_status.
Annotations the server declares
- title: Check a started project
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_boardsThe boards whose panels read from a project, or from any of several with `projects`.No findings
Why it is in this group
- The name "list_boards" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List boards
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_issue_occurrencesRecent individual occurrences of one issue, newest first: when, which user and session, release, environment, page, browser and OS.Reads text others writeNo findings
Why it is in this group
- The name "list_issue_occurrences" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "list_issue_occurrences" says "list" and "issue": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
Description, as the server wrote it 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 browse_events.
Annotations the server declares
- title: List issue occurrences
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_issuesError-tracking issues (errors grouped by fingerprint) for a project, or across several with `projects`, with occurrences and affected users inside the window.Reads text others writeNo findings
Why it is in this group
- The name "list_issues" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "list_issues" says "list" and "issue": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
Description, as the server wrote it 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 14 days. Follow up with get_issue for the stack trace.
Annotations the server declares
- title: List issues
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_projectsList 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.No findings
Why it is in this group
- The name "list_projects" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List projects
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
query_funnelConversion through an ordered sequence of events (e.g.No findings
Why it is in this group
- The name "query_funnel" says "query": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Query funnel
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
query_retentionCohort 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.Reads private dataNo findings
Why it is in this group
- The name "query_retention" says "query": a word for reading.
What it can reach
- private-dataThe description's first sentence says "table": it reads databases.
Description, as the server wrote it 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".
Annotations the server declares
- title: Query retention
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
query_trendsMetrics 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…No findings
Why it is in this group
- The name "query_trends" says "query": a word for reading.
Description, as the server wrote it 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 workhorse for "how many / how much / is it growing" questions. interval "total" returns one de-duplicated number per series for the whole window.
Annotations the server declares
- title: Query trends
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
40 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.
- Reads private data5
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__vinktar__create_alert",
"mcp__vinktar__update_issue"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:50 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 15
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.vinktar.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://mcp.vinktar.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 15 tools that change things (9 destructive, 1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.vinktar.com/mcp: tools/list returned 31 tools to an anonymous client, including create_board (destructive), define_event (destructive), delete_board (destructive), delete_panel (destructive), set_project_notes (destructive) and 10 more
Findings
Matches of fixed checks, with the text they matched.
- Warnrun_sql
The server marks "run_sql" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_sql" says "run": a word for a change.
- Warnwhats_changed
The server marks "whats_changed" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.
- Infoadd_panel
The description is 2,175 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...er they should read; to change the rows afterwards, use update_board with `rows`."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:check_fixChanges thingsdescription
- Changed:create_alertCan't be undonedescriptioninputSchema
- Changed:get_alertOnly readsdescription
- Changed:get_install_guideOnly readsinputSchema
- Changed:update_alertDeletes or cancelsdescriptioninputSchema
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http vinktar https://mcp.vinktar.com/mcpclaude mcp add --transport http vinktar https://mcp.vinktar.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__vinktar__browse_events",
"mcp__vinktar__get_alert",
"mcp__vinktar__get_board",
"mcp__vinktar__get_install_guide",
"mcp__vinktar__get_issue",
"mcp__vinktar__get_project_keys",
"mcp__vinktar__get_schema",
"mcp__vinktar__get_setup_status",
"mcp__vinktar__list_boards",
"mcp__vinktar__list_issue_occurrences",
"mcp__vinktar__list_issues",
"mcp__vinktar__list_projects",
"mcp__vinktar__query_funnel",
"mcp__vinktar__query_retention",
"mcp__vinktar__query_trends",
"mcp__vinktar__get_start_status"
],
"ask": [
"mcp__vinktar__add_panel",
"mcp__vinktar__check_fix",
"mcp__vinktar__create_alert",
"mcp__vinktar__run_sql",
"mcp__vinktar__whats_changed",
"mcp__vinktar__start_project"
],
"deny": [
"mcp__vinktar__create_board",
"mcp__vinktar__define_event",
"mcp__vinktar__delete_board",
"mcp__vinktar__delete_panel",
"mcp__vinktar__set_project_notes",
"mcp__vinktar__update_alert",
"mcp__vinktar__update_board",
"mcp__vinktar__update_issue",
"mcp__vinktar__update_panel"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vinktar. Review it before you use it.
Capability tags behind 10 rules
- mcp__vinktar__browse_events untrusted-input
- mcp__vinktar__create_alert outbound
- mcp__vinktar__get_install_guide private-data
- mcp__vinktar__get_issue private-data, untrusted-input
- mcp__vinktar__get_project_keys private-data
- mcp__vinktar__get_schema private-data
- mcp__vinktar__list_issue_occurrences untrusted-input
- mcp__vinktar__list_issues untrusted-input
- mcp__vinktar__query_retention private-data
- mcp__vinktar__update_issue outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.vinktar/mcp/verify?hash=3db4edd4cd18542ff9f1de4e0eb51466a828aaf28a95baf09ee9656a755eb420" | jq -e '.changed == false'Pinned hash 3db4edd4cd18, from Nov 11, 2026, 05:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.vinktar/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.vinktar/mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:10 UTC.
Vinktar MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Vinktar MCP server safe?
- No scan can promise that. What its definitions show: 31 tools, 15 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Vinktar MCP server delete data?
- Yes. 9 tools can delete, cancel or revoke something: create_board, define_event, delete_board, delete_panel, set_project_notes, update_alert and 3 more.
Can the Vinktar MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: create_alert.
What tools does the Vinktar MCP server have?
- 31 tools: 9 destructive, 1 irreversible, 5 write, 16 read. create_board, define_event, delete_board, delete_panel, set_project_notes, update_alert, update_board, update_issue and 23 more.
Does the Vinktar MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Vinktar MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_alert and update_issue.
Has the Vinktar MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.