io.github.robinlidberg-dot/cap-shield
PYPI · CAP-SHIELD · SCANNED SEP 20
Context selection and compression for AI agents - recall measured, not claimed.
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 9 dependencies flagged as unhealthy. View diagnostics → Pass
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 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 483 tokens (~96/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.robinlidberg-dot/cap-shield MCP server?
io.github.robinlidberg-dot/cap-shield runs locally as a PyPI package, launched with uvx cap-shield. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · cap-shield
claude mcp add robinlidberg-dot-cap-shield -- uvx cap-shield
{
"mcpServers": {
"robinlidberg-dot-cap-shield": {
"command": "uvx",
"args": [
"cap-shield"
]
}
}
} {
"servers": {
"robinlidberg-dot-cap-shield": {
"command": "uvx",
"args": [
"cap-shield"
]
}
}
} codex mcp add robinlidberg-dot-cap-shield -- uvx cap-shield
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"robinlidberg-dot-cap-shield": {
"type": "local",
"command": [
"uvx",
"cap-shield"
],
"enabled": true
}
}
} openclaw mcp add robinlidberg-dot-cap-shield --command uvx --arg cap-shield
mcp_servers:
robinlidberg-dot-cap-shield:
command: "uvx"
args: ["cap-shield"] {
"McpServers": {
"robinlidberg-dot-cap-shield": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"cap-shield"
]
}
}
} assistant mcp add robinlidberg-dot-cap-shield -t stdio -c uvx -a cap-shield
{
"mcpServers": {
"robinlidberg-dot-cap-shield": {
"command": "uvx",
"args": [
"cap-shield"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 pypi/cap-shield@0.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 9 packages
| Packages resolved | 9 |
|---|---|
| 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 →
assemble_context ~121
Retrieve the memory entries that answer a question, within a token budget. REQUIRES A KEY. Send the returned 'context' to your language model INSTEAD of the whole history. This does not call a model itself — it selects what to send. The budget is a ceiling, not a target: selection stops where relevance runs out, often well below it. The response says how many entries were left behind and why.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | yes | – |
| query | string | yes | What you need context about. |
| token_budget | integer | – | – |
No output schema declared.
No examples provided.
get_account ~74
Get an account and an API key. Requires an email address. The key is returned ONCE and cannot be shown again — store it immediately. Beta quotas are low by design; they are hard stops, never overage billing.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| traffic | string | – | Optional. What your agent sends. |
No output schema declared.
No examples provided.
list_packages ~56
List the available dictionaries with their MEASURED compression, including the ones that perform badly. Each entry says whether it works one message at a time or only batched, and how many messages came out LARGER. No key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
measure_traffic ~143
Measure how much of your own agent traffic could be saved. NO ACCOUNT OR KEY NEEDED — use this first. Returns byte savings over the wire and, if a query is given, token savings from selective context retrieval. Nothing is stored: the text is compressed in memory and discarded. Rate limited to 20 calls per hour per IP.
| Name | Type | Req | Description |
|---|---|---|---|
| dict_id | string | – | Which trained dictionary to measure against. Call list_packages to see the options and their measured figures. |
| query | string | – | Optional. What your agent would search its memory for. Given this, token savings are measured too. |
| texts | array | yes | Your actual messages. 200 max. |
No output schema declared.
No examples provided.
remember ~89
Store a memory entry for later retrieval. REQUIRES A KEY. This does not call any language model — it stores text in an isolated per-tenant archive. Use assemble_context to get relevant entries back.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | – | Optional. Same id overwrites the entry. Omit for a generated one. |
| namespace | string | yes | Groups related memories. |
| text | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.robinlidberg-dot/cap-shield MCP server?
io.github.robinlidberg-dot/cap-shield is an MCP server listed in the public MCP registry as io.github.robinlidberg-dot/cap-shield. Context selection and compression for AI agents - recall measured, not claimed. This page covers its PyPI package (cap-shield).
Is the io.github.robinlidberg-dot/cap-shield MCP server safe to use?
io.github.robinlidberg-dot/cap-shield scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.robinlidberg-dot/cap-shield MCP server expose?
io.github.robinlidberg-dot/cap-shield exposes 5 tools: measure_traffic, list_packages, remember, assemble_context, get_account. Their descriptions and schemas cost roughly 483 tokens of context every time the server is loaded.
Is the io.github.robinlidberg-dot/cap-shield MCP server still maintained?
io.github.robinlidberg-dot/cap-shield 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.robinlidberg-dot/cap-shield MCP server under?
io.github.robinlidberg-dot/cap-shield declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.