# com.aiengineerprofessional/guide-registry (remote · aiengineerprofessional.com)

Read-only Bicycle Guide registry: published guides, homes, taxonomy, capability spine. No auth.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `aiengineerprofessional.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-aiengineerprofessional-guide-registry/aiengineerprofessional.md), [page](https://verifymcp.io/servers/com-aiengineerprofessional-guide-registry/aiengineerprofessional)

## Channel facts

- Endpoint: `https://aiengineerprofessional.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1047 tokens (~261/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.aiengineerprofessional/guide-registry MCP server?

com.aiengineerprofessional/guide-registry is a hosted endpoint at https://aiengineerprofessional.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.

### Claude

```bash
claude mcp add --transport http com-aiengineerprofessional-guide-registry 'https://aiengineerprofessional.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-aiengineerprofessional-guide-registry": {
      "url": "https://aiengineerprofessional.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-aiengineerprofessional-guide-registry": {
      "type": "http",
      "url": "https://aiengineerprofessional.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-aiengineerprofessional-guide-registry]
url = "https://aiengineerprofessional.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-aiengineerprofessional-guide-registry": {
      "type": "remote",
      "url": "https://aiengineerprofessional.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-aiengineerprofessional-guide-registry --url 'https://aiengineerprofessional.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-aiengineerprofessional-guide-registry:
    url: "https://aiengineerprofessional.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-aiengineerprofessional-guide-registry": {
      "Transport": "http",
      "Url": "https://aiengineerprofessional.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-aiengineerprofessional-guide-registry -t streamable-http -u 'https://aiengineerprofessional.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-aiengineerprofessional-guide-registry": {
      "type": "http",
      "url": "https://aiengineerprofessional.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 78, +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.

### 2026-09-19 (score 77, +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.

### 2026-09-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 74, +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.

### 2026-09-11 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-09 (score 72, +47)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 100

## MCP tools (4)

### `list_guides` (~482 tokens)

List the guide registry

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).

Input parameters:

- `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.

Output parameters:

- `api_version` (string)
- `count` (number)
- `fields` (string)
- `filters` (object)
- `guides` (array)
- `limit`
- `registry_meta`
- `rollup` (object)
- `total_matching` (number)

### `get_guide` (~44 tokens)

Get one guide's registry row

Get one guide's registry row by slug, with its artifact + routing-surface status.

Input parameters:

- `slug` (string, required): The guide slug, e.g. start-a-company.

Output parameters:

- `api_version` (string)
- `guide` (object)

### `list_taxonomy` (~59 tokens)

Get the guide program's vocabulary

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.

Output parameters:

- `api_version` (string)
- `conventions` (object)
- `counts_basis` (object)
- `domains` (array)
- `guide_types` (array)
- `personas` (array)
- `registry_meta`
- `series` (array)
- `shelves` (array)
- `unclassified` (object)

### `list_capabilities` (~462 tokens)

Traverse the capability spine (books · guides · KSAO elements · jobs)

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'.

Input parameters:

- `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.

Output parameters:

- `api_version` (string)
- `capability` (object)
- `elements` (array)
- `returned` (number)
- `spine_meta`
- `total` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-aiengineerprofessional-guide-registry/aiengineerprofessional#diagnostics

## Score history

- 2026-09-22: 78
- 2026-09-21: 78
- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 25

## Common questions

### What is the com.aiengineerprofessional/guide-registry MCP server?

com.aiengineerprofessional/guide-registry is an MCP server listed in the public MCP registry as com.aiengineerprofessional/guide-registry. Read-only Bicycle Guide registry: published guides, homes, taxonomy, capability spine. No auth. This page covers its hosted endpoint (https://aiengineerprofessional.com/mcp).

### Is the com.aiengineerprofessional/guide-registry MCP server safe to use?

com.aiengineerprofessional/guide-registry scores 78 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 com.aiengineerprofessional/guide-registry MCP server expose?

com.aiengineerprofessional/guide-registry exposes 4 tools: list_guides, get_guide, list_taxonomy, list_capabilities. Their descriptions and schemas cost roughly 1,047 tokens of context every time the server is loaded.

### Does the com.aiengineerprofessional/guide-registry MCP server require authentication?

No. We connected to com.aiengineerprofessional/guide-registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.aiengineerprofessional/guide-registry MCP server still maintained?

com.aiengineerprofessional/guide-registry 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.

## Links

- Remote endpoint: https://aiengineerprofessional.com/mcp
- Repository: https://github.com/people-analyst/bicycle-guide
- Website: https://aiengineerprofessional.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-aiengineerprofessional-guide-registry/aiengineerprofessional.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-aiengineerprofessional-guide-registry/aiengineerprofessional.json
- HTML version of this page: https://verifymcp.io/servers/com-aiengineerprofessional-guide-registry/aiengineerprofessional