Is io.github.alimbenhelal-pro/alm-xpp-mcp up? Live MCP status

Yes, it is up. It answered an MCP server/discover with no credential and negotiated protocol 2026-07-28.

A stock client connected with no credential and negotiated 2026-07-28. Use it.

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

Read at https://api.almxpp.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 90 tools: 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.

No change to its tools between 2026-09 and 2026-10.

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy