ALM X++
Dynamics 365 Finance and Operations X++ knowledge base with Azure DevOps integration.
Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
Limited view: static analysis for JavaScript is partially covered.
How we verified
Monitored 7 days · every push re-verified
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
Destructive tools are labelled
2 tools sound destructive but lacks a destructiveHint annotation: plan_and_execute, dmf
Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.
Tool annotations
75/90 tools declare annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
90/90 tools missing one or more hints — validate_best_practices (missing: destructiveHint, openWorldHint); find_extensions (missing: destructiveHint, openWorldHint); dmf_import_file (missing: readOnlyHint, idempotentHint), +87 more. OpenAI's directory rejects tools where any hint is missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
[](https://m8ven.ai/mcp/alimbenhelal-pro/alm-xpp-mcp)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check