# io.github.CloudCorpRecords/appbase (oci · ghcr.io/cloudcorprecords/appbase)

Supabase projects, tables, SQL, migrations, and storage from your MCP client.

- Trust score: 40/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/appbase`: 65/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-appbase/reneturcios-appbase.md), [page](https://verifymcp.io/servers/cloudcorprecords-appbase/reneturcios-appbase)
- oci · `ghcr.io/cloudcorprecords/appbase`: 40/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-appbase/ghcr-io-cloudcorprecords-appbase.md), [page](https://verifymcp.io/servers/cloudcorprecords-appbase/ghcr-io-cloudcorprecords-appbase)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/appbase`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1570 tokens (~56/item across 28 items; 28 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_sql" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/appbase MCP server?

io.github.CloudCorpRecords/appbase runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/appbase:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-appbase -- docker run --rm -i ghcr.io/cloudcorprecords/appbase:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-appbase": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/appbase:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-appbase": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/appbase:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-appbase -- docker run --rm -i ghcr.io/cloudcorprecords/appbase:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-appbase": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/appbase:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-appbase:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/appbase:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-appbase": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/appbase:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-appbase": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/appbase:0.1.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 38)

First indexed and scored.

## MCP tools (28)

### `list_tables` (~57 tokens)

Lists all tables within the specified schemas.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project whose tables are listed.
- `schemas` (array): The database schemas to list tables from, defaulting to public when omitted.

### `list_extensions` (~36 tokens)

Lists all extensions in the database.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project whose database extensions are listed.

### `list_migrations` (~36 tokens)

Lists all migrations in the database.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project whose migrations are listed.

### `execute_sql` (~53 tokens)

Executes raw SQL in the database.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project to run the SQL against.
- `query` (string, required): The raw SQL query to execute in the project's database.

### `apply_migration` (~93 tokens)

Applies a SQL migration to the database. SQL passed to this tool will be tracked within the database, so use this for DDL operations (schema changes).

Input parameters:

- `name` (string, required): The name of the migration to record in the database.
- `project_id` (string, required): The reference ID of the Supabase project to apply the migration to.
- `query` (string, required): The SQL statements of the migration to apply.

### `get_logs` (~87 tokens)

Gets logs for a Supabase project by service (api, postgres, edge-function, auth, storage, realtime, or branch-action).

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project whose logs are retrieved.
- `service` (string, required): The service to get logs for, one of api, postgres, edge-function, auth, storage, realtime, or branch-action.

### `get_advisors` (~65 tokens)

Gets advisory notices for a Supabase project, by type: security or performance.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project whose advisors are retrieved.
- `type` (string, required): The type of advisory notices to get, either security or performance.

### `get_project_url` (~40 tokens)

Gets the API URL for a Supabase project.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project whose API URL is returned.

### `get_publishable_keys` (~49 tokens)

Gets the publishable and anon API keys for a Supabase project.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project whose publishable and anon API keys are returned.

### `generate_typescript_types` (~62 tokens)

Generates TypeScript types based on the database schema.

Input parameters:

- `included_schemas` (array): The database schemas to include when generating the TypeScript types.
- `project_id` (string, required): The reference ID of the Supabase project to generate TypeScript types for.

### `list_edge_functions` (~40 tokens)

Lists all Edge Functions in a Supabase project.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project whose Edge Functions are listed.

### `get_edge_function` (~55 tokens)

Gets details for an Edge Function by slug.

Input parameters:

- `function_slug` (string, required): The slug of the Edge Function to retrieve.
- `project_id` (string, required): The reference ID of the Supabase project that owns the Edge Function.

### `deploy_edge_function` (~123 tokens)

Deploys an Edge Function to a Supabase project from inline files.

Input parameters:

- `entrypoint_path` (string): The path of the entrypoint file for the Edge Function.
- `files` (array, required): The inline files that make up the Edge Function, each with a name and content.
- `import_map_path` (string): The path of the import map file for the Edge Function.
- `name` (string, required): The name of the Edge Function to deploy.
- `project_id` (string, required): The reference ID of the Supabase project to deploy the Edge Function to.

### `list_storage_buckets` (~41 tokens)

Lists all storage buckets in a Supabase project.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project whose storage buckets are listed.

### `create_storage_bucket` (~110 tokens)

Creates a new storage bucket in a Supabase project.

Input parameters:

- `allowed_mime_types` (array): The MIME types allowed for files uploaded to the bucket.
- `file_size_limit` (number): The maximum file size allowed for uploads to the bucket.
- `name` (string, required): The name of the new storage bucket.
- `project_id` (string, required): The reference ID of the Supabase project to create the storage bucket in.
- `public` (boolean): Whether the new storage bucket is publicly accessible.

### `list_branches` (~40 tokens)

Lists all development branches for a Supabase project.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project whose development branches are listed.

### `create_branch` (~79 tokens)

Creates a new development branch for a Supabase project.

Input parameters:

- `confirm_cost_id` (string): The cost confirmation ID authorizing the branch creation charge, if one was obtained.
- `name` (string, required): The name of the new development branch.
- `project_id` (string, required): The reference ID of the Supabase project to create the development branch in.

### `delete_branch` (~55 tokens)

Deletes a development branch from a Supabase project.

Input parameters:

- `branch_id` (string, required): The ID of the development branch to delete.
- `project_id` (string, required): The reference ID of the Supabase project that owns the development branch.

### `merge_branch` (~60 tokens)

Merges migrations and edge functions from a development branch into production.

Input parameters:

- `branch_id` (string, required): The ID of the development branch to merge into production.
- `project_id` (string, required): The reference ID of the Supabase project that owns the development branch.

### `reset_branch` (~78 tokens)

Resets a development branch to its parent state, optionally at a migration version.

Input parameters:

- `branch_id` (string, required): The ID of the development branch to reset.
- `migration_version` (string): The optional migration version to reset the branch to.
- `project_id` (string, required): The reference ID of the Supabase project that owns the development branch.

### `rebase_branch` (~63 tokens)

Rebases a development branch on its parent, applying newer migrations.

Input parameters:

- `branch_id` (string, required): The ID of the development branch to rebase on its parent.
- `project_id` (string, required): The reference ID of the Supabase project that owns the development branch.

### `list_projects` (~17 tokens)

Lists all Supabase projects for the user.

### `get_project` (~30 tokens)

Gets details for a project.

Input parameters:

- `id` (string, required): The ID of the project to retrieve details for.

### `create_project` (~88 tokens)

Creates a new Supabase project.

Input parameters:

- `confirm_cost_id` (string): The cost confirmation ID authorizing the project creation charge, if one was obtained.
- `name` (string, required): The name of the new Supabase project.
- `organization_id` (string, required): The ID of the organization to create the new project in.
- `region` (string): The region to create the new project in.

### `pause_project` (~31 tokens)

Pauses a project.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project to pause.

### `restore_project` (~31 tokens)

Restores a project.

Input parameters:

- `project_id` (string, required): The reference ID of the Supabase project to restore.

### `list_organizations` (~20 tokens)

Lists all organizations that the user is a member of.

### `get_organization` (~31 tokens)

Gets details for an organization.

Input parameters:

- `id` (string, required): The ID of the organization to retrieve details for.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-appbase/ghcr-io-cloudcorprecords-appbase#diagnostics

## Score history

- 2026-11-05: 40
- 2026-11-04: 40
- 2026-11-03: 39
- 2026-11-02: 39
- 2026-11-01: 38

## Common questions

### What is the io.github.CloudCorpRecords/appbase MCP server?

io.github.CloudCorpRecords/appbase is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/appbase. Supabase projects, tables, SQL, migrations, and storage from your MCP client. This page covers its container image (ghcr.io/cloudcorprecords/appbase).

### Is the io.github.CloudCorpRecords/appbase MCP server safe to use?

io.github.CloudCorpRecords/appbase scores 40 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.CloudCorpRecords/appbase MCP server expose?

io.github.CloudCorpRecords/appbase exposes 28 tools: list_tables, list_extensions, list_migrations, execute_sql, apply_migration, and 23 more. Their descriptions and schemas cost roughly 1,570 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/appbase MCP server still maintained?

io.github.CloudCorpRecords/appbase is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.CloudCorpRecords/appbase MCP server under?

io.github.CloudCorpRecords/appbase declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/appbase
- Repository: https://github.com/CloudCorpRecords/appbase
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-appbase/ghcr-io-cloudcorprecords-appbase.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-appbase/ghcr-io-cloudcorprecords-appbase.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-appbase/ghcr-io-cloudcorprecords-appbase