Superbased MCP Server

superbased npm v2.0.9

Published by marmutapp — 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.

Trust grade
C
74/100
Last scanned
Trust
C · 74/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
Critical
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.
C Why this grade threat 85 − adoption risk = 74/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 − 15.4 = 85. What the published surface and source actually contain:

PointsWhat was foundCategory
−15.4 Untrusted input concatenated into a command sink ×10 MTC-SRC-009 injection

2. Client adoption risk — 85 − 11 = 74. 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
−10 capability blast radius (critical) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable
inspection depth (source) — how much of the target the scan could see

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 30

high Shell/command execution in server code (dist/electron/core/input-injection/windows.js)MTC-SRC-002

In the server's implementation (`dist/electron/core/input-injection/windows.js:47`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

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/electron/core/input-injection/windows.js

high Shell/command execution in server code (dist/electron/main.js)MTC-SRC-002

In the server's implementation (`dist/electron/main.js:1971`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

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/electron/main.js

high Shell/command execution in server code (dist/electron/modules/context-menu-detect.js)MTC-SRC-002

In the server's implementation (`dist/electron/modules/context-menu-detect.js:59`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

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/electron/modules/context-menu-detect.js

high Shell/command execution in server code (dist/electron/modules/platform/dpi.js)MTC-SRC-002

In the server's implementation (`dist/electron/modules/platform/dpi.js:32`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

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/electron/modules/platform/dpi.js

high Shell/command execution in server code (dist/electron/modules/platform/macos/ax.js)MTC-SRC-002

In the server's implementation (`dist/electron/modules/platform/macos/ax.js:13`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

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/electron/modules/platform/macos/ax.js

high Shell/command execution in server code (dist/electron/modules/platform/macos/capture.js)MTC-SRC-002

In the server's implementation (`dist/electron/modules/platform/macos/capture.js:13`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

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/electron/modules/platform/macos/capture.js

high Shell/command execution in server code (dist/electron/modules/platform/macos/launch.js)MTC-SRC-002

In the server's implementation (`dist/electron/modules/platform/macos/launch.js:19`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

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/electron/modules/platform/macos/launch.js

high Shell/command execution in server code (dist/electron/modules/platform/macos/window.js)MTC-SRC-002

In the server's implementation (`dist/electron/modules/platform/macos/window.js:26`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

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/electron/modules/platform/macos/window.js

high Shell/command execution in server code (dist/electron/modules/platform/shared.js)MTC-SRC-002

In the server's implementation (`dist/electron/modules/platform/shared.js:110`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

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/electron/modules/platform/shared.js

high Shell/command execution in server code (dist/electron/modules/platform/windows/ax.js)MTC-SRC-002

In the server's implementation (`dist/electron/modules/platform/windows/ax.js:44`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

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/electron/modules/platform/windows/ax.js

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

In the server's implementation (`dist/electron/modules/dictation.js:172`): 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: fetch('https://api.superbased.app/api/v1/ai/dictation-stt-config'

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/electron/modules/dictation.js

medium Hardcoded egress to an external endpoint (dist/headless/electron/modules/dictation.js)MTC-SRC-003

In the server's implementation (`dist/headless/electron/modules/dictation.js:172`): 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: fetch('https://api.superbased.app/api/v1/ai/dictation-stt-config'

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/headless/electron/modules/dictation.js

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

In the server's implementation (`dist/headless/headless/dictation-hotkey.js:172`): 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: fetch('https://api.superbased.app/api/v1/ai/dictation-stt-config'

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/headless/headless/dictation-hotkey.js

medium Untrusted input concatenated into a command sink (dist/electron/db/database.js)MTC-SRC-009

In the server's implementation (`dist/electron/db/database.js:208`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: exec(`ALTER TABLE captures ADD COLUMN ${col.name} ${

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/electron/db/database.js

medium Untrusted input concatenated into a command sink (dist/electron/main.js)MTC-SRC-009

