Home / MCP registry index / io.github.alimbenhelal-pro/alm-xpp-mcp
ALM X++ MCP Server
io.github.alimbenhelal-pro/alm-xpp-mcp in the official MCP registry.
Endpoint https://api.almxpp.com/mcp. Source: github.com/alimbenhelal-pro/ALM-XPP-MCP.
The registry describes it as: D365 F&O: 90 AI tools over 200K+ objects, 25M+ cross-refs, 24M+ label translations.
We read its 90 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
validate_best_practices find_extensions dmf_import_file search_d365_code dmf_transform_excel generate_query ado_wiki_delete_page appinsights_diagnose_slowness ado_wiki_list get_object_details ado_query_workitems dmf_apply_entity_filter ado_update_workitem find_references ado_gap_fit_analysis batch_search ado_read_attachment trace_field_lineage plan_and_execute find_similar_implementations recommend_extension_strategy diff_model_versions find_related_objects ado_review_xpp_pr dmf_create_data_project find_entity_for_table summarize_for_stakeholder suggest_refactoring resync_devops_index ado_wiki_get_page dmf find_callers healthcheck ado_analyze_pr_impact find_error_patterns suggest_edt get_object_context odata_upsert_rows find_change_impact generate_security_report ado_create_task appinsights_set_connection dmf_get_job_status detect_performance_issues get_relation_graph d365fo_clear_connection generate_xpp_template get_security_coverage_for_object get_output_page ado_pr_dependency_map generate_fdd map_business_process ado_post_comment get_data_entity_info compare_objects list_objects explain_workflow trace_role_license_tree prepare_release_note_context ado_analyze_workitem and 30 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-alimbenhelal-pro-alm-xpp-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.