io.github.CloudCorpRecords/pgcloud
NPM · @RENETURCIOS/PGCLOUD · 2 COMPONENTS
Neon Postgres projects, branches, SQL, and migrations from your MCP client.
Available components
Last scanned (23 hours ago)
Scores higher than 33% of npm 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1915 tokens (~95/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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; "delete_project" implies "delete" 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 20 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 64
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 4 Nov 2026 · Analysed npm/@reneturcios/pgcloud@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 | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
complete_database_migration ~108
Complete a database migration when the user confirms the migration is ready to be applied to the main branch.
| Name | Type | Req | Description |
|---|---|---|---|
| databaseName | string | – | Optional name of the database to apply the migration to; when omitted, the database recorded when the migration was prepared is used. |
| migrationId | string | yes | ID of the prepared migration session returned by prepare_database_migration. |
| projectId | string | yes | ID of the Neon project the migration was prepared for; must match the prepared migration's project. |
No output schema declared.
No examples provided.
complete_query_tuning ~111
Complete a query tuning session by either applying the changes to the main branch or discarding them.
| Name | Type | Req | Description |
|---|---|---|---|
| applyChanges | boolean | yes | Whether to apply the tuning session's changes to the original branch (true) or discard them (false); the temporary branch is deleted either way. |
| projectId | string | yes | ID of the Neon project the tuning session was prepared for; must match the session's project. |
| tuningId | string | yes | ID of the query tuning session returned by prepare_query_tuning. |
No output schema declared.
No examples provided.
create_branch ~88
Create a branch in a Neon project
| Name | Type | Req | Description |
|---|---|---|---|
| branchName | string | – | Optional name for the new branch; when omitted, Neon assigns a default name. |
| parentBranchId | string | – | Optional ID of the branch to copy from; when omitted, the branch is created from the project's default branch. |
| projectId | string | yes | ID of the Neon project in which to create the branch. |
No output schema declared.
No examples provided.
create_project ~81
Create a new Neon project.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional name for the new Neon project; when omitted, Neon assigns a default name. |
| org_id | string | – | Optional Neon organization ID that will own the new project. |
| region_id | string | – | Optional Neon region ID in which to create the project, such as aws-us-east-1. |
No output schema declared.
No examples provided.
delete_branch ~47
Delete a branch from a Neon project
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | yes | ID of the branch to delete. |
| projectId | string | yes | ID of the Neon project that owns the branch. |
No output schema declared.
No examples provided.
delete_project ~34
Delete a Neon project
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | ID of the Neon project to delete, together with everything in it. |
No output schema declared.
No examples provided.
describe_branch ~68
Get a tree view of all objects in a branch, including databases, schemas, tables, views, and functions
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | yes | ID of the branch to describe, including the databases it holds. |
| projectId | string | yes | ID of the Neon project that owns the branch. |
No output schema declared.
No examples provided.
describe_project ~29
Describes a Neon project
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | ID of the Neon project to describe. |
No output schema declared.
No examples provided.
describe_table_schema ~105
Describe the schema of a table in a Neon database
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | – | Optional ID of the branch containing the table; when omitted, the project's default branch is used. |
| databaseName | string | – | Optional name of the database containing the table; when omitted, the project's default database is used. |
| projectId | string | yes | ID of the Neon project that owns the table. |
| tableName | string | yes | Name of the table whose columns to describe. |
No output schema declared.
No examples provided.
explain_sql_statement ~133
Describe the PostgreSQL query execution plan for a SQL statement by running EXPLAIN in the database
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | – | Optional ID of the branch to explain against; when omitted, the project's default branch is used. |
| databaseName | string | – | Optional name of the database to explain against; when omitted, the project's default database is used. |
| projectId | string | yes | ID of the Neon project that owns the database. |
| sql | string | yes | The SQL statement whose PostgreSQL execution plan to return, run under EXPLAIN (ANALYZE, BUFFERS, FORMAT JSON). |
No output schema declared.
No examples provided.
get_connection_string ~157
Get a PostgreSQL connection string for a Neon database with all parameters being optional
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | – | Optional ID of the branch to connect to; when omitted, the project's default branch is used. |
| databaseName | string | – | Optional name of the database to connect to; when omitted, the project's default database is used. |
| pooled | boolean | – | Optional flag: when true, return a pooled connection string (through Neon's connection pooler); when false or omitted, return a direct connection string. |
| projectId | string | yes | ID of the Neon project whose connection string to return. |
| roleName | string | – | Optional name of the database role to connect as; when omitted, the default role is used. |
No output schema declared.
No examples provided.
get_database_tables ~88
Get all tables in a Neon database
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | – | Optional ID of the branch whose tables to list; when omitted, the project's default branch is used. |
| databaseName | string | – | Optional name of the database whose tables to list; when omitted, the project's default database is used. |
| projectId | string | yes | ID of the Neon project that owns the database. |
No output schema declared.
No examples provided.
list_branch_computes ~74
List compute endpoints for a project or a specific branch, including compute ID, type, and size.
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | – | Optional ID of a branch; when given, only compute endpoints for that branch are listed. |
| projectId | string | yes | ID of the Neon project whose compute endpoints to list. |
No output schema declared.
No examples provided.
list_organizations ~42
List all organizations that the current user has access to, optionally filtered by a search term.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Optional search term to filter organizations by name. |
No output schema declared.
No examples provided.
list_projects ~69
List all Neon projects in your account.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of Neon projects to return. |
| org_id | string | – | Optional Neon organization ID; when given, only projects belonging to that organization are listed. |
| search | string | – | Optional search term to filter projects by name. |
No output schema declared.
No examples provided.
list_slow_queries ~122
List slow queries from pg_stat_statements, ordered by mean execution time.
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | – | Optional ID of the branch to inspect; when omitted, the project's default branch is used. |
| databaseName | string | – | Optional name of the database to inspect; when omitted, the project's default database is used. |
| limit | number | – | Optional maximum number of slow queries to return, clamped to between 1 and 100; defaults to 10. |
| projectId | string | yes | ID of the Neon project that owns the database. |
No output schema declared.
No examples provided.
prepare_database_migration ~145
Perform a database schema migration by executing the given SQL on a temporary branch for safety, ready to complete onto the main branch.
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | – | Optional ID of the branch to migrate; the temporary branch is created from it and completion applies the migration back to it. When omitted, the project's default branch is used. |
| databaseName | string | – | Optional name of the database to migrate; when omitted, the project's default database is used. |
| migrationSql | string | yes | The migration SQL to test on a temporary branch before it is applied to the original branch. |
| projectId | string | yes | ID of the Neon project that owns the database to migrate. |
No output schema declared.
No examples provided.
prepare_query_tuning ~141
Analyze a slow query or DML statement on a temporary branch, returning its execution plan to suggest optimizations.
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | – | Optional ID of the branch to tune against; the temporary tuning branch is created from it. When omitted, the project's default branch is used. |
| databaseName | string | – | Optional name of the database the statement runs against; when omitted, the project's default database is used. |
| projectId | string | yes | ID of the Neon project that owns the database. |
| sql | string | yes | The slow query or DML statement to analyze on a temporary branch; its execution plan is returned to suggest optimizations. |
No output schema declared.
No examples provided.
run_sql ~130
Execute a single SQL statement against a Neon database.
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | – | Optional ID of the branch to run against; when omitted, the project's default branch is used. |
| databaseName | string | – | Optional name of the database to run against; when omitted, the project's default database is used. |
| projectId | string | yes | ID of the Neon project that owns the database. |
| roleName | string | – | Optional name of the database role to run as; when omitted, the default role is used. |
| sql | string | yes | The single SQL statement to execute against the Neon database. |
No output schema declared.
No examples provided.
run_sql_transaction ~143
Execute a SQL transaction against a Neon database, should be used for multiple SQL statements.
| Name | Type | Req | Description |
|---|---|---|---|
| branchId | string | – | Optional ID of the branch to run against; when omitted, the project's default branch is used. |
| databaseName | string | – | Optional name of the database to run against; when omitted, the project's default database is used. |
| projectId | string | yes | ID of the Neon project that owns the database. |
| roleName | string | – | Optional name of the database role to run as; when omitted, the default role is used. |
| sql | array | yes | Array of SQL statements to execute together in a single transaction against the Neon database. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/pgcloud MCP server?
io.github.CloudCorpRecords/pgcloud runs locally as an npm package, launched with npx -y @reneturcios/pgcloud. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/pgcloud
claude mcp add cloudcorprecords-pgcloud -- npx -y @reneturcios/pgcloud
What is the io.github.CloudCorpRecords/pgcloud MCP server?
io.github.CloudCorpRecords/pgcloud is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/pgcloud. Neon Postgres projects, branches, SQL, and migrations from your MCP client. This page covers its npm package (@reneturcios/pgcloud).
Is the io.github.CloudCorpRecords/pgcloud MCP server safe to use?
io.github.CloudCorpRecords/pgcloud scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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/pgcloud MCP server expose?
io.github.CloudCorpRecords/pgcloud exposes 20 tools: list_projects, describe_project, create_project, delete_project, create_branch, and 15 more. Their descriptions and schemas cost roughly 1,915 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/pgcloud MCP server still maintained?
io.github.CloudCorpRecords/pgcloud is still listed as active in the MCP registry. We last reached this channel on 4 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/pgcloud MCP server under?
io.github.CloudCorpRecords/pgcloud declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.