lemmaoracle MCP server
io.github.lemmaoracle/mcplemmaoraclestreamable-httpv0.0.17Scanned
Verifiable provenance for AI agents — ZK proofs over confidential documents, no plaintext exposure.
5 tools: 5 only read.
- Reads private data · 1
- Reads text others write · 5
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the lemmaoracle MCP server can do
The lemmaoracle MCP server is published by the GitHub account lemmaoracle. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (lemma_get_generator); 5 tools bring in text other people can write (lemma_query_verified_attributes, lemma_get_schema, lemma_get_circuit and 2 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 0.0.17.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Only reads 5Show 5 read-only tools
lemma_get_circuitRetrieve a zero-knowledge proof circuit by its circuitId via GET /v1/circuits/{circuitId}.Reads text others writeNo findings
Why it is in this group
- The name "lemma_get_circuit" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Retrieve a zero-knowledge proof circuit by its circuitId via GET /v1/circuits/{circuitId}. A circuit defines the constraints that proofs must satisfy and binds to a single schema. Returns CircuitMeta { circuitId, schema, description?, inputs?, verifier?: { type: 'onchain'|'offchain', address?, chainId? }, artifact?: { location: { type: 'ipfs'|'https', wasm, zkey } } }. Use this before lemma_submit_proof to confirm the circuit's schema, public inputs, and verifier configuration. Circuits are immutable; new variants get new circuitIds.
Annotations the server declares
- title: Lemma — get circuit
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
- destructiveHint: false
lemma_get_generatorRetrieve a Lemma document generator by generatorId via GET /v1/doc-generators/{generatorId}.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "lemma_get_generator" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "retrieve" and "document": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Retrieve a Lemma document generator by generatorId via GET /v1/doc-generators/{generatorId}. A generator describes how a class of source documents is produced (e.g., what fields a 'KYC-v2' issuer must populate). Returns GeneratorMeta { generatorId, schema, description?, language?, source?: { type: 'url', uri }, inputsSpec?, outputsSpec? }. Each generator is bound to one schema. Use this when onboarding a new issuer or auditing how an existing schema is being populated.
Annotations the server declares
- title: Lemma — get generator
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
- destructiveHint: false
lemma_get_proof_statusGet the verification status of a proof.Reads text others writeNo findings
Why it is in this group
- The name "lemma_get_proof_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get the verification status of a proof. NOTE: the v2 API does not yet expose a dedicated GET /v1/proofs/{id} endpoint, so this tool internally calls POST /v1/verified-attributes/query filtered by docHash (treating the verificationId returned from lemma_submit_proof as a docHash filter). Returns { status, circuitId, chainId, docHash } extracted from the matched item, or undefined if the verificationId is unknown. Status enum: received | verified | onchain-verified | rejected. Use the SDK's isVerified() helper (or check status === 'verified' || status === 'onchain-verified') to determine cryptographic validity.
Annotations the server declares
- title: Lemma — get proof status
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
- destructiveHint: false
lemma_get_schemaRetrieve a Lemma schema by its ID via GET /v1/schemas/{id}.Reads text others writeNo findings
Why it is in this group
- The name "lemma_get_schema" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Retrieve a Lemma schema by its ID via GET /v1/schemas/{id}. A schema declares how documents of a given type are interpreted and normalized. Returns SchemaMeta { id, description? } with additionalProperties open — implementations commonly include a `normalize` artifact (WASM that maps raw documents to canonical form) and its content hash. Use this when you need to interpret attribute keys returned by lemma_query_verified_attributes.
Annotations the server declares
- title: Lemma — get schema
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
- destructiveHint: false
lemma_query_verified_attributesQuery cryptographically verified attributes from Lemma.Reads text others writeNo findings
Why it is in this group
- The name "lemma_query_verified_attributes" says "query": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Query cryptographically verified attributes from Lemma. Use this as the primary tool for finding documents whose attributes match given conditions (e.g., "subject's birthYear lt 2008"). Returns { results: Array<{ docHash, schema, issuerId, subjectId, attributes, isVerified, proof?: { status, circuitId, chainId }, disclosure? }>, hasMore }. The MCP layer enriches each item with an `isVerified` flag derived from `proof.status` (true when status is 'verified' or 'onchain-verified'). Use lemma_get_proof_status to monitor a specific proof; use lemma_get_schema to interpret the keys returned in `attributes`.
Annotations the server declares
- title: Lemma — query verified attributes
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
- destructiveHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:07 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.0.17. Values in angle brackets are yours to fill in.
claude mcp add --transport http lemmaoracle https://mcp.lemma.workers.dev/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http lemmaoracle https://mcp.lemma.workers.dev/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__lemmaoracle__lemma_query_verified_attributes",
"mcp__lemmaoracle__lemma_get_schema",
"mcp__lemmaoracle__lemma_get_circuit",
"mcp__lemmaoracle__lemma_get_generator",
"mcp__lemmaoracle__lemma_get_proof_status"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lemmaoracle. Review it before you use it.
Capability tags behind 5 rules
- mcp__lemmaoracle__lemma_query_verified_attributes untrusted-input
- mcp__lemmaoracle__lemma_get_schema untrusted-input
- mcp__lemmaoracle__lemma_get_circuit untrusted-input
- mcp__lemmaoracle__lemma_get_generator private-data, untrusted-input
- mcp__lemmaoracle__lemma_get_proof_status untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.lemmaoracle/mcp/verify?hash=04986b6084dfe6841d401e91de689461db62a6d8180c3d002cb2a9aafb3fbdde" | jq -e '.changed == false'Pinned hash 04986b6084df, from Nov 20, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.lemmaoracle/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.lemmaoracle/mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:38 UTC.
lemmaoracle MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the lemmaoracle MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the lemmaoracle MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the lemmaoracle MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the lemmaoracle MCP server have?
- 5 tools: 5 read. lemma_query_verified_attributes, lemma_get_schema, lemma_get_circuit, lemma_get_generator and lemma_get_proof_status.
Does the lemmaoracle MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the lemmaoracle MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the lemmaoracle MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.