Skip to content
Agentmart
Submit a tool

lemmaoracle/mcp

Verifiable provenance for AI agents — ZK proofs over confidential documents, no plaintext exposure.

Connector by lemmaoracle · GitHub account verified by the MCP Registry

IndexedApache-2.0Local (stdio)Remote (HTTP)★ 1
Write a review

Install

Works with Claude Code, VS Code, Codex, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/lemmaoracle-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoint

  • https://mcp.lemma.workers.dev/mcp Remote (HTTP)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Verifiable provenance for AI agents — ZK proofs over confidential documents, no plaintext exposure.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
5 read · 0 write · 0 deleteRead-only
Secrets
2 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 5

From the running server's own tool list (tools/list) on Oct 25, 2026.

Read 5 · Look things up without changing anything.

  • lemma_get_circuit
  • lemma_get_generator
  • lemma_get_proof_status
  • lemma_get_schema
  • lemma_query_verified_attributes

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • Authorization
  • LEMMA_API_KEY

Other settings (environment variables or headers).

  • LEMMA_API_BASE

Network hosts it talks to 1

  • mcp.lemma.workers.dev · found in remote endpoint, install command

Tools (5)

As the server listed them on Oct 25, 2026. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • lemma_get_circuitLemma — get circuitread-only

    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.

  • lemma_get_generatorLemma — get generatorread-only

    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.

  • lemma_get_proof_statusLemma — get proof statusread-only

    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 cryptog…

  • lemma_get_schemaLemma — get schemaread-only

    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.

  • lemma_query_verified_attributesLemma — query verified attributesread-only

    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 `att…

Signals

Stars
1
Forks
2
Open issues
4
Weekly downloads
14
Last commit (this folder)
Oct 14, 2026 (15 days ago)
Last release
May 18, 2026 (5 months ago)
Last package publish
Jul 21, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.lemmaoracle/mcp
Version
0.0.17
Auth
Bearer token, API key
Packages
npm @lemmaoracle/mcp
License
Apache-2.0
Repository
github.com/lemmaoracle/lemma
Website
lemma.frame00.com
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registrygithub-graphql
Cite this page

lemmaoracle/mcp. Agent Mart. https://agentmart.dev/connectors/lemmaoracle-mcp (last updated 2026-10-24)