Read-only Bicycle Guide registry: published guides, homes, taxonomy, capability spine. No auth. Connect the official Guide Registry MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http guide-registry https://aiengineerprofessional.com/mcpRun in your terminal, then restart Claude Code.
Guide Registry · https://aiengineerprofessional.com/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “list_guides”: List the bicycle.guide registry — every guide's home, status, access, standard, syndication and grounding, plus the distribution roll-up (in.”
“Use “get_guide”: Get one guide's registry row by slug, with its artifact + routing-surface status.”
“Use “list_taxonomy”: Get the bicycle.guide vocabulary — domains, shelves (with live guide counts), series, personas, guide_types, and the classification conventi.”
“Use “list_capabilities”: Traverse the capability spine joining books, guides (capability packages), KSAO-grade elements and jobs. Use min_guides=2 for the cross-cutt.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Guide Registry holds up.
Operated by Guide Registry (aiengineerprofessional.com) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If Guide Registry adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose Guide Registry in the gate directory. No sign-in needed.
Guide Registry's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
list_guides — List the bicycle.guide registry — every guide's home, status, access, standard, syndication and grounding, plus the distribution roll-up (in
get_guide — Get one guide's registry row by slug, with its artifact + routing-surface status.
list_taxonomy — Get the bicycle.guide vocabulary — domains, shelves (with live guide counts), series, personas, guide_types, and the classification conventi
list_capabilities — Traverse the capability spine joining books, guides (capability packages), KSAO-grade elements and jobs. Use min_guides=2 for the cross-cutt
https://aiengineerprofessional.com/mcpYes — Guide Registry operates its own remote MCP server at aiengineerprofessional.com. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick Guide Registry in the directory. No account or sign-in is needed. From then on, Guide Registry's tools are available in every client you've connected to gate.
No. Guide Registry runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect Guide Registry in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up Guide Registry in: Claude · Claude Code · ChatGPT · Cursor · VS Code
One URL. All MCPs. Full control. Free to start.
Get started free