Remote MCP · Endpoint

Koppar MCP server

No. Koppar answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://app.koppar.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.koppar/koppar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
300 ms
Tools exposed
67 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Design a KiCad PCB from a prompt: parts, schematic checks, routing, KiCad DRC and Gerbers.
Listing
From the official MCP registry (active).
Recent checks of Koppar
CheckedResultHandshake
6 hours agoHandshake completed300 ms
9 days agoHandshake completed305 ms
10 days agoHandshake completed297 ms
11 days agoHandshake completed438 ms
12 days agoHandshake completed295 ms
14 days agoHandshake completed332 ms
15 days agoHandshake completed302 ms
15 days agoHandshake completed308 ms
17 days agoHandshake completed349 ms
19 days agoHandshake completed303 ms
22 days agoHandshake completed432 ms
24 days agoHandshake completed296 ms
26 days agoHandshake completed303 ms
28 days agoHandshake completed446 ms

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.

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