Pocketbase Mcp Bridge MCP Server

pocketbase-mcp-bridge npm v1.0.0 Source verified

Published by nestebe — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Complete Model Context Protocol (MCP) server for PocketBase — collections, records, auth, files, logs, settings, backups, crons and more.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/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 = 94/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 − 6 = 94. 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

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

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: download_backup → get_logs_stats ⇒ send_raw_request. Untrusted input is ingested, private data is read, and it can be sent to an external sink — and at least one leg is a direct schema wire (⇒), where a producer's output drops straight into a free-text parameter of the next tool, so the chain needs little agent cooperation. Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow download_backup → get_logs_stats → send_raw_request

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

Tool "unlink_external_auth" can write, overwrite or delete files (keyword "unlink" 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 unlink_external_auth

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

Tool "unlink_external_auth" 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 unlink_external_auth

Tools 55

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

  • download_backupingests untrusted input
  • download_fileingests untrusted input
  • get_backup_download_urlingests untrusted input
  • get_collectioningests untrusted input
  • get_full_record_listingests untrusted input
  • get_logingests untrusted input
  • get_logs_statsreads sensitive data
  • get_recordingests untrusted input
  • get_settingsingests untrusted input
  • send_raw_requestnetwork egress
Show 45 more tools ↓
  • unlink_external_authwrites files
  • auth_infono sensitive capability
  • auth_with_otpno sensitive capability
  • auth_with_passwordno sensitive capability
  • batchno sensitive capability
  • confirm_email_changeno sensitive capability
  • confirm_password_resetno sensitive capability
  • confirm_verificationno sensitive capability
  • create_backupno sensitive capability
  • create_collectionno sensitive capability
  • create_recordno sensitive capability
  • create_superuserno sensitive capability
  • delete_backupno sensitive capability
  • delete_collectionno sensitive capability
  • delete_recordno sensitive capability
  • delete_superuserno sensitive capability
  • generate_apple_client_secretno sensitive capability
  • get_collection_scaffoldsno sensitive capability
  • get_file_tokenno sensitive capability
  • get_file_urlno sensitive capability
  • get_first_recordno sensitive capability
  • health_checkno sensitive capability
  • impersonateno sensitive capability
  • import_collectionsno sensitive capability
  • list_auth_methodsno sensitive capability
  • list_backupsno sensitive capability
  • list_collectionsno sensitive capability
  • list_cronsno sensitive capability
  • list_external_authsno sensitive capability
  • list_logsno sensitive capability
  • list_recordsno sensitive capability
  • list_superusersno sensitive capability
  • request_otpno sensitive capability
  • request_password_resetno sensitive capability
  • request_verificationno sensitive capability
  • restore_backupno sensitive capability
  • run_cronno sensitive capability
  • test_emailno sensitive capability
  • test_s3no sensitive capability
  • truncate_collectionno sensitive capability
  • update_collectionno sensitive capability
  • update_recordno sensitive capability
  • update_settingsno sensitive capability
  • update_superuserno sensitive capability
  • upload_backupno 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
v1.0.0 latest A 94/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 · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/pocketbase-mcp-bridge/badge.svg)](https://mcptrustchecker.com/registry/pocketbase-mcp-bridge)
HTML
<a href="https://mcptrustchecker.com/registry/pocketbase-mcp-bridge"><img src="https://mcptrustchecker.com/registry/pocketbase-mcp-bridge/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/pocketbase-mcp-bridge/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 pocketbase-mcp-bridge --online

Use the free API → How scoring works

More in Databases