io.github.Madia333/lintbase-mcp
NPM · LINTBASE-MCP · SCANNED SEP 20
Real-time Firestore schema context for AI coding agents. Stop hallucinating field names.
Available components
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 Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 10.0.0, reached via firebase-admin > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 83 of 244 dependencies flagged as unhealthy (2 deprecated). 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 78 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 474 tokens (~158/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the io.github.Madia333/lintbase-mcp server?
io.github.Madia333/lintbase-mcp runs locally as an npm package, launched with npx -y lintbase-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · lintbase-mcp
claude mcp add madia333-lintbase-mcp -- npx -y lintbase-mcp
{
"mcpServers": {
"madia333-lintbase-mcp": {
"command": "npx",
"args": [
"-y",
"lintbase-mcp"
]
}
}
} {
"servers": {
"madia333-lintbase-mcp": {
"command": "npx",
"args": [
"-y",
"lintbase-mcp"
]
}
}
} codex mcp add madia333-lintbase-mcp -- npx -y lintbase-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"madia333-lintbase-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"lintbase-mcp"
],
"enabled": true
}
}
} openclaw mcp add madia333-lintbase-mcp --command npx --arg -y --arg lintbase-mcp
mcp_servers:
madia333-lintbase-mcp:
command: "npx"
args: ["-y", "lintbase-mcp"] {
"McpServers": {
"madia333-lintbase-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"lintbase-mcp"
]
}
}
} assistant mcp add madia333-lintbase-mcp -t stdio -c npx -a -y lintbase-mcp
{
"mcpServers": {
"madia333-lintbase-mcp": {
"command": "npx",
"args": [
"-y",
"lintbase-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −2
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.83 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −2
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/lintbase-mcp@0.1.3
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-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 244 packages
| Packages resolved | 244 |
|---|---|
| Deprecated | 2 |
| Stale | 81 |
| 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 →
lintbase_get_issues LintBase Get Issues ~196
Runs all LintBase analyzers and returns a filtered list of issues. Use this for targeted questions like "any errors in users?", "schema issues only?", or "all security problems?". Lighter than lintbase_scan — returns only actionable issues, no summary metadata. Filter by severity (error/warning/info), collection name, or rule prefix (schema/, security/, perf/, cost/).
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Filter to a single collection name. Omit to scan all collections. |
| keyPath | string | yes | Absolute or relative path to the Firebase service account JSON file. |
| rule | string | – | Filter by rule prefix, e.g. "schema/" returns only schema drift issues, "security/" only security issues. |
| sampleSize | integer | – | Max documents to sample per collection (default: 50). |
| severity | string | – | Filter by severity. Omit to return all severities. |
No output schema declared.
No examples provided.
lintbase_get_schema LintBase Get Schema ~149
Returns the ground-truth schema of your Firestore collections by sampling real documents. For each collection you get field names, observed types, and presence rates. Use this BEFORE writing any database code to avoid hallucinating field names. Stable fields (≥80% presence, single type) are safe to use. Fields marked with a note need attention (drift, sparse, or optional).
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Name of a single collection to inspect. Omit to get the schema of ALL collections. |
| keyPath | string | yes | Absolute or relative path to the Firebase service account JSON file. |
| sampleSize | integer | – | Max documents to sample per collection (default: 50). |
No output schema declared.
No examples provided.
lintbase_scan LintBase Full Scan ~129
Runs a full LintBase scan against a Firestore database. Detects schema drift, security issues, performance problems, and cost leaks. Returns a structured report with a risk score and actionable issues. Use this before writing any database-related code to get ground-truth schema context.
| Name | Type | Req | Description |
|---|---|---|---|
| collections | array | – | Optional list of collection names to scan. Omit to scan all collections. |
| keyPath | string | yes | Absolute or relative path to the Firebase service account JSON file. |
| sampleSize | integer | – | Max documents to sample per collection (default: 50, max: 500). |
No output schema declared.
No examples provided.
What is the io.github.Madia333/lintbase-mcp server?
io.github.Madia333/lintbase-mcp is listed in the public MCP registry as io.github.Madia333/lintbase-mcp. Real-time Firestore schema context for AI coding agents. Stop hallucinating field names. This page covers its npm package (lintbase-mcp).
Is the io.github.Madia333/lintbase-mcp server safe to use?
io.github.Madia333/lintbase-mcp scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 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.Madia333/lintbase-mcp server expose?
io.github.Madia333/lintbase-mcp exposes 3 tools: lintbase_scan, lintbase_get_schema, lintbase_get_issues. Their descriptions and schemas cost roughly 474 tokens of context every time the server is loaded.
Is the io.github.Madia333/lintbase-mcp server still maintained?
io.github.Madia333/lintbase-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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.Madia333/lintbase-mcp server under?
io.github.Madia333/lintbase-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.