Is Al safe and trustworthy?

tashan scores Al on public evidence — tashan score 38.0/100, it is currently abandoned, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, its declared dependencies reach: filesystem. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

In Claude Code: run `claude mcp add al-mcp-server -- npx -y al-mcp-server`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

source: StefanMaron/AL-Dependency-MCP-Server.

‹ The Index

Al

npm

Model Context Protocol (MCP) server providing intelligent AL (Application Language) code assistance for Microsoft Dynamics 365 Business Central development.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Install (Claude Code):

claude mcp add al-mcp-server -- npx -y al-mcp-server

solid

“5 worked examples; short of deep on per-tool docs and a stated limitation and setup/auth”

This grade is wrong ›

Looking for a replacement? npx tashan-cli doctor is free and tells you everything above about your whole config. tashan Pro names the replacement — which one, and how it measures. $6/mo.

tashan score: 38.0
Instruction depth: 64.0 (solid — documents the job properly, with examples you could follow)
Adoption: 419/wk
Upkeep: 52.0
Freshness: 49.0
Evidence coverage: 100% of the inputs this score can use
Health: abandoned
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 2.5.0 — this package, not its dependency tree

Reads and writes filesfrom declared dependencies

Signed build provenancepublished from public CI with an attestation

What changed recently

2026-08-10 al-mcp-server now reaches filesystem Its declared dependencies reach further into your machine than they did before.
2026-09-13 al-mcp-server now reads as abandoned, was active Upkeep signals stopped, under enough issue pressure that it is not merely finished.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 2 changes to Al in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-al-mcp-server.svg)](https://tashan.sh/capability/pkg-al-mcp-server.html)

npm ↗ · source ↗ · pkg:al-mcp-server

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?