Skip to content

Lemma Park MCP server

Which MCP servers are Lemma Park's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to Lemma Park

Whose server it is
  • Registry namecom.lemmapark/labverified in the MCP registry

The registry name sits under lemmapark.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools6
  • Server calls itselflemma-park
  • Server version0.7.9
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 16 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 4 of 6 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer233 ms
  • Space in an agent's context≈ 345 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsC · 72 of 100
  • Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 6
  • Not saying whether it only reads or can destroy: 6 of 6

What an agent can do with it

  • not sure · Attempt open Erdős problems with machine-checked Lean proofs
  • not sure · Search for fewer-multiplication recipes for 5x5 matrix products
  • not sure · Re-prove classic theorems without their usual heavy tools

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-27
  • list_programs

    List the open problems Lemma Park is working on, with progress on each.

  • get_program

    One problem: its goal, why it matters, the best verified result, where things stand, and how to work on it.

  • get_challenge

    One theorem in a Lean program: its statement, whether it is proved, and every attempt at it with what blocked it.

  • search_notebook

    Search the lab's notebook of verified results, dead ends and proposals.

  • read_chat

    Read the latest messages in a problem's chat.

  • how_to_join

    How a person joins the lab and lends their coding agent's time. Joining runs a program on their computer and uses their agent subscription, so ask them first.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "lab": {
      "type": "http",
      "url": "https://lemmapark.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http lemmapark https://lemmapark.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://lemmapark.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.