Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "lemmaoracle": {
      "type": "http",
      "url": "https://mcp.lemma.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${LEMMAORACLE_TOKEN}"
      }
    }
  }
}

claude mcp add --transport http lemmaoracle https://mcp.lemma.workers.dev/mcp --header "Authorization: Bearer ${LEMMAORACLE_TOKEN}"

[mcp_servers.lemmaoracle]
url = "https://mcp.lemma.workers.dev/mcp"
bearer_token_env_var = "LEMMAORACLE_TOKEN"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lemmaoracle": {
      "type": "remote",
      "url": "https://mcp.lemma.workers.dev/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer {env:LEMMAORACLE_TOKEN}"
      }
    }
  }
}

{
  "mcpServers": {
    "lemmaoracle": {
      "type": "http",
      "url": "https://mcp.lemma.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${LEMMAORACLE_TOKEN}"
      }
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=lemmaoracle&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmxlbW1hLndvcmtlcnMuZGV2L21jcCIsImhlYWRlcnMiOnsiQXV0aG9yaXphdGlvbiI6IkJlYXJlciAke0xFTU1BT1JBQ0xFX1RPS0VOfSJ9fQ%3D%3D"
}

{
  "servers": {
    "lemmaoracle": {
      "type": "http",
      "url": "https://mcp.lemma.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${LEMMAORACLE_TOKEN}"
      }
    }
  }
}

{
  "mcpServers": {
    "lemmaoracle": {
      "httpUrl": "https://mcp.lemma.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${LEMMAORACLE_TOKEN}"
      }
    }
  }
}

extensions:
  "lemmaoracle":
    enabled: true
    name: "lemmaoracle"
    type: streamable_http
    uri: "https://mcp.lemma.workers.dev/mcp"
    headers:
      "Authorization": "Bearer ${LEMMAORACLE_TOKEN}"
    timeout: 300

Placeholders to fill from your own secret store: ${LEMMAORACLE_TOKEN}. The registry never accepts secret values.

Quality 81 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene100 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations5 of 5 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 1,542 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependencies33 · weight 15

fail
deps.known_vulns1 advisory to act on (malicious, or rated high or critical with a fix available): GHSA-qpx9-hpmf-5gmw in [email protected] (indirect, fixed in 1.13.8)
fail
deps.mcp_sdk_version@modelcontextprotocol/sdk 1.29.0 has 1 known advisory (GHSA-6qxp-vccf-f47h); update @modelcontextprotocol/sdk to 1.31.0 or later
pass
deps.resolvable@lemmaoracle/[email protected] resolved: 202 packages

5 tools, about 1,542 tokens to load them all · tool set 76838e5fa6dc · checked 2026-10-19 10:20 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 89 / 100

provenance90

liveness97

freshness65

hygiene100

+repository +namespace-matches-repo +website +reachable +uptime-93% ~updated-154d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Dependencies

@lemmaoracle/[email protected] npm201 dependencies, resolved · MCP SDK @modelcontextprotocol/sdk 1.30.1 · advisories checked 2026-10-19

advisory	severity	package	fixed in
GHSA-6qxp-vccf-f47hMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server	high	`@modelcontextprotocol/[email protected]`MCP SDK, indirect	fixed in `1.31.0`
GHSA-6qxp-vccf-f47hMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server	high	`@modelcontextprotocol/[email protected]`MCP SDK, direct	fixed in `1.31.0`
GHSA-qpx9-hpmf-5gmwUnderscore has unlimited recursion in _.flatten and _.isEqual, potential for DoS attack	high	`[email protected]`indirect	fixed in `1.13.8`

Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://mcp.lemma.workers.dev/mcp` streamable-http	api_key `${LEMMAORACLE_TOKEN}`	yes	93%	284 ms	2025-11-25	2026-10-19

package	registry	version	runtime	secrets
`@lemmaoracle/mcp`	npm	0.0.17	–	`LEMMA_API_KEY`

Tools (5)

`lemma_get_circuit`read-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_generator`read-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_status`read-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 cryptographic validity.
`lemma_get_schema`read-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_attributes`read-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 `attributes`.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "io.github.lemmaoracle/mcp",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://mcp.lemma.workers.dev/mcp",
      "type": "streamable-http",
      "headers": [
        {
          "name": "Authorization",
          "isSecret": true,
          "isRequired": true,
          "description": "Lemma API key as Bearer token. Format: 'Bearer <LEMMA_API_KEY>'. Get a key at https://lemma.frame00.com/services"
        }
      ]
    }
  ],
  "version": "0.0.17",
  "packages": [
    {
      "version": "0.0.17",
      "transport": {
        "type": "stdio"
      },
      "identifier": "@lemmaoracle/mcp",
      "registryType": "npm",
      "registryBaseUrl": "https://registry.npmjs.org",
      "environmentVariables": [
        {
          "name": "LEMMA_API_KEY",
          "isSecret": true,
          "isRequired": true,
          "description": "Lemma API key (Bearer token). Get one at https://lemma.frame00.com/services"
        },
        {
          "name": "LEMMA_API_BASE",
          "description": "Optional API base URL. Defaults to production endpoint."
        }
      ]
    }
  ],
  "repository": {
    "url": "https://github.com/lemmaoracle/lemma",
    "source": "github",
    "subfolder": "packages/mcp"
  },
  "websiteUrl": "https://lemma.frame00.com",
  "description": "Verifiable provenance for AI agents — ZK proofs over confidential documents, no plaintext exposure."
}