pg-perf-mcp vs VillageSQL Skills
Side-by-side comparison
These work together
They provide different kinds of components and share a runtime, so they can be installed together.
- Choose pg-perf-mcp if you use MCP. It is the only one here that lists it. Based on: Works with.
- Choose VillageSQL Skills if you use Agent Plugin or Codex. It is the only one here that lists them. Based on: Works with.
- Choose VillageSQL Skills if you need skills. The others list none. Based on: Skills.
- Choose pg-perf-mcp if you need MCP servers. The others list none. Based on: MCP servers.
Suggestions use only facts every plugin here reports. They never use Trust Score totals, memberships or paid placement.
Showing 10 of 14 rows that differ.
Show all rows| Plugin | pg-perf-mcp gouranshul/pg-perf | VillageSQL Skills villagesql/villagesql |
|---|---|---|
| Works with | Claude Code, MCP | Agent Plugin, Claude Code, Codex |
| Trust score | 65/100 | 69/100 |
| Security scan | Caution (59/100, 4 findings) | Needs review (71/100, 6 findings) |
| Directory listings | Listed in 0 of 5 checked | Listed in 3 of 5 checked |
| Skills | 0 | 3 |
| MCP servers | 1 | 0 |
| Version | 0.1.0 | 1.0.0 |
| Last updated | 2026-10-15 | 2026-10-14 |
| Developer | gouranshul | VillageSQL |
| Category | Tools & Integrations | Development & Workflow |
Facts come from the public registry record. Directory listings count the public directory lists HOL has read; release integrity is what HOL recorded each channel serving. “Not reported” means there is no value yet; it is not treated as no or zero. Paid placement and HOL memberships do not change any value shown here.