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.

LemonLDAP::NG MCP Server

NPM · LLNG-MCP · SCANNED SEP 25

Manage LemonLDAP::NG SSO instances: configuration, sessions, OIDC, SAML, 2FA.

Available components

0 this week 72 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2821 tokens (~65/item across 43 items; 43 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 12 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "llng_config_delKey" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 43 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
Install

How do I install the LemonLDAP::NG MCP Server server?

LemonLDAP::NG MCP Server runs locally as an npm package, launched with npx -y llng-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · llng-mcp

# add to Claude Code
claude mcp add linagora-llng-mcp -- npx -y llng-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "linagora-llng-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "llng-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "linagora-llng-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "llng-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add linagora-llng-mcp -- npx -y llng-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "linagora-llng-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "llng-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add linagora-llng-mcp --command npx --arg -y --arg llng-mcp
# ~/.hermes/config.yaml
mcp_servers:
  linagora-llng-mcp:
    command: "npx"
    args: ["-y", "llng-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "linagora-llng-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "llng-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add linagora-llng-mcp -t stdio -c npx -a -y llng-mcp
// mcp.json
{
  "mcpServers": {
    "linagora-llng-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "llng-mcp"
      ]
    }
  }
}
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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 22 Sept 26 0
    • Stability: 0.97 → pass security
  • 21 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 25 Sept 2026 · Analysed npm/llng-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 43 exposed · ~2,821 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
llng_2fa_delete ~50

Delete specific 2FA device(s)

NameTypeReqDescription
idsarrayyes–
instancestring–LLNG instance name (uses default if omitted)
userstringyes–

No output schema declared.

No examples provided.

llng_2fa_delType ~54

Delete all 2FA devices of a given type

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
typestringyes–
userstringyes–

No output schema declared.

No examples provided.

llng_2fa_list ~42

List user's 2FA devices

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
userstringyes–

No output schema declared.

No examples provided.

llng_config_addKey ~75

Add subkey to a composite LLNG config parameter

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
keystringyesThe composite config key
subkeystringyesThe subkey to add
valuestringyesThe value for the subkey

No output schema declared.

No examples provided.

llng_config_delKey ~62

Delete subkey from a composite LLNG config parameter

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
keystringyesThe composite config key
subkeystringyesThe subkey to delete

No output schema declared.

No examples provided.

llng_config_export ~34

Export full LLNG config as JSON

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_config_get ~49

Get LLNG config value(s) by key

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
keysarrayyesArray of config keys to retrieve

No output schema declared.

No examples provided.

llng_config_import ~47

Import LLNG config from JSON

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
jsonstringyesJSON string of the config to import

No output schema declared.

No examples provided.

llng_config_info ~39

Get current LLNG config metadata (number, author, date)

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_config_merge ~47

Merge JSON snippet into LLNG config

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
jsonstringyesJSON string to merge into config

No output schema declared.

No examples provided.

llng_config_rollback ~36

Rollback LLNG config to previous version

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_config_set ~60

Set LLNG config value(s)

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
keysobjectyesKey-value pairs to set in config
logstring–Optional log message for this change

No output schema declared.

No examples provided.

llng_config_test_email ~51

Send a test email to verify SMTP settings

NameTypeReqDescription
destinationstringyesEmail address to send the test email to
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_config_update_cache ~34

Force LLNG config cache update

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_consent_delete ~48

Delete user's OIDC consent(s)

NameTypeReqDescription
idsarrayyes–
instancestring–LLNG instance name (uses default if omitted)
userstringyes–

No output schema declared.

No examples provided.

llng_consent_list ~41

List user's OIDC consents

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
userstringyes–

No output schema declared.

No examples provided.

llng_delete_session ~68

Delete user sessions by UID pattern

NameTypeReqDescription
debugboolean–Enable debug output
forceboolean–Force deletion without confirmation
instancestring–LLNG instance name (uses default if omitted)
uidstringyesUID pattern to match for session deletion

No output schema declared.

No examples provided.

llng_download_saml_metadata ~88

