guide.bicycle/guide-registry
REMOTE · BICYCLE.GUIDE · SCANNED SEP 30
Read-only Bicycle Guide registry: published guides, homes, taxonomy, capability spine. No auth.
Available components
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: this domain isn't protected by DNSSEC. 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 (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1473 tokens (~210/item across 7 items; 7 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 Management73
- Stability observed for 22 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 (100% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 guide.bicycle/guide-registry MCP server?
guide.bicycle/guide-registry is a hosted endpoint at https://bicycle.guide/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 · bicycle.guide
claude mcp add --transport http guide-bicycle-guide-registry 'https://bicycle.guide/mcp'
{
"mcpServers": {
"guide-bicycle-guide-registry": {
"url": "https://bicycle.guide/mcp"
}
}
} {
"servers": {
"guide-bicycle-guide-registry": {
"type": "http",
"url": "https://bicycle.guide/mcp"
}
}
} [mcp_servers.guide-bicycle-guide-registry] url = "https://bicycle.guide/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"guide-bicycle-guide-registry": {
"type": "remote",
"url": "https://bicycle.guide/mcp",
"enabled": true
}
}
} openclaw mcp add guide-bicycle-guide-registry --url 'https://bicycle.guide/mcp' --transport streamable-http
mcp_servers:
guide-bicycle-guide-registry:
url: "https://bicycle.guide/mcp" {
"McpServers": {
"guide-bicycle-guide-registry": {
"Transport": "http",
"Url": "https://bicycle.guide/mcp"
}
}
} assistant mcp add guide-bicycle-guide-registry -t streamable-http -u 'https://bicycle.guide/mcp'
{
"mcpServers": {
"guide-bicycle-guide-registry": {
"type": "http",
"url": "https://bicycle.guide/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Schema quality: 218 → 189 ▲ functional
- New tool “list_conditions” functional
- New tool “list_disagreements” functional
- New tool “search_guides” functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 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 30 Sept 2026 · Probed https://bicycle.guide/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bicycle.guide | CN=YR2,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | RSA 2048 | SHA256-RSA | 519c41644c9d5b0eee9a66258678c83d06b |
| SANs: bicycle.guide | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bicycle.guide. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| guide. | present | 49501 | 8 | Verified |
| bicycle.guide. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bicycle.guide/mcp | Verified | 200 | |
| http (plaintext) | http://bicycle.guide/mcp | HTTPS enforced | 308 | https://bicycle.guide/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 →
get_guide Get one guide's registry row ~44
Get one guide's registry row by slug, with its artifact + routing-surface status.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The guide slug, e.g. start-a-company. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | yes | – |
| guide | object | yes | – |
No examples provided.
list_capabilities Traverse the capability spine (books · guides · KSAO elements · jobs) ~462
Traverse the capability spine joining books, guides (capability packages), KSAO-grade elements and jobs. Use min_guides=2 for the cross-cutting capabilities that span many guides, role=<role> for what a job requires, capability_detail=<slug> for one package with its elements and books hydrated. ksao_type/canon_component_id are null by design where unresolved — treat null as 'not yet joined', never as 'no link'.
| Name | Type | Req | Description |
|---|---|---|---|
| canon_promotion_candidate | boolean | – | true = only elements the JobFrame canon has NO component for. This is a real answer, not a failed lookup — these are the constructs to PROMOTE into the canon. |
| capability | string | – | Elements taught by this capability (guide slug). |
| capability_detail | string | – | Return ONE capability with its elements and books hydrated, instead of querying elements. |
| conflicting | boolean | – | Only elements where 2+ non-career guides define the same label differently — these need a ruling. |
| construct_class | string | – | person-attribute (knowledge/skill/ability — what a JOB requires and a learner develops) | condition-or-outcome (what a capability PRODUCES, e.g. 'Retention & Workforce Stability'). Only ~30% of eleme… |
| has_canon_identity | boolean | – | true = only elements resolved to a JobFrame canon component (an IDENTITY, panel-adjudicated). false = only unresolved. |
| has_job | boolean | – | Only elements that some job requires (via a career guide). |
| ksao_type | string | – | knowledge | skill | ability | other — from a panel validated at 95.1% on gold O*NET labels. 'other' is UNVALIDATED (no gold labels existed for it). |
| limit | number | – | Cap the rows returned (default 200). `total` always reports the true count. |
| min_guides | number | – | Only elements taught by >= N capabilities. 2 gives the cross-cutting spine. |
| q | string | – | Substring match on the element label. |
| role | string | – | Elements required by this job role, e.g. compensation-analyst. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | yes | – |
| capability | object | – | – |
| elements | array | – | – |
| returned | number | – | – |
| spine_meta | – | yes | – |
| total | number | – | – |
No examples provided.
list_conditions List organizational conditions ~164
List organizational conditions (identity, label, guide count, causal-role counts). Filter by draft domain, subdomain, or causal_role (driver|mediator|outcome). Names and counts only — no addresses, no passages.
| Name | Type | Req | Description |
|---|---|---|---|
| causal_role | string | – | driver | mediator | outcome. Unknown values match nothing. |
| domain | string | – | Draft domain slug, e.g. organizational-structure-and-culture. |
| id | string | – | Exact condition_identity_id. When set, other filters are ignored. |
| limit | number | – | Cap rows returned. Default 100, max 500. |
| q | string | – | Substring match on the condition label. |
| subdomain | string | – | Draft sub-domain slug, e.g. organizational-learning-and-improvement. |
| Name | Type | Req | Description |
|---|---|---|---|
| address_status | string | yes | – |
| api_version | string | yes | – |
| conditions | array | yes | – |
| count | number | yes | – |
| filters | object | yes | – |
| taxonomy | object | yes | – |
| total_matching | number | yes | – |
No examples provided.
list_disagreements List cross-book disagreements ~135
Where does the field disagree? Returns cross-book tension names and the books on each pole (title, author, library_id) plus the guide URL. Filter by slug, persona, or category. Names and provenance only — no passages.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Subject shelf, e.g. field, skills, analytics. |
| limit | number | – | Cap rows returned. Default 100, max 500. |
| persona | string | – | Audience filter, e.g. people-analytics-professional. |
| slug | string | – | One guide, e.g. start-a-company. When set, persona/category are ignored. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | yes | – |
| count | number | yes | – |
| disagreements | array | yes | – |
| filters | object | yes | – |
| total_matching | number | yes | – |
No examples provided.
list_guides List the guide registry ~482
List the bicycle.guide registry — every guide's home, status, access, standard, syndication and grounding, plus the distribution roll-up (including guides homed to a property with no rendering surface).
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | Filter by access: free | gated. |
| category | string | – | Filter by subject shelf — the reader-facing topic axis, e.g. field, skills, analytics, writing, comp. Matches the primary category OR a cross-shelf tag. |
| domain | string | – | Filter by life-domain — the layer ABOVE the subject shelf: work | life | play. Derived from the guide's category via content/registry/shelves.json. `rollup.by_domain` lists them. |
| fields | string | – | Row shape. "compact" returns only slug/title/home/status/access/price_cents/has_artifact/category/domain/personas/canonical_url — no rollup, no registry_meta. "full" returns the entire decorated regi… |
| guide_type | string | – | Filter by guide CLASS: career (level-based job guides, their own program) | capability | book_profile. Combine with series=ladder:<role> to get one role's whole ladder. |
| has_artifact | boolean | – | Only guides that do (true) / do not (false) have a new-design artifact. |
| home | string | – | Filter by owning property, e.g. jobframe, peopleanalyst, penwright. |
| home_unrouted | boolean | – | Only guides whose home has NO rendering surface at all (the distribution gap). |
| limit | number | – | Cap the rows returned. Default 100, max 500. |
| persona | string | – | Filter by the audience a guide serves, e.g. people-analytics-professional, aspiring-author, executive-performance-leader. A guide can serve several; this matches any of them. |
| series | string | – | Filter by guide series — the operational grouping of guides made to be used together, e.g. competencies, penwright-writing, startup-journey, ladder:hr-business-partner. |
| standard | string | – | Filter by standard: bicycle | life-stage | problem-opportunity. |
| status | string | – | Filter by status: on | draft. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | yes | – |
| count | number | yes | – |
| fields | string | yes | – |
| filters | object | yes | – |
| guides | array | yes | – |
| limit | – | yes | – |
| registry_meta | – | – | – |
| rollup | object | – | – |
| total_matching | number | yes | – |
No examples provided.
list_taxonomy Get the guide program's vocabulary ~59
Get the bicycle.guide vocabulary — domains, shelves (with live guide counts), series, personas, guide_types, and the classification conventions (pillar/spoke, discriminant home, bicycle-guide-serves-all) as machine-readable data rather than prose.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | yes | – |
| conventions | object | yes | – |
| counts_basis | object | yes | – |
| domains | array | yes | – |
| guide_types | array | yes | – |
| personas | array | yes | – |
| registry_meta | – | yes | – |
| series | array | yes | – |
| shelves | array | yes | – |
| unclassified | object | yes | – |
No examples provided.
search_guides Search guides, or refuse with the nearest owned ~127
Search published guides by topic. Returns matches, or a structured refusal with the nearest owned guides and the missing topic. No model call. Filter by persona or category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Subject shelf filter. A miss that fails this rule is a structured refusal. |
| limit | number | – | Cap hits returned. Default 10, max 20. |
| persona | string | – | Audience filter. A miss that fails this rule is a structured refusal. |
| q | string | yes | Topic or question in plain language. No model call — matched against registry taxonomy and the capability spine. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | yes | – |
| covered | boolean | yes | – |
| filters | object | yes | – |
| guides | array | yes | – |
| missing_topic | – | yes | – |
| nearest | array | yes | – |
| query | string | yes | – |
| suggest | array | yes | – |
No examples provided.
What is the guide.bicycle/guide-registry MCP server?
guide.bicycle/guide-registry is an MCP server listed in the public MCP registry as guide.bicycle/guide-registry. Read-only Bicycle Guide registry: published guides, homes, taxonomy, capability spine. No auth. This page covers its hosted endpoint (https://bicycle.guide/mcp).
Is the guide.bicycle/guide-registry MCP server safe to use?
guide.bicycle/guide-registry scores 83 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 guide.bicycle/guide-registry MCP server expose?
guide.bicycle/guide-registry exposes 7 tools: list_guides, get_guide, list_taxonomy, list_capabilities, search_guides, and 2 more. Their descriptions and schemas cost roughly 1,473 tokens of context every time the server is loaded.
Does the guide.bicycle/guide-registry MCP server require authentication?
No. We connected to guide.bicycle/guide-registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the guide.bicycle/guide-registry MCP server still maintained?
guide.bicycle/guide-registry is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.