cellula.id
NPM · CELLULA-MCP
Resolve and check .cell names on Nervos, verify what a name signed, pay over Fiber as an agent.
Available components
Last scanned (29 minutes ago)
Scores higher than 34% of npm servers
Category Crypto and Web3
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
- A known CVE affects elliptic, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
- No install/post-install scripts declared.Pass
- 46 of 172 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 2 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 637 tokens (~127/item across 5 items; 5 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
- 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 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
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −9
- CVE-2025-14505 affects this package ▼ security
- Malware scan: pass → unverified ▼ security
- CVE-2026-111771 no longer affects this package ▲ security
- CVE-2026-111767 no longer affects this package ▲ security
- CVE-2026-111768 no longer affects this package ▲ security
- CVE-2026-111769 no longer affects this package ▲ security
- CVE-2023-54404 no longer affects this package ▲ security
- Known CVEs: fail → partial ▲ security
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.4.0 → 0.4.1 functional
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 45
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 5 Nov 2026 · Analysed npm/cellula-mcp@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 | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-848j-6mx2-7j84 | CVE-2025-14505 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 172 packages
| Packages resolved | 172 |
|---|---|
| Stale | 45 |
| No linked repository | 1 |
| 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 →
cell_name_registration_link A link to register a free .cell name ~162
Prepare the registration of a free .cell name for a person: returns a link that opens it on cellula.id, where they sign with their own wallet. Nothing is registered or paid by this tool. With invited_by (a registered .cell name), the link carries that name's invitation: a tenth of the fee goes to that name's owner in the same transaction, and the person pays the same as without it. Says the yearly fee and, when invited, the inviter's share.
| Name | Type | Req | Description |
|---|---|---|---|
| invited_by | string | – | A registered .cell name whose owner invites this registration |
| name | string | yes | The name to register, with or without .cell |
| network | string | – | Which Nervos network to read. Defaults to mainnet. |
No output schema declared.
No examples provided.
check_cell_name Is a .cell name free ~98
Check whether a .cell name can be registered. For a free name: the yearly fee in CKB as it stands today and the deposit held in the name. For a taken one: when it expires. Registering happens at the page returned, with the person's own wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name, with or without .cell |
| network | string | – | Which Nervos network to read. Defaults to mainnet. |
No output schema declared.
No examples provided.
name_for_address The .cell name of an address ~119
Find the .cell name a CKB address chose for itself (its primary name), checked both ways: the address chose the name and the name still points back to it. Takes a CKB address (ckb1... on mainnet, ckt1... on testnet). Returns null for an address without one.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | A CKB address: ckb1... on mainnet, ckt1... on testnet |
| network | string | – | Which Nervos network to read. Defaults to mainnet. |
No output schema declared.
No examples provided.
resolve_cell_name Where a .cell name is paid ~162
Look up a .cell name (for example alice.cell) on the Nervos blockchain and return where its owner is paid: a CKB address, and when published a Bitcoin address, an Ethereum/EVM address, a Lightning Address and a Fiber node. Also whether the name is registered, its state (live, grace or free) and when it expires. Read from the chain directly, and only addresses written by whoever holds the name now are returned (one a former owner left is listed as withheld). Pay with your own wallet to the address returned; never to an address taken from anywhere else.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name, with or without .cell |
| network | string | – | Which Nervos network to read. Defaults to mainnet. |
No output schema declared.
No examples provided.
verify_cell_statement Was this said by a .cell name ~96
Verify a statement signed by a .cell name (its check link, its token, or the pasted block between its marker lines). Says whether it was signed by whoever owns the name now, and if not, why: a former owner, a changed text, another deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Which Nervos network to read. Defaults to mainnet. |
| statement | string | yes | The statement link, token or block |
No output schema declared.
No examples provided.
How do I install the cellula.id MCP server?
cellula.id runs locally as an npm package, launched with npx -y cellula-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 · cellula-mcp
claude mcp add lusocryptolabs-cellula -- npx -y cellula-mcp
What is the cellula.id MCP server?
cellula.id is an MCP server listed in the public MCP registry as io.github.LusoCryptoLabs/cellula. Resolve and check .cell names on Nervos, verify what a name signed, pay over Fiber as an agent. This page covers its npm package (cellula-mcp).
Is the cellula.id MCP server safe to use?
cellula.id scores 67 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 cellula.id MCP server expose?
cellula.id exposes 5 tools: resolve_cell_name, name_for_address, check_cell_name, verify_cell_statement, cell_name_registration_link. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.
Is the cellula.id MCP server still maintained?
cellula.id is still listed as active in the MCP registry. We last reached this channel on 5 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 cellula.id MCP server under?
cellula.id declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.