Metabase (imlewc) MCP Server

@imlewc/metabase-server npm v0.1.0

Published by @imlewc — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for interacting with Metabase - provides AI assistants with tools to query, create, and manage dashboards, cards, and databases

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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 = 95/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 − 5 = 95. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 37

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

  • execute_queryreads sensitive data
  • add_card_to_dashboardno sensitive capability
  • add_dashboard_filterno sensitive capability
  • add_user_to_groupno sensitive capability
  • Card by IDno sensitive capability
  • create_cardno sensitive capability
  • create_collectionno sensitive capability
  • create_dashboardno sensitive capability
  • create_permission_groupno sensitive capability
  • create_userno sensitive capability
Show 27 more tools ↓
  • Dashboard by IDno sensitive capability
  • Database by IDno sensitive capability
  • delete_cardno sensitive capability
  • delete_dashboardno sensitive capability
  • delete_permission_groupno sensitive capability
  • disable_userno sensitive capability
  • execute_cardno sensitive capability
  • get_cardno sensitive capability
  • get_collection_permissionsno sensitive capability
  • get_dashboardno sensitive capability
  • get_dashboard_cardsno sensitive capability
  • get_userno sensitive capability
  • list_cardsno sensitive capability
  • list_collectionsno sensitive capability
  • list_dashboardsno sensitive capability
  • list_databasesno sensitive capability
  • list_permission_groupsno sensitive capability
  • list_usersno sensitive capability
  • remove_card_from_dashboardno sensitive capability
  • remove_user_from_groupno sensitive capability
  • Semesterno sensitive capability
  • update_cardno sensitive capability
  • update_collectionno sensitive capability
  • update_collection_permissionsno sensitive capability
  • update_dashboardno sensitive capability
  • update_dashboard_cardsno sensitive capability
  • update_userno 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
v0.1.0 latest A 95/100 0 1.13.0 2026-09-07

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/imlewc-metabase-server/badge.svg)](https://mcptrustchecker.com/registry/imlewc-metabase-server)
HTML
<a href="https://mcptrustchecker.com/registry/imlewc-metabase-server"><img src="https://mcptrustchecker.com/registry/imlewc-metabase-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/imlewc-metabase-server/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 @imlewc/metabase-server --online

Use the free API → How scoring works

Other implementations of Metabase 11

Independent packages implementing the same tool, scanned with the same engine. Compare all 12 side by side →

More in Databases