Firekeep
PYPI · FIREKEEP-CLIENT · SCANNED AUG 18
Self-hosted operating layer for AI agents: knowledge, continuity, coordination, and governance.
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 →
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
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 Management17
- Stability observed for 5 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
pypi · firekeep-client
claude mcp add kapella-hub-firekeep -- uvx firekeep-client
codex mcp add kapella-hub-firekeep -- uvx firekeep-client
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kapella-hub-firekeep": {
"type": "local",
"command": [
"uvx",
"firekeep-client"
],
"enabled": true
}
}
} openclaw mcp add kapella-hub-firekeep --command uvx --arg firekeep-client
mcp_servers:
kapella-hub-firekeep:
command: "uvx"
args: ["firekeep-client"] {
"mcpServers": {
"kapella-hub-firekeep": {
"command": "uvx",
"args": [
"firekeep-client"
]
}
}
} 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.
- 18 Aug 26 +18
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.1.43 → 1.0.2 functional
- Package version: 0.1.43 → 1.0.1 functional
- 17 Aug 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Aug 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Aug 26 65
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 18 Aug 2026 · Analysed pypi/firekeep-client@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
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.
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.