Baasix MCP Server

@tspvivek/baasix-mcp-server npm v0.1.7

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

Model Context Protocol (MCP) server for Baasix Backend-as-a-Service - provides 40+ tools for schema management, CRUD operations with 50+ filter operators, relationships, permissions, files, workflows, and more

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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
High
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 = 93/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 − 7 = 93. 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
−6 capability blast radius (high) — 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 3

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([baasix_list_files]) and tools that can send data out ([baasix_send_notification]) are exposed together. An agent can move private data to the sink.

Evidence: sources [baasix_list_files] → sinks [baasix_send_notification]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow baasix_list_files → baasix_send_notification

medium Tool "baasix_delete_file" can modify the filesystemMTC-CAP-002

Tool "baasix_delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool baasix_delete_file

low Mutating tool "baasix_delete_file" declares no destructiveHintMTC-CAP-005

Tool "baasix_delete_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool baasix_delete_file

Tools 57

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

  • baasix_delete_filewrites files
  • baasix_list_filesreads sensitive data
  • baasix_send_notificationnetwork egress
  • baasix_add_indexno sensitive capability
  • baasix_auth_statusno sensitive capability
  • baasix_collection_statsno sensitive capability
  • baasix_create_itemno sensitive capability
  • baasix_create_permissionno sensitive capability
  • baasix_create_relationshipno sensitive capability
  • baasix_create_schemano sensitive capability
Show 47 more tools ↓
  • baasix_delete_itemno sensitive capability
  • baasix_delete_permissionno sensitive capability
  • baasix_delete_relationshipno sensitive capability
  • baasix_delete_schemano sensitive capability
  • baasix_export_schemasno sensitive capability
  • baasix_generate_reportno sensitive capability
  • baasix_get_current_userno sensitive capability
  • baasix_get_file_infono sensitive capability
  • baasix_get_itemno sensitive capability
  • baasix_get_permissionno sensitive capability
  • baasix_get_permissionsno sensitive capability
  • baasix_get_schemano sensitive capability
  • baasix_get_settingsno sensitive capability
  • baasix_get_templateno sensitive capability
  • baasix_get_user_tenantsno sensitive capability
  • baasix_import_schemasno sensitive capability
  • baasix_list_itemsno sensitive capability
  • baasix_list_notificationsno sensitive capability
  • baasix_list_permissionsno sensitive capability
  • baasix_list_rolesno sensitive capability
  • baasix_list_schemasno sensitive capability
  • baasix_list_templatesno sensitive capability
  • baasix_loginno sensitive capability
  • baasix_logoutno sensitive capability
  • baasix_mark_notification_seenno sensitive capability
  • baasix_realtime_collectionsno sensitive capability
  • baasix_realtime_configno sensitive capability
  • baasix_realtime_disableno sensitive capability
  • baasix_realtime_enableno sensitive capability
  • baasix_realtime_statusno sensitive capability
  • baasix_refresh_authno sensitive capability
  • baasix_register_userno sensitive capability
  • baasix_reload_permissionsno sensitive capability
  • baasix_remove_indexno sensitive capability
  • baasix_send_inviteno sensitive capability
  • baasix_send_magic_linkno sensitive capability
  • baasix_server_infono sensitive capability
  • baasix_sort_itemsno sensitive capability
  • baasix_switch_tenantno sensitive capability
  • baasix_update_itemno sensitive capability
  • baasix_update_permissionno sensitive capability
  • baasix_update_permissionsno sensitive capability
  • baasix_update_relationshipno sensitive capability
  • baasix_update_schemano sensitive capability
  • baasix_update_settingsno sensitive capability
  • baasix_update_templateno sensitive capability
  • baasix_verify_inviteno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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

Use the free API → How scoring works

More in Cloud & DevOps