# mcp-adr-analysis-server

AI-powered MCP server for analyzing Architectural Decision Records (ADRs).

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 2.7.20
- **Author:** io.github.tosin2013
- **License:** MIT
- **npm:** mcp-adr-analysis-server
- **Source:** https://github.com/tosin2013/mcp-adr-analysis-server
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 10 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-18T23:34:00.560Z
- **Version scanned:** 2.6.14
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `get_server_context`
- `goal_specification`
- `project_type`
- `target_audience`
- `scale_requirements`
- `action_confirmation`
- `action`
- `files`
- `preview`
- `ambiguity_resolution`
- `context`
- `ambiguous_items`
- `suggestions`
- `custom_rule_definition`
- `rule_category`
- `existing_rules`
- `baseline_analysis`
- `project_path`
- `focus_areas`
- `secret_prevention_guidance`
- `content_type`
- `target_location`
- `todo_task_generation`
- `adrDirectory`
- `scope`
- `phase`
- `projectPath`
- `todo_status_management`
- `taskId`
- `newStatus`
- `filters`
- `todo_dependency_analysis`
- `includeUpstream`
- `includeDownstream`
- `analysisDepth`
- `todo_estimation`
- `estimationType`
- `includeUncertainty`
- `granularity`
- `projectContext`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-adr-analysis-server\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"mcp-adr-analysis-server\"\n      ],\n      \"env\": {\n        \"OPENROUTER_API_KEY\": \"<YOUR_OPENROUTER_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `OPENROUTER_API_KEY` — Openrouter API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 23, ceiling 23 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/mcp-adr-analysis-server
- Install plan: https://forgeregistry.com/api/v1/packages/mcp-adr-analysis-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/mcp-adr-analysis-server
- HTML page: https://forgeregistry.com/registry/mcp-adr-analysis-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.