Download SAML metadata from a remote IdP

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
noCheckboolean–Disable SSL certificate verification
outputFilestring–Output file path for downloaded metadata
urlstringyesURL of the remote SAML metadata
verboseboolean–Enable verbose output

No output schema declared.

No examples provided.

llng_import_metadata ~140

Import a SAML federation into LLNG config

NameTypeReqDescription
idpPrefixstring–Prefix for IdP entity IDs
ignoreIdparray–IdP entity IDs to ignore
ignoreSparray–SP entity IDs to ignore
instancestring–LLNG instance name (uses default if omitted)
noCheckboolean–Disable SSL certificate verification
removeboolean–Remove entities not in metadata
spPrefixstring–Prefix for SP entity IDs
urlstringyesURL of the SAML federation metadata
verboseboolean–Enable verbose output

No output schema declared.

No examples provided.

llng_instances ~19

List available LLNG instances and their transport mode

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

llng_oidc_authorize ~42

Get authorization URL with PKCE

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
scopestring––

No output schema declared.

No examples provided.

llng_oidc_check_auth ~61

Check if a URL requires authentication (only public URLs allowed, private/internal IPs blocked)

NameTypeReqDescription
access_tokenstringyes–
instancestring–LLNG instance name (uses default if omitted)
urlstringyes–

No output schema declared.

No examples provided.

llng_oidc_introspect ~43

Introspect an access token

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
tokenstringyes–

No output schema declared.

No examples provided.

llng_oidc_issuer_enable ~66

Enable OIDC issuer on the LLNG instance (activates issuerDBOpenIDConnectActivation and generates signing keys)

NameTypeReqDescription
forceboolean–Force re-enable even if already activated
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_oidc_metadata ~33

Fetch OIDC discovery metadata

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_oidc_refresh ~40

Refresh an access token

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)
refresh_tokenstringyes–

No output schema declared.

No examples provided.

llng_oidc_rp_add ~158

Add a new OIDC Relying Party

NameTypeReqDescription
clientIdstringyesOAuth2 client ID
clientSecretstring–OAuth2 client secret
confKeystringyesInternal identifier for the RP
displayNamestring–Display name for the RP
exportedVarsobject–Claim-to-attribute mappings (default: {"name":"cn","preferred_username":"uid","email":"mail"})
extraClaimsobject–Extra claims mappings
instancestring–LLNG instance name (uses default if omitted)
optionsobject–Additional raw OIDC RP options
redirectUrisstringyesRedirect URIs (space or newline separated)

No output schema declared.

No examples provided.

llng_oidc_rp_delete ~55

Delete an OIDC Relying Party by confKey

NameTypeReqDescription
confKeystringyesThe RP configuration key to delete
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_oidc_rp_get ~59

Get full details of an OIDC Relying Party by confKey

NameTypeReqDescription
confKeystringyesThe RP configuration key (internal identifier)
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_oidc_rp_list ~45

List configured OIDC Relying Parties with their clientID and displayName

NameTypeReqDescription
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_oidc_tokens ~49

Exchange authorization code for tokens

NameTypeReqDescription
codestringyes–
code_verifierstringyes–
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_oidc_userinfo ~44

Get user info from OIDC provider

NameTypeReqDescription
access_tokenstringyes–
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_oidc_whoami ~55

Decode ID token to show identity (WARNING: signature is NOT verified, for debugging only)

NameTypeReqDescription
id_tokenstringyes–
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_purge_central_cache ~69

Purge expired sessions from central cache

NameTypeReqDescription
debugboolean–Enable debug output
forceboolean–Force purge without confirmation
instancestring–LLNG instance name (uses default if omitted)
jsonboolean–Output in JSON format

No output schema declared.

No examples provided.

llng_purge_local_cache ~44

Purge local handler cache

NameTypeReqDescription
debugboolean–Enable debug output
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_rotate_oidc_keys ~44

Rotate OIDC signing keys

NameTypeReqDescription
debugboolean–Enable debug output
instancestring–LLNG instance name (uses default if omitted)

No output schema declared.

No examples provided.

llng_session_backup ~83

Backup all LLNG sessions