In the server's implementation (`dist/electron/main.js:1973`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`osascript -e 'set the clipboard to POSIX file "${

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/electron/main.js

medium Untrusted input concatenated into a command sink (dist/electron/modules/context-menu-detect.js)MTC-SRC-009

In the server's implementation (`dist/electron/modules/context-menu-detect.js:102`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`powershell -ExecutionPolicy Bypass -File "${

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/electron/modules/context-menu-detect.js

medium Untrusted input concatenated into a command sink (dist/electron/modules/platform/shared.js)MTC-SRC-009

In the server's implementation (`dist/electron/modules/platform/shared.js:128`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`powershell -ExecutionPolicy Bypass -File "${

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/electron/modules/platform/shared.js

medium Untrusted input concatenated into a command sink (dist/electron/modules/platform/windows/session.js)MTC-SRC-009

In the server's implementation (`dist/electron/modules/platform/windows/session.js:49`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`powershell -NoProfile -Command "@(Get-Process -Name '${

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/electron/modules/platform/windows/session.js

medium Untrusted input concatenated into a command sink (dist/electron/modules/platform/windows/window.js)MTC-SRC-009

In the server's implementation (`dist/electron/modules/platform/windows/window.js:210`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`powershell -ExecutionPolicy Bypass -File "${script}" -Hwnd ${nativeId} -State ${state} -BX ${bx} -BY ${by} -BW ${bw} -BH ${

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/electron/modules/platform/windows/window.js

medium Untrusted input concatenated into a command sink (dist/electron/modules/window-activate.js)MTC-SRC-009

In the server's implementation (`dist/electron/modules/window-activate.js:209`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`powershell -ExecutionPolicy Bypass -File "${script}" -TargetHwnd ${

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/electron/modules/window-activate.js

medium Untrusted input concatenated into a command sink (dist/electron/modules/window-input.js)MTC-SRC-009

In the server's implementation (`dist/electron/modules/window-input.js:121`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`powershell -ExecutionPolicy Bypass -File "${script}" -Hwnd ${

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/electron/modules/window-input.js

medium Untrusted input concatenated into a command sink (dist/headless/electron/db/database.js)MTC-SRC-009

In the server's implementation (`dist/headless/electron/db/database.js:208`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: exec(`ALTER TABLE captures ADD COLUMN ${col.name} ${

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/headless/electron/db/database.js

medium Untrusted input concatenated into a command sink (dist/headless/electron/modules/context-menu-detect.js)MTC-SRC-009

In the server's implementation (`dist/headless/electron/modules/context-menu-detect.js:102`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`powershell -ExecutionPolicy Bypass -File "${

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/headless/electron/modules/context-menu-detect.js

medium Dynamic module load from a non-literal (dist/electron/core/config.js)MTC-SRC-005

In the server's implementation (`dist/electron/core/config.js:58`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: require(p)

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/electron/core/config.js

medium Dynamic module load from a non-literal (dist/electron/modules/api-server.js)MTC-SRC-005

In the server's implementation (`dist/electron/modules/api-server.js:2628`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: require(p)

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/electron/modules/api-server.js

medium Dynamic module load from a non-literal (dist/headless/electron/core/config.js)MTC-SRC-005

In the server's implementation (`dist/headless/electron/core/config.js:58`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: require(p)

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/headless/electron/core/config.js

medium Dynamic module load from a non-literal (dist/headless/electron/modules/api-server.js)MTC-SRC-005

In the server's implementation (`dist/headless/electron/modules/api-server.js:2628`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: require(p)

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/headless/electron/modules/api-server.js

medium Dynamic module load from a non-literal (dist/headless/headless/cli.js)MTC-SRC-005

In the server's implementation (`dist/headless/headless/cli.js:157`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: require(mcpPath)

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/headless/headless/cli.js

medium Dynamic module load from a non-literal (dist/headless/headless/doctor.js)MTC-SRC-005

In the server's implementation (`dist/headless/headless/doctor.js:175`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: require(name)

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/headless/headless/doctor.js

medium Dynamic module load from a non-literal (dist/headless/headless/tui-bridge.js)MTC-SRC-005

In the server's implementation (`dist/headless/headless/tui-bridge.js:75`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: require(s)

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/headless/headless/tui-bridge.js

Tools 72

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

  • superbased_galleryingests untrusted input
  • superbased_ui_dumpreads sensitive data
  • superbased_accessibility_treeno sensitive capability
  • superbased_aino sensitive capability
  • superbased_ai_usageno sensitive capability
  • superbased_annotateno sensitive capability
  • superbased_authno sensitive capability
  • superbased_ax_invokeno sensitive capability
  • superbased_baselineno sensitive capability
  • superbased_captureno sensitive capability
  • superbased_capture_imageno sensitive capability
  • superbased_capture_templateno sensitive capability
  • superbased_clickno sensitive capability
  • superbased_clipboardno sensitive capability
  • superbased_compress_textno sensitive capability
  • superbased_context_menu_selectno sensitive capability
  • superbased_describe_framesno sensitive capability
  • superbased_dialog_handleno sensitive capability
  • superbased_dictateno sensitive capability
  • superbased_dictation_historyno sensitive capability
  • superbased_diffno sensitive capability
  • superbased_display_listno sensitive capability
  • superbased_doctor_gui_automationno sensitive capability
  • superbased_dragno sensitive capability
  • superbased_drag_fileno sensitive capability
  • superbased_dry_runno sensitive capability
  • superbased_exportno sensitive capability
  • superbased_find_imageno sensitive capability
  • superbased_find_in_pageno sensitive capability
  • superbased_find_title_bar_drag_regionno sensitive capability
  • superbased_focus_windowno sensitive capability
  • superbased_form_fillno sensitive capability
  • superbased_gallery_imageno sensitive capability
  • superbased_gallery_updateno sensitive capability
  • superbased_healthno sensitive capability
  • superbased_hotkeyno sensitive capability
  • superbased_hoverno sensitive capability
  • superbased_launch_appno sensitive capability
  • superbased_licenseno sensitive capability
  • superbased_locateno sensitive capability
  • superbased_mouse_positionno sensitive capability
  • superbased_narrateno sensitive capability
  • superbased_ocrno sensitive capability
  • superbased_open_urlno sensitive capability
  • superbased_pixel_colorno sensitive capability
  • superbased_presetsno sensitive capability
  • superbased_projectno sensitive capability
  • superbased_recordingno sensitive capability
  • superbased_redactno sensitive capability
  • superbased_replayno sensitive capability
  • superbased_resize_windowno sensitive capability
  • superbased_screenshotno sensitive capability
  • superbased_scrollno sensitive capability
  • superbased_scroll_captureno sensitive capability
  • superbased_scroll_tono sensitive capability
  • superbased_sequenceno sensitive capability
  • superbased_sessionsno sensitive capability
  • superbased_settingsno sensitive capability
  • superbased_stt_statusno sensitive capability
  • superbased_tab_managementno sensitive capability
  • superbased_toolsno sensitive capability
  • superbased_transcribeno sensitive capability
  • superbased_tray_clickno sensitive capability
  • superbased_typeno sensitive capability
  • superbased_undo_lastno sensitive capability
  • superbased_virtual_desktopno sensitive capability
  • superbased_waitno sensitive capability
  • superbased_wait_forno sensitive capability
  • superbased_window_boundsno sensitive capability
  • superbased_window_listno sensitive capability
  • superbased_window_stateno sensitive capability
  • superbased_workspace_syncno sensitive capability

What this scan could not see

Versions

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.0.9 latest C 74/100 30 1.8.0 2026-07-23

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

Use the free API → How scoring works

More in Developer Tools