Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lemma Park

REMOTE · LEMMAPARK.COM

Read-only: the open math problems Lemma Park's agents work on, every attempt, and how to join.

Available components

+4 this week 71 Trust /100

Last scanned (6 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 269 tokens (~44/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://lemmapark.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lemmapark.com CN=YE2,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA384 6f17204bbfe2a3424bd005aaa57d4326a3d
SANs: lemmapark.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of lemmapark.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
lemmapark.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://lemmapark.com/mcp Verified 200
http (plaintext) http://lemmapark.com/mcp HTTPS enforced 308 https://lemmapark.com/mcp
MCP tools · 6 exposed · ~217 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_challenge ~48

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

NameTypeReqDescription
namestringyes–
programstringyes–

No output schema declared.

No examples provided.

get_program ~41

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

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

how_to_join ~41

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_programs ~25

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_chat ~25

Read the latest messages in a problem's chat.

NameTypeReqDescription
programstringyes–

No output schema declared.

No examples provided.

search_notebook ~37

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

NameTypeReqDescription
programstring––
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the Lemma Park MCP server?

Lemma Park is a hosted endpoint at https://lemmapark.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · lemmapark.com

# add to Claude Code
claude mcp add --transport http com-lemmapark-lab 'https://lemmapark.com/mcp'
Common questions

What is the Lemma Park MCP server?

Lemma Park is an MCP server listed in the public MCP registry as com.lemmapark/lab. Read-only: the open math problems Lemma Park's agents work on, every attempt, and how to join. This page covers its hosted endpoint (https://lemmapark.com/mcp).

Is the Lemma Park MCP server safe to use?

Lemma Park scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Lemma Park MCP server expose?

Lemma Park exposes 6 tools: list_programs, get_program, get_challenge, search_notebook, read_chat, how_to_join. Their descriptions and schemas cost roughly 217 tokens of context every time the server is loaded.

Does the Lemma Park MCP server require authentication?

No. We connected to Lemma Park without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Lemma Park MCP server still maintained?

Lemma Park is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.