io.github.CloudCorpRecords/appbase
OCI · GHCR.IO/CLOUDCORPRECORDS/APPBASE · 2 COMPONENTS
Supabase projects, tables, SQL, migrations, and storage from your MCP client.
Available components
Last scanned (2 hours ago)
Scores higher than 41% of OCI servers
Category Databases
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1570 tokens (~56/item across 28 items; 28 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 38
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/appbase@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
apply_migration ~93
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).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the migration to record in the database. |
| project_id | string | yes | The reference ID of the Supabase project to apply the migration to. |
| query | string | yes | The SQL statements of the migration to apply. |
No output schema declared.
No examples provided.
create_branch ~79
Creates a new development branch for a Supabase project.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_cost_id | string | – | The cost confirmation ID authorizing the branch creation charge, if one was obtained. |
| name | string | yes | The name of the new development branch. |
| project_id | string | yes | The reference ID of the Supabase project to create the development branch in. |
No output schema declared.
No examples provided.
create_project ~88
Creates a new Supabase project.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_cost_id | string | – | The cost confirmation ID authorizing the project creation charge, if one was obtained. |
| name | string | yes | The name of the new Supabase project. |
| organization_id | string | yes | The ID of the organization to create the new project in. |
| region | string | – | The region to create the new project in. |
No output schema declared.
No examples provided.
create_storage_bucket ~110
Creates a new storage bucket in a Supabase project.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The name of the new storage bucket. |
| project_id | string | yes | The reference ID of the Supabase project to create the storage bucket in. |
| public | boolean | – | Whether the new storage bucket is publicly accessible. |
No output schema declared.
No examples provided.
delete_branch ~55
Deletes a development branch from a Supabase project.
| Name | Type | Req | Description |
|---|---|---|---|
| branch_id | string | yes | The ID of the development branch to delete. |
| project_id | string | yes | The reference ID of the Supabase project that owns the development branch. |
No output schema declared.
No examples provided.
deploy_edge_function ~123
Deploys an Edge Function to a Supabase project from inline files.
| Name | Type | Req | Description |
|---|---|---|---|
| entrypoint_path | string | – | The path of the entrypoint file for the Edge Function. |
| files | array | yes | 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 | yes | The name of the Edge Function to deploy. |
| project_id | string | yes | The reference ID of the Supabase project to deploy the Edge Function to. |
No output schema declared.
No examples provided.
execute_sql ~53
Executes raw SQL in the database.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project to run the SQL against. |
| query | string | yes | The raw SQL query to execute in the project's database. |
No output schema declared.
No examples provided.
generate_typescript_types ~62
Generates TypeScript types based on the database schema.
| Name | Type | Req | Description |
|---|---|---|---|
| included_schemas | array | – | The database schemas to include when generating the TypeScript types. |
| project_id | string | yes | The reference ID of the Supabase project to generate TypeScript types for. |
No output schema declared.
No examples provided.
get_advisors ~65
Gets advisory notices for a Supabase project, by type: security or performance.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose advisors are retrieved. |
| type | string | yes | The type of advisory notices to get, either security or performance. |
No output schema declared.
No examples provided.
get_edge_function ~55
Gets details for an Edge Function by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| function_slug | string | yes | The slug of the Edge Function to retrieve. |
| project_id | string | yes | The reference ID of the Supabase project that owns the Edge Function. |
No output schema declared.
No examples provided.
get_logs ~87
Gets logs for a Supabase project by service (api, postgres, edge-function, auth, storage, realtime, or branch-action).
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose logs are retrieved. |
| service | string | yes | The service to get logs for, one of api, postgres, edge-function, auth, storage, realtime, or branch-action. |
No output schema declared.
No examples provided.
get_organization ~31
Gets details for an organization.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the organization to retrieve details for. |
No output schema declared.
No examples provided.
get_project ~30
Gets details for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the project to retrieve details for. |
No output schema declared.
No examples provided.
get_project_url ~40
Gets the API URL for a Supabase project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose API URL is returned. |
No output schema declared.
No examples provided.
get_publishable_keys ~49
Gets the publishable and anon API keys for a Supabase project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose publishable and anon API keys are returned. |
No output schema declared.
No examples provided.
list_branches ~40
Lists all development branches for a Supabase project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose development branches are listed. |
No output schema declared.
No examples provided.
list_edge_functions ~40
Lists all Edge Functions in a Supabase project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose Edge Functions are listed. |
No output schema declared.
No examples provided.
list_extensions ~36
Lists all extensions in the database.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose database extensions are listed. |
No output schema declared.
No examples provided.
list_migrations ~36
Lists all migrations in the database.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose migrations are listed. |
No output schema declared.
No examples provided.
list_organizations ~20
Lists all organizations that the user is a member of.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_projects ~17
Lists all Supabase projects for the user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_storage_buckets ~41
Lists all storage buckets in a Supabase project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose storage buckets are listed. |
No output schema declared.
No examples provided.
list_tables ~57
Lists all tables within the specified schemas.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | 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. |
No output schema declared.
No examples provided.
merge_branch ~60
Merges migrations and edge functions from a development branch into production.
| Name | Type | Req | Description |
|---|---|---|---|
| branch_id | string | yes | The ID of the development branch to merge into production. |
| project_id | string | yes | The reference ID of the Supabase project that owns the development branch. |
No output schema declared.
No examples provided.
pause_project ~31
Pauses a project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project to pause. |
No output schema declared.
No examples provided.
rebase_branch ~63
Rebases a development branch on its parent, applying newer migrations.
| Name | Type | Req | Description |
|---|---|---|---|
| branch_id | string | yes | The ID of the development branch to rebase on its parent. |
| project_id | string | yes | The reference ID of the Supabase project that owns the development branch. |
No output schema declared.
No examples provided.
reset_branch ~78
Resets a development branch to its parent state, optionally at a migration version.
| Name | Type | Req | Description |
|---|---|---|---|
| branch_id | string | yes | The ID of the development branch to reset. |
| migration_version | string | – | The optional migration version to reset the branch to. |
| project_id | string | yes | The reference ID of the Supabase project that owns the development branch. |
No output schema declared.
No examples provided.
restore_project ~31
Restores a project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project to restore. |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/cloudcorprecords/appbase
claude mcp add cloudcorprecords-appbase -- docker run --rm -i ghcr.io/cloudcorprecords/appbase:0.1.0
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.