Home / MCP registry index / com.vinktar/mcp
Vinktar
com.vinktar/mcp in the official MCP registry.
Endpoint https://mcp.vinktar.com/mcp. Source: github.com/vinktarhq/agent.
The registry describes it as: Error tracking for small teams and their coding agents.
We read its 31 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
add_panel browse_events check_fix create_alert create_board define_event delete_board delete_panel get_alert get_board get_install_guide get_issue get_project_keys get_schema get_setup_status list_boards list_issue_occurrences list_issues list_projects query_funnel query_retention query_trends run_sql set_project_notes update_alert update_board update_issue update_panel whats_changed start_project get_start_status
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-vinktar-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.