Is Mnemoshare Keycloak Mcp Safe?
Mnemoshare Keycloak Mcp — Nerq Trust Score 71.3/100 (B grade). Based on analysis of 5 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-04-28.
Yes, Mnemoshare Keycloak Mcp is safe to use. Mnemoshare Keycloak Mcp is a software tool with a Nerq Trust Score of 71.3/100 (B), based on 5 independent data dimensions. Recommended for use. Security: 0/100. Maintenance: 1/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-28. Machine-readable data (JSON).
Is Mnemoshare Keycloak Mcp safe?
YES — Mnemoshare Keycloak Mcp has a Nerq Trust Score of 71.3/100 (B). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for use — review the full report below for specific considerations.
What is Mnemoshare Keycloak Mcp's trust score?
Mnemoshare Keycloak Mcp has a Nerq Trust Score of 71.3/100, earning a B grade. This score is based on 5 independently measured dimensions including security, maintenance, and community adoption.
What are the key security findings for Mnemoshare Keycloak Mcp?
Mnemoshare Keycloak Mcp's strongest signal is compliance at 100/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.
What is Mnemoshare Keycloak Mcp and who maintains it?
| Author | MnemoShare |
| Category | Devops |
| Source | https://github.com/MnemoShare/mnemoshare-keycloak-mcp |
| Frameworks | anthropic · mcp |
| Protocols | mcp · rest |
Regulatory Compliance
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Popular Alternatives in devops
What Is Mnemoshare Keycloak Mcp?
Mnemoshare Keycloak Mcp is a DevOps tool: Keycloak MCP server for automating Keycloak administration tasks.. Nerq Trust Score: 71/100 (B).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.
How Nerq Assesses Mnemoshare Keycloak Mcp's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Mnemoshare Keycloak Mcp performs in each:
- Security (0/100): Mnemoshare Keycloak Mcp's security posture is poor. This score factors in known CVEs, dependency vulnerabilities, security policy presence, and code signing practices.
- Maintenance (1/100): Mnemoshare Keycloak Mcp is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (1/100): Documentation quality is insufficient. This includes README completeness, API documentation, usage examples, and contribution guidelines.
- Compliance (100/100): Mnemoshare Keycloak Mcp is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Based on GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 71.3/100 (B) reflects the weighted combination of these signals. This exceeds the Nerq Verified threshold of 70, indicating the tool meets our standards for production use.
Who Should Use Mnemoshare Keycloak Mcp?
Mnemoshare Keycloak Mcp is designed for:
- Developers and teams working with devops tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: Mnemoshare Keycloak Mcp meets the minimum threshold for production use, but we recommend monitoring for security advisories and keeping dependencies up to date. Consider implementing additional guardrails for sensitive workloads.
How to Verify Mnemoshare Keycloak Mcp's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Review the repository's security policy, open issues, and recent commits for signs of active maintenance.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Mnemoshare Keycloak Mcp's dependency tree. - Review permissions — Understand what access Mnemoshare Keycloak Mcp requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Mnemoshare Keycloak Mcp in a sandboxed environment before granting access to production data or systems.
- Monitor continuously — Use Nerq's API to set up automated trust checks:
GET nerq.ai/v1/preflight?target=mnemoshare-keycloak-mcp - Review the license — Confirm that Mnemoshare Keycloak Mcp's license is compatible with your intended use case. Pay attention to restrictions on commercial use, redistribution, and derivative works. Some AI tools use dual licensing or have separate terms for enterprise customers that differ from the open-source license.
- Check community signals — Look at the project's issue tracker, discussion forums, and social media presence. A healthy community actively reports bugs, contributes fixes, and discusses security concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Mnemoshare Keycloak Mcp
When evaluating whether Mnemoshare Keycloak Mcp is safe, consider these category-specific risks:
Understand how Mnemoshare Keycloak Mcp processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Mnemoshare Keycloak Mcp's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.
Regularly check for updates to Mnemoshare Keycloak Mcp. Security patches and bug fixes are only effective if you're running the latest version.
If Mnemoshare Keycloak Mcp connects to external APIs or services, each integration point is a potential attack surface. Audit all third-party connections, verify that data shared with external services is minimized, and ensure that integration credentials are rotated regularly.
Verify that Mnemoshare Keycloak Mcp's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Mnemoshare Keycloak Mcp in violation of its license can expose your organization to legal liability.
Mnemoshare Keycloak Mcp and the EU AI Act
Mnemoshare Keycloak Mcp is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.
Nerq's compliance assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal compliance.
Best Practices for Using Mnemoshare Keycloak Mcp Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Mnemoshare Keycloak Mcp while minimizing risk:
Periodically review how Mnemoshare Keycloak Mcp is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.
Ensure Mnemoshare Keycloak Mcp and all its dependencies are running the latest stable versions to benefit from security patches.
Grant Mnemoshare Keycloak Mcp only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Mnemoshare Keycloak Mcp's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Mnemoshare Keycloak Mcp is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Mnemoshare Keycloak Mcp?
Even well-trusted tools aren't right for every situation. Consider avoiding Mnemoshare Keycloak Mcp in these scenarios:
- Scenarios where Mnemoshare Keycloak Mcp's specific capabilities exceed your actual needs — simpler tools may be safer
- Air-gapped environments where the tool cannot receive security updates
- Projects with strict regulatory requirements that haven't been explicitly validated
For each scenario, evaluate whether Mnemoshare Keycloak Mcp's trust score of 71.3/100 meets your organization's risk tolerance. The Nerq Verified status indicates general production readiness, but sector-specific requirements may apply.
How Mnemoshare Keycloak Mcp Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among DevOps tools, the average Trust Score is 63/100. Mnemoshare Keycloak Mcp's score of 71.3/100 is above the category average of 63/100.
This positions Mnemoshare Keycloak Mcp favorably among DevOps tools. While it outperforms the average, there is still room for improvement in certain trust dimensions.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderate in isolation may actually represent strong performance within a challenging category — or vice versa. Nerq's category-relative analysis helps teams make informed decisions by showing not just absolute quality, but how a tool ranks against its direct peers.
Trust Score History
Nerq continuously monitors Mnemoshare Keycloak Mcp and recalculates its Trust Score as new data becomes available. Our scoring engine ingests real-time signals from source repositories, vulnerability databases (NVD, OSV.dev), package registries, and community metrics. When a new CVE is published, a major release ships, or maintenance patterns change, Mnemoshare Keycloak Mcp's score is updated within 24 hours.
Historical trust trends reveal whether a tool is improving, stable, or declining over time. A tool that consistently maintains or improves its score demonstrates ongoing commitment to security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Mnemoshare Keycloak Mcp's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=mnemoshare-keycloak-mcp&include=history
Nerq retains trust score snapshots at regular intervals, enabling trend analysis across weeks and months. Enterprise users can access detailed historical reports showing how each dimension — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Mnemoshare Keycloak Mcp are strengthening or weakening over time.
Mnemoshare Keycloak Mcp vs Alternatives
In the devops category, Mnemoshare Keycloak Mcp scores 71.3/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Mnemoshare Keycloak Mcp vs ansible — Trust Score: 76.8/100
- Mnemoshare Keycloak Mcp vs Flowise — Trust Score: 63.3/100
- Mnemoshare Keycloak Mcp vs learn-claude-code — Trust Score: 69.2/100
Key Takeaways
- Mnemoshare Keycloak Mcp has a Trust Score of 71.3/100 (B) and is Nerq Verified.
- Mnemoshare Keycloak Mcp meets the minimum threshold for production deployment, though monitoring and additional guardrails are recommended.
- Among DevOps tools, Mnemoshare Keycloak Mcp scores above the category average of 63/100, demonstrating above-average reliability.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
Detailed Score Analysis
| Dimension | Score |
|---|---|
| Security | 0/100 |
| Maintenance | 1/100 |
| Popularity | 0/100 |
Based on 3 dimensions. Data from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard.
What data does Mnemoshare Keycloak Mcp collect?
Privacy assessment for Mnemoshare Keycloak Mcp is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.
Is Mnemoshare Keycloak Mcp secure?
Security score: 0/100. Review security practices and consider alternatives with higher security scores for sensitive use cases.
Nerq monitors this entity against NVD, OSV.dev, and registry-specific vulnerability databases for ongoing security assessment.
Full analysis: Mnemoshare Keycloak Mcp Security Report
How we calculated this score
Mnemoshare Keycloak Mcp's trust score of 71.3/100 (B) is computed from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 3 independent dimensions: security (0/100), maintenance (1/100), popularity (0/100). Each dimension is weighted equally to produce the composite trust score.
Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.
This page was last reviewed on April 28, 2026. Data version: 1.0.
Full methodology documentation · Machine-readable data (JSON API)
Frequently Asked Questions
Is Mnemoshare Keycloak Mcp Safe?
What is Mnemoshare Keycloak Mcp's trust score?
What are safer alternatives to Mnemoshare Keycloak Mcp?
How often is Mnemoshare Keycloak Mcp's safety score updated?
Can I use Mnemoshare Keycloak Mcp in a regulated environment?
See Also
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.