CKB Pulse
REMOTE · PULSE-LAB.LUSOCRYPTOLABS.COM
Who builds on Nervos CKB, from public GitHub: projects, people, updates, DAO-funded work. Read-only.
Available components
Last scanned (21 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: signatures are present but failed validation. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 636 tokens (~79/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 70
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 4 Nov 2026 · Probed https://pulse-lab.lusocryptolabs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pulse-lab.lusocryptolabs.com | CN=YE1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5df4d09c7707e3db38b8e14d321e0f95946 |
| SANs: pulse-lab.lusocryptolabs.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC bogus
Validation of pulse-lab.lusocryptolabs.com. — Bogus
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lusocryptolabs.com. | present | 3486 | 13 | Verified |
| pulse-lab.lusocryptolabs.com. | Bogus address RRset signature failed verification |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15768000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pulse-lab.lusocryptolabs.com/mcp | Verified | 200 | |
| http (plaintext) | http://pulse-lab.lusocryptolabs.com/mcp | HTTPS enforced | 301 | https://pulse-lab.lusocryptolabs.com/mcp |
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 →
dao_funded Grants of the Community Fund DAO ~43
The projects the Nervos Community Fund DAO pays for: their code activity next to their reports on Nervos Talk, and whether each is in progress, quiet or delivered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_projects Find CKB projects ~96
Search the projects Pulse follows by words in their name, description or topics, by area (ckb, fiber, dob/spore, rgb++, ccc, nervos), or both; the most active first.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | – |
| limit | integer | – | at most this many, 15 by default |
| query | string | – | words to look for, e.g. "wallet" or "lock script" |
No output schema declared.
No examples provided.
overview What is happening in CKB ~60
The CKB ecosystem over the last day, week or month: how many updates, people and projects, the most active projects, people and organisations, and the projects new to Pulse.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | day, week (the default) or month |
No output schema declared.
No examples provided.
person One CKB developer ~50
What one person works on across the CKB projects Pulse follows: their projects, the areas and languages of those projects, and the kinds of updates they make.
| Name | Type | Req | Description |
|---|---|---|---|
| login | string | yes | the GitHub login |
No output schema declared.
No examples provided.
project One CKB project ~55
One followed project in detail: description, language, topics, activity per day over 30 days, commits and developers per month, its people and its latest updates.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | the GitHub repository, owner/repo |
No output schema declared.
No examples provided.
recent_updates Latest updates ~90
The latest updates by people (pushes, pull requests, issues, reviews, releases) across CKB, or in one project, or by one person; newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | at most this many, 20 by default |
| login | string | – | a GitHub login, to see one person |
| project | string | – | owner/repo, to see one project |
No output schema declared.
No examples provided.
trends Builders per month ~33
Developers, new developers and commits per month over two years, in the projects Pulse follows today. The current month is so far.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
who_works_on Who works on what ~114
The people most active in the projects of an area (ckb, fiber, dob/spore, rgb++, ccc, nervos) or in the projects that match some words, with the projects they work on. Useful to find who to ask about a part of CKB.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | – |
| limit | integer | – | at most this many people, 10 by default |
| query | string | – | words that pick the projects, e.g. "wallet" or "spore" |
No output schema declared.
No examples provided.
How do I install the CKB Pulse MCP server?
CKB Pulse is a hosted endpoint at https://pulse-lab.lusocryptolabs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pulse-lab.lusocryptolabs.com
claude mcp add --transport http lusocryptolabs-ckb-pulse 'https://pulse-lab.lusocryptolabs.com/mcp'
What is the CKB Pulse MCP server?
CKB Pulse is an MCP server listed in the public MCP registry as io.github.LusoCryptoLabs/ckb-pulse. Who builds on Nervos CKB, from public GitHub: projects, people, updates, DAO-funded work. Read-only. This page covers its hosted endpoint (https://pulse-lab.lusocryptolabs.com/mcp).
Is the CKB Pulse MCP server safe to use?
CKB Pulse scores 71 out of 100 on VerifyMCP. 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 CKB Pulse MCP server expose?
CKB Pulse exposes 8 tools: overview, find_projects, project, person, who_works_on, and 3 more. Their descriptions and schemas cost roughly 541 tokens of context every time the server is loaded.
Does the CKB Pulse MCP server require authentication?
No. We connected to CKB Pulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CKB Pulse MCP server still maintained?
CKB Pulse 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.