NameTypeReqDescription
backendstring–Optional backend type to backup (persistent, oidc, saml, cas)
instancestring–LLNG instance name (uses default if omitted)
persistentboolean–Shortcut for --backend persistent
refreshTokensboolean–Filter for refresh token (offline) sessions only

No output schema declared.

No examples provided.

llng_session_delete ~167

Delete LLNG session(s)

NameTypeReqDescription
backendstring–Optional backend type (persistent, oidc, saml, cas)
hashboolean–Indicates session IDs are original cookie values
idsarray–Array of session IDs to delete (not needed when using where)
instancestring–LLNG instance name (uses default if omitted)
kindstring–Filter by session kind: SSO, SAML, CAS, OIDC, Persistent. This is a shortcut that adds _session_kind to the where filter
persistentboolean–Shortcut for --backend persistent
refreshTokensboolean–Filter for refresh token (offline) sessions only
whereobject–Delete sessions matching filter instead of by ID

No output schema declared.

No examples provided.

llng_session_delKey ~111

Delete key(s) from an LLNG session

NameTypeReqDescription
backendstring–Optional backend type
hashboolean–Session ID is original cookie value
idstringyesThe session ID to modify
instancestring–LLNG instance name (uses default if omitted)
keysarrayyesArray of keys to delete from the session
persistentboolean–Shortcut for --backend persistent
refreshTokensboolean–Target refresh token sessions

No output schema declared.

No examples provided.

llng_session_get ~124

Get LLNG session by ID

NameTypeReqDescription
backendstring–Optional backend type (persistent, oidc, saml, cas)
hashboolean–Indicates the given session ID is the original cookie value (for hashed session storage)
idstringyesThe session ID to retrieve
instancestring–LLNG instance name (uses default if omitted)
persistentboolean–Shortcut for --backend persistent; also hashes UID for persistent session ID
refreshTokensboolean–Filter for refresh token (offline) sessions only

No output schema declared.

No examples provided.

llng_session_search ~181

Search LLNG sessions

NameTypeReqDescription
backendstring–Backend type (persistent, oidc, saml, cas)
countboolean–Return only the count of matching sessions
hashboolean–Indicates session IDs are original cookie values
idOnlyboolean–Only return session IDs
instancestring–LLNG instance name (uses default if omitted)
kindstring–Filter by session kind: SSO, SAML, CAS, OIDC, Persistent. This is a shortcut that adds _session_kind to the where filter
persistentboolean–Shortcut for --backend persistent
refreshTokensboolean–Filter for refresh token (offline) sessions only
selectarray–Fields to return in results
whereobject–Field=value pairs for filtering

No output schema declared.

No examples provided.

llng_session_setKey ~111

Set key(s) in an LLNG session

NameTypeReqDescription
backendstring–Optional backend type
hashboolean–Session ID is original cookie value
idstringyesThe session ID to modify
instancestring–LLNG instance name (uses default if omitted)
keysobjectyesKey-value pairs to set in the session
persistentboolean–Shortcut for --backend persistent
refreshTokensboolean–Target refresh token sessions

No output schema declared.

No examples provided.

llng_user_attributes ~53

Look up user attributes

NameTypeReqDescription
fieldstring–Specific field to return
instancestring–LLNG instance name (uses default if omitted)
usernamestringyesUsername to look up

No output schema declared.

No examples provided.

Common questions

What is the LemonLDAP::NG MCP Server server?

LemonLDAP::NG MCP Server is listed in the public MCP registry as io.github.linagora/llng-mcp. Manage LemonLDAP::NG SSO instances: configuration, sessions, OIDC, SAML, 2FA. This page covers its npm package (llng-mcp).

Is the LemonLDAP::NG MCP Server server safe to use?

LemonLDAP::NG MCP Server scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 LemonLDAP::NG MCP Server server expose?

LemonLDAP::NG MCP Server exposes 43 tools: llng_config_info, llng_config_get, llng_config_set, llng_config_addKey, llng_config_delKey, and 38 more. Their descriptions and schemas cost roughly 2,821 tokens of context every time the server is loaded.

Is the LemonLDAP::NG MCP Server server still maintained?

LemonLDAP::NG MCP Server is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.