Should my agent depend on the MCP server io.github.alimbenhelal-pro/alm-xpp-mcp?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

ALM X++ MCP Server

io.github.alimbenhelal-pro/alm-xpp-mcp

50 AI tools for D365 F&O: X++ search, ADO integration, code gen, security tracing & upgrade impact.

— the operator's own registry description reported

Publisher io.github.alimbenhelal-pro · first seen 2026-08-12 · endpoint https://www.almxpp.com/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.735 (unusual). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency291 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools90

vs populationhigh

capabilities4

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers true0/0 agree

🔏 Signed receipt rr_48fe126672ed6895324f37f7 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

ado_analyze_pr_impact ado_analyze_workitem ado_create_task ado_estimate_effort ado_gap_fit_analysis ado_list_prs ado_post_comment ado_post_pr_comment ado_pr_dependency_map ado_query_workitems ado_read_attachment ado_review_xpp_pr ado_update_workitem ado_wiki_create_or_update_page ado_wiki_delete_page ado_wiki_get_page ado_wiki_list analyze_upgrade_impact appinsights_clear_connection appinsights_diagnose_slowness appinsights_query appinsights_set_connection batch_search compare_objects create_aot_object d365fo_clear_connection d365fo_set_connection detect_performance_issues diff_model_versions dmf dmf_apply_entity_filter dmf_create_data_project dmf_export_package dmf_get_job_status dmf_import_file dmf_transform_excel explain_workflow federated_search find_callers find_change_impact find_entity_for_table find_error_patterns find_event_handlers find_extensions find_references find_related_objects find_relation_path find_similar_implementations fix_best_practice_violations generate_data_entity generate_diagram generate_fdd generate_query generate_release_note_document generate_security_report generate_unit_test generate_xpp_form generate_xpp_template get_data_entity_info get_menu_item_info get_object_context get_object_details get_output_page get_relation_graph get_security_coverage_for_object healthcheck list_custom_model_objects list_objects list_release_note_inputs map_business_process odata_export_entity odata_upsert_rows plan_and_execute prepare_release_note_context recommend_extension_strategy resolve_client_profile resolve_workspace_roots resync_devops_index save_client_profile search_context_docs search_d365_code search_labels suggest_edt suggest_refactoring summarize_for_stakeholder trace_field_lineage trace_role_license_tree trace_security_chain validate_best_practices validate_object_naming

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	90/90	✓
has a description	90/90	✓
description is substantive	90/90	✓
parameters are typed	90/90	✓
parameters are described	90/90	✓

90 of 90 tools graded · 90 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

0/0 answers agree with the published primary source · 2 unverifiable.

claim class	key	verdict	primary source
tariff-duty	6109.10.00	unverifiable	us-hts
tariff-duty	8471.30.01	unverifiable	us-hts

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.0.0

server version ALMXPPMCP

Capabilities: logging prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)

date	type	what changed
2026-08-14	outcome	ok_tools (was http_error)
2026-08-12	outcome	first probe: http_error

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:22Z	ok_tools	200	291	2025-06-18
2026-08-12T05:34:34Z	http_error	404	290

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.alimbenhelal-pro/alm-xpp-mcp.svg)](https://robinsaige.com/s/io.github.alimbenhelal-pro/alm-xpp-mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview