Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.aiengineerprofessional/guide-registry

REMOTE · AIENGINEERPROFESSIONAL.COM · SCANNED SEP 22

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

+3 this week 78 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
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.

remote · aiengineerprofessional.com

# add to Claude Code
claude mcp add --transport http com-aiengineerprofessional-guide-registry 'https://aiengineerprofessional.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-aiengineerprofessional-guide-registry": {
      "url": "https://aiengineerprofessional.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-aiengineerprofessional-guide-registry": {
      "type": "http",
      "url": "https://aiengineerprofessional.com/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-aiengineerprofessional-guide-registry --url 'https://aiengineerprofessional.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-aiengineerprofessional-guide-registry:
    url: "https://aiengineerprofessional.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-aiengineerprofessional-guide-registry": {
      "Transport": "http",
      "Url": "https://aiengineerprofessional.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-aiengineerprofessional-guide-registry -t streamable-http -u 'https://aiengineerprofessional.com/mcp'
// mcp.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 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.

  • 21 Sept 26 +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.

  • 19 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.

  • 17 Sept 26 +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.

  • 15 Sept 26 +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.

  • 13 Sept 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.

  • 11 Sept 26 +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.

  • 10 Sept 26 0
    • Stability: unverified → 0.03 functional
  • 9 Sept 26 +47
    • Authorization: unverified → partial security
    • Injection markers: unverified → pass security
    • Transport: fail → pass security
    • First check of Judged manipulation: pass security
    • Tool coverage: unverified → 100 functional
    • 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 functional
Diagnostics

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 · Probed https://aiengineerprofessional.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aiengineerprofessional.com CN=YR2,O=Let's Encrypt,C=US 10 Sept 2026 9 Dec 2026 RSA 2048 SHA256-RSA 5a9a70dab96645542e02356626209fd0a97
SANs: aiengineerprofessional.com
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 aiengineerprofessional.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
aiengineerprofessional.com. 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://aiengineerprofessional.com/mcp Verified 200
http (plaintext) http://aiengineerprofessional.com/mcp HTTPS enforced 308 https://aiengineerprofessional.com/mcp
MCP tools · 4 exposed · ~1,047 tokens

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 →

Tool Tokens
get_guide ~44

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

NameTypeReqDescription
slugstringyesThe guide slug, e.g. start-a-company.
NameTypeReqDescription
api_versionstringyes
guideobjectyes

No examples provided.

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

NameTypeReqDescription
canon_promotion_candidatebooleantrue = 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.
capabilitystringElements taught by this capability (guide slug).
capability_detailstringReturn ONE capability with its elements and books hydrated, instead of querying elements.
conflictingbooleanOnly elements where 2+ non-career guides define the same label differently — these need a ruling.
construct_classstringperson-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_identitybooleantrue = only elements resolved to a JobFrame canon component (an IDENTITY, panel-adjudicated). false = only unresolved.
has_jobbooleanOnly elements that some job requires (via a career guide).
ksao_typestringknowledge | skill | ability | other — from a panel validated at 95.1% on gold O*NET labels. 'other' is UNVALIDATED (no gold labels existed for it).
limitnumberCap the rows returned (default 200). `total` always reports the true count.
min_guidesnumberOnly elements taught by >= N capabilities. 2 gives the cross-cutting spine.
qstringSubstring match on the element label.
rolestringElements required by this job role, e.g. compensation-analyst.
NameTypeReqDescription
api_versionstringyes
capabilityobject
elementsarray
returnednumber
spine_metayes
totalnumber

No examples provided.

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

NameTypeReqDescription
accessstringFilter by access: free | gated.
categorystringFilter by subject shelf — the reader-facing topic axis, e.g. field, skills, analytics, writing, comp. Matches the primary category OR a cross-shelf tag.
domainstringFilter 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.
fieldsstringRow 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_typestringFilter 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_artifactbooleanOnly guides that do (true) / do not (false) have a new-design artifact.
homestringFilter by owning property, e.g. jobframe, peopleanalyst, penwright.
home_unroutedbooleanOnly guides whose home has NO rendering surface at all (the distribution gap).
limitnumberCap the rows returned. Default 100, max 500.
personastringFilter 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.
seriesstringFilter by guide series — the operational grouping of guides made to be used together, e.g. competencies, penwright-writing, startup-journey, ladder:hr-business-partner.
standardstringFilter by standard: bicycle | life-stage | problem-opportunity.
statusstringFilter by status: on | draft.
NameTypeReqDescription
api_versionstringyes
countnumberyes
fieldsstringyes
filtersobjectyes
guidesarrayyes
limityes
registry_meta
rollupobject
total_matchingnumberyes

No examples provided.

list_taxonomy ~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.

NameTypeReqDescription
api_versionstringyes
conventionsobjectyes
counts_basisobjectyes
domainsarrayyes
guide_typesarrayyes
personasarrayyes
registry_metayes
seriesarrayyes
shelvesarrayyes
unclassifiedobjectyes

No examples provided.

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.