MCP servers observed by Lowdown
ai.koppar/koppar MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 67 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-15 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.koppar/koppar
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.koppar/koppar?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 3 compared days.
- 2026-11-15: input or output schemas changed, descriptions changed, tool names changed; tool count 66 → 67
- 2026-11-12: input or output schemas changed, descriptions changed
What tools does it list?
67 tools on 2026-11-18:
add_copperadd_custom_footprintadd_project_filesanneal_placeauto_placebridge_islandscheck_net_rulescheck_physicschoose_bom_partcleanup_boardconsolidate_bom_basiccouple_pairscreate_custom_symbolcreate_designdelete_designdiagnose_open_netsedit_circuitexport_stepfill_zonesfinish_boardget_board_contextget_board_infoget_board_jobget_board_statusget_bomget_designget_downloadsget_fab_statusget_kicad_symbolget_order_priceget_review_packetget_workflow_guideimport_kicad_projectleave_feedbacklist_board_revisionslist_designslist_order_providersplace_footprintspolish_viasprune_viasread_design_filerender_boardrepair_boardrestore_board_revisionrestore_designripup_routingroute_boardrun_drcsave_dossiersearch_kicad_footprintsearch_kicad_symbolsend_order_to_providerset_board_outlineset_design_rulesset_keepoutsset_silkscreenset_zonesstamp_silkscreenstart_boardstop_board_jobsubmit_circuitswap_footprinttidy_coppertie_rail_padsupdate_board_from_netlistupload_boardwiden_nets
MCP Registry declaration
- Registry name:
ai.koppar/koppar - Declared version: 1.0.1
- Status: active
- Declared hosts:
app.koppar.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:ai.koppar/koppar", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.koppar/koppar?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).