Remote MCP · Endpoint

Vinktar MCP server

No. Vinktar answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.vinktar.com/mcp

The last check completed an MCP handshake.

Registry name
com.vinktar/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
323 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Error tracking for small teams and their coding agents.
Website
https://vinktar.com/docs/mcp
Repository
https://github.com/vinktarhq/agent
Listing
From the official MCP registry (active).
Recent checks of Vinktar
CheckedResultHandshake
2 hours agoHandshake completed323 ms
2 days agoHandshake completed327 ms
4 days agoHandshake completed324 ms
6 days agoHandshake completed343 ms
8 days agoHandshake completed325 ms
10 days agoHandshake completed332 ms
12 days agoHandshake completed321 ms
14 days agoHandshake completed330 ms
15 days agoCredentials required—
16 days agoCredentials required—
18 days agoCredentials required—
20 days agoCredentials required—
22 days agoCredentials required—
23 days agoCredentials required—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Vinktar and makes no claim about it beyond what these checks measured.