io.github.tjclaude88/bling-bag
NPM · BLING-BAG · SCANNED SEP 22
Give your bot an identity!
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. 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 141 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 328 tokens (~65/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 Management97
- Stability observed for 29 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
- Structured output schemas are declared (60% of tools); any adoption earns full credit.Pass
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.tjclaude88/bling-bag MCP server?
io.github.tjclaude88/bling-bag runs locally as an npm package, launched with npx -y bling-bag. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · bling-bag
claude mcp add tjclaude88-bling-bag -- npx -y bling-bag
{
"mcpServers": {
"tjclaude88-bling-bag": {
"command": "npx",
"args": [
"-y",
"bling-bag"
]
}
}
} {
"servers": {
"tjclaude88-bling-bag": {
"command": "npx",
"args": [
"-y",
"bling-bag"
]
}
}
} codex mcp add tjclaude88-bling-bag -- npx -y bling-bag
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tjclaude88-bling-bag": {
"type": "local",
"command": [
"npx",
"-y",
"bling-bag"
],
"enabled": true
}
}
} openclaw mcp add tjclaude88-bling-bag --command npx --arg -y --arg bling-bag
mcp_servers:
tjclaude88-bling-bag:
command: "npx"
args: ["-y", "bling-bag"] {
"McpServers": {
"tjclaude88-bling-bag": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"bling-bag"
]
}
}
} assistant mcp add tjclaude88-bling-bag -t stdio -c npx -a -y bling-bag
{
"mcpServers": {
"tjclaude88-bling-bag": {
"command": "npx",
"args": [
"-y",
"bling-bag"
]
}
}
} 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.
- 22 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 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.
- 10 Sept 26 −3
- Stability: pass → 0.80 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 22 Sept 2026 · Analysed npm/bling-bag@0.2.0
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 →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
get_identity Who's My Bot? ~51
Who's your bot? Pull up the full identity — name, personality, quirks, appearance, and theme colours. Returns whatever's configured in bling.json. Errors if bling.json is missing or invalid.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rarity_report Show Off My Card ~41
Get the formatted share card for the most-recent roll — a plain-text block ready to screenshot and post. Errors if no roll has happened this session.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| report | string | – | – |
No examples provided.
get_theme_for_platform Style Me Up ~67
Get your bot's colours formatted for a specific platform. Supported: terminal (ANSI codes), web (CSS variables), slack, discord, ide. Unknown platforms get the raw hex colours.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | Target platform: terminal, web, slack, discord, or ide |
No output schema declared.
No examples provided.
roll_identity Spin the Wheel ~102
Give your bot a random identity. Pick a variant: wow (Weird Office Workers — quirky office drones, default) or legends (historical figures in absurd corporate roles). Returns a name, job title, traits, rarity score, and a screenshot-ready share card. Stores the roll for save_last_roll.
| Name | Type | Req | Description |
|---|---|---|---|
| variant | string | – | Which identity pool to use: wow (Weird Office Workers, default) or legends (historical figures in absurd corporate roles). |
| Name | Type | Req | Description |
|---|---|---|---|
| framed | string | yes | – |
| identity | object | yes | – |
| lore | string|null | yes | – |
| paragraph | string | yes | – |
| rarity | object | yes | – |
No examples provided.
save_last_roll Lock It In ~67
Save the most-recent roll as your bot's permanent identity. Errors if no roll has happened this session — call roll_identity first. Writes to bling.json, backing up any existing config to bling.json.bak first. Returns the backup path (or null if nothing was overwritten).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| backup | string|null | – | – |
| error | string | – | – |
| ok | boolean | – | – |
| written_to | string | – | – |
No examples provided.
What is the io.github.tjclaude88/bling-bag MCP server?
io.github.tjclaude88/bling-bag is an MCP server listed in the public MCP registry as io.github.tjclaude88/bling-bag. Give your bot an identity! This page covers its npm package (bling-bag).
Is the io.github.tjclaude88/bling-bag MCP server safe to use?
io.github.tjclaude88/bling-bag scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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.tjclaude88/bling-bag MCP server expose?
io.github.tjclaude88/bling-bag exposes 5 tools: get_identity, get_theme_for_platform, roll_identity, save_last_roll, get_rarity_report. Their descriptions and schemas cost roughly 328 tokens of context every time the server is loaded.
Is the io.github.tjclaude88/bling-bag MCP server still maintained?
io.github.tjclaude88/bling-bag is still listed as active in the MCP registry. We last reached this channel on 22 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.tjclaude88/bling-bag MCP server under?
io.github.tjclaude88/bling-bag declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.