Firekeep
PYPI · FIREKEEP-CLIENT
Self-hosted operating layer for AI agents: knowledge, continuity, coordination, and governance.
Available components
Last scanned (22 hours ago)
Scores higher than 94% of PyPI servers
Category Memory and Knowledge
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to kapella-hub/FirekeepHQ). View diagnostics → Pass
- License check failed: the license (LicenseRef-Firekeep-BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 8 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 357 tokens (~357/item across 1 items; 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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.
- 4 Nov 26 0
- Security disclosure: pass → unverified ▼ functional
- Package version: 1.8.0 → 1.8.2 functional
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → pass ▲ functional
- 30 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- Stability: pass → 0.97 functional
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Package version: 1.8.0 → 1.8.2 functional
- Package version: 1.8.0 → 1.8.1 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
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 pypi/firekeep-client@1.8.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | kapella-hub/FirekeepHQ |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/kapella-hub/FirekeepHQ/.github/workflows/release.yml@refs/tags/client-v1.8.2 |
| Rekor log index | 3485675279 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d218adb0110cc49bd3352f90bf4a7954751852c1b288d5da657c98264b3b4cf6 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| 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 →
firekeep_gateway_status ~37
Report which Firekeep backends are reachable and why any backend's tools are absent. This is diagnostic only; plans never filter tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Firekeep MCP server?
Firekeep runs locally as a PyPI package, launched with uvx firekeep-client. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · firekeep-client
claude mcp add kapella-hub-firekeep -- uvx firekeep-client
What is the Firekeep MCP server?
Firekeep is an MCP server listed in the public MCP registry as io.github.kapella-hub/firekeep. Self-hosted operating layer for AI agents: knowledge, continuity, coordination, and governance. This page covers its PyPI package (firekeep-client).
Is the Firekeep MCP server safe to use?
Firekeep scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Firekeep MCP server expose?
Firekeep exposes 1 tool: firekeep_gateway_status. Their descriptions and schemas cost roughly 37 tokens of context every time the server is loaded.
Is the Firekeep MCP server still maintained?
Firekeep 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 Firekeep MCP server under?
Firekeep declares the LicenseRef-Firekeep-BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.