Adaptive Cards MCP Server

adaptive-cards-mcp npm v2.3.0

Published by vikrantsingh01 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

AI-powered Adaptive Card generator — MCP server + npm library. 9 tools: generate, validate, optimize, template, transform cards for Teams, Outlook, Copilot. Designer preview included.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 4

medium Hardcoded egress to an external endpoint (dist/index.cjs)MTC-SRC-003

In the server's implementation (`dist/index.cjs:4400`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch("https://api.anthropic.com/v1/messages", { method: "POST", headers: { "Conte

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/index.cjs

medium Hardcoded egress to an external endpoint (dist/index.js)MTC-SRC-003

In the server's implementation (`dist/index.js:4312`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch("https://api.anthropic.com/v1/messages", { method: "POST", headers: { "Conte

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/index.js

medium Hardcoded egress to an external endpoint (dist/server.cjs)MTC-SRC-003

In the server's implementation (`dist/server.cjs:3706`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch("https://api.anthropic.com/v1/messages", { method: "POST", headers: { "Conte

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/server.cjs

medium Hardcoded egress to an external endpoint (dist/server.js)MTC-SRC-003

In the server's implementation (`dist/server.js:3697`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch("https://api.anthropic.com/v1/messages", { method: "POST", headers: { "Conte

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/server.js

Tools 47

Each tool and what it can reach — statically extracted from the published source.

  • Adaptive Cards v1.6 Schemano sensitive capability
  • approvalno sensitive capability
  • calendar-eventno sensitive capability
  • cardno sensitive capability
  • card_workflowno sensitive capability
  • chartno sensitive capability
  • convert-data-to-cardno sensitive capability
  • create-adaptive-cardno sensitive capability
  • dashboardno sensitive capability
  • datano sensitive capability
Show 37 more tools ↓
  • data_to_cardno sensitive capability
  • data-tableno sensitive capability
  • descriptionno sensitive capability
  • Example Cards Catalogno sensitive capability
  • Examples by Intentno sensitive capability
  • factsno sensitive capability
  • flight-statusno sensitive capability
  • generate_and_validateno sensitive capability
  • generate_cardno sensitive capability
  • hostno sensitive capability
  • Host Compatibility Matrixno sensitive capability
  • Host-specific Compatibilityno sensitive capability
  • image-galleryno sensitive capability
  • incident-alertno sensitive capability
  • input-formno sensitive capability
  • intentno sensitive capability
  • Layout Pattern Guideno sensitive capability
  • listno sensitive capability
  • notificationno sensitive capability
  • optimize_cardno sensitive capability
  • order-confirmationno sensitive capability
  • presentationno sensitive capability
  • pricing-tableno sensitive capability
  • profileno sensitive capability
  • pull-requestno sensitive capability
  • review-adaptive-cardno sensitive capability
  • Session Card Storeno sensitive capability
  • status-updateno sensitive capability
  • suggest_layoutno sensitive capability
  • survey-pollno sensitive capability
  • template_cardno sensitive capability
  • timeline-activityno sensitive capability
  • titleno sensitive capability
  • transform_cardno sensitive capability
  • validate_cardno sensitive capability
  • weatherno sensitive capability
  • wizard-stepno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.3.0 latest A 96/100 4 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/adaptive-cards-mcp/badge.svg)](https://mcptrustchecker.com/registry/adaptive-cards-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/adaptive-cards-mcp"><img src="https://mcptrustchecker.com/registry/adaptive-cards-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/adaptive-cards-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan adaptive-cards-mcp --online

Use the free API → How scoring works

More in Productivity & Workflow