Ldap Assistant MCP Server

ldap-assistant-mcp PyPI v0.5.0

Published by droideck — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for 389 Directory Server health diagnostics, log analysis, and SOS-report investigation

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 44

Each tool and what it can reach — statically extracted from the published source.

  • analyze_access_logno sensitive capability
  • analyze_archiveno sensitive capability
  • analyze_audit_logno sensitive capability
  • analyze_error_logno sensitive capability
  • analyze_index_configurationno sensitive capability
  • check_replication_lagno sensitive capability
  • compare_dse_configsno sensitive capability
  • compare_server_configurationsno sensitive capability
  • describe_connectionno sensitive capability
  • find_unindexed_searchesno sensitive capability
Show 34 more tools ↓
  • first_lookno sensitive capability
  • get_agreement_statusno sensitive capability
  • get_backend_configurationno sensitive capability
  • get_cache_statisticsno sensitive capability
  • get_connection_statisticsno sensitive capability
  • get_operation_statisticsno sensitive capability
  • get_performance_summaryno sensitive capability
  • get_replication_statusno sensitive capability
  • get_replication_topologyno sensitive capability
  • get_resource_utilizationno sensitive capability
  • get_server_configurationno sensitive capability
  • get_thread_statisticsno sensitive capability
  • get_user_detailsno sensitive capability
  • ldap_searchno sensitive capability
  • list_active_usersno sensitive capability
  • list_all_groupsno sensitive capability
  • list_all_usersno sensitive capability
  • list_healthcheck_errorsno sensitive capability
  • list_healthchecksno sensitive capability
  • list_indexesno sensitive capability
  • list_locked_usersno sensitive capability
  • list_pluginsno sensitive capability
  • list_replication_conflictsno sensitive capability
  • list_serversno sensitive capability
  • parse_access_logno sensitive capability
  • parse_audit_logno sensitive capability
  • parse_error_logno sensitive capability
  • run_healthcheckno sensitive capability
  • run_monitorno sensitive capability
  • search_users_by_attributeno sensitive capability
  • search_users_by_nameno sensitive capability
  • server_healthno sensitive capability
  • validate_configurationno sensitive capability
  • whoamino sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.5.0 latest A 99/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ldap-assistant-mcp/badge.svg)](https://mcptrustchecker.com/registry/ldap-assistant-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/ldap-assistant-mcp"><img src="https://mcptrustchecker.com/registry/ldap-assistant-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ldap-assistant-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan ldap-assistant-mcp --online --registry pypi

Use the free API → How scoring works

More in Databases