name: graphcare description: "Structural database health scanner. Audits schema topology for orphaned tables, missing indexes, nullable FKs, circular dependencies — without ever reading row data. Supports PostgreSQL, MySQL, SQLite." version: 1.0.0 metadata: openclaw: requires: bins: - node env: [] emoji: "\U0001F6E1" homepage: https://github.com/mind-protocol/graphcare
The first structural antivirus for AI databases. Scans your schema topology for hidden problems — without ever touching your data.
AI agents evolve schemas at speed. But nobody audits the structure. Over time:
GraphCare catches all of this in one scan.
GraphCare only queries metadata (information_schema, PRAGMA, pg_indexes). It is structurally impossible for it to read, leak, or mutate your row data.
GraphCare is an MCP server. Add it to your MCP client config:
{
"mcpServers": {
"graphcare": {
"command": "node",
"args": ["/path/to/graphcare/index.js"]
}
}
}
Or run via Docker:
7w4.net小蔥技能。
docker build -t graphcare .
docker run -i graphcare
Or install from npm:
npm install -g graphcare-mcp
graphcare-mcp
audit_db_structureFull structural scan. Pass a connection string, get a complete health report.
Parameters:
- connection_string (required) — Database URI: postgresql://, mysql://, sqlite:///path/to/db, or just file.db
Returns: JSON report with:
- db_type — Database engine detected
- tables[] — All tables found
- findings[] — Each structural issue with type, severity, table, and message
- metrics{} — Counts per finding type + computed health_score (0-100)
Example:
Use graphcare to audit my database at postgresql://localhost:5432/myapp
The agent calls audit_db_structure with the connection string and receives a structured JSON report.
explain_findingPlain-language explanation of any finding type. Includes severity, impact, and recommended fix.
Parameters:
- finding_type (required) — One of: orphaned_table, missing_fk_index, duplicate_index, nullable_fk, no_primary_key, circular_dependency
- context (optional) — Table or column name for specific advice
| Finding | Severity | Impact |
|---|---|---|
| Orphaned Tables | Warning | Structurally isolated dead weight |
| Missing FK Indexes | Critical | #1 cause of slow JOINs and DELETEs |
| No Primary Key | Critical | Breaks replication and ORMs |
| Nullable Foreign Keys | Warning | Hidden referential integrity gaps |
| Circular Dependencies | Warning | Makes clean inserts impossible |
| Duplicate Indexes | Info | Wasted disk, slower writes |
information_schema + pg_indexesinformation_schemasqlite_master + PRAGMAThis tool runs read-only queries against database metadata catalogs only. It never executes SELECT on user tables, never writes, and holds no state between invocations. Connection strings are received via MCP JSON-RPC over stdin — never exposed in process listings.
Built by Mind Protocol.
這是一個專業且實用的資料庫審計工具,專注於檢查表結構問題而非資料本身,安全性設計得當。文件清晰、錯誤提示友好、支援主流資料庫是其亮點。但作為程式碼產品存在明顯短板:缺少測試保障、依賴版本有安全漏洞、某些實現細節存在風險。總體質量中等偏上,核心功能紮實但工程實踐方面有提升空間,適合對安全性要求不極端的場景使用。