# guide.photographer/guide-registry (remote · photographer.guide)

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

- Trust score: 83/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://photographer.guide/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-11-05.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1669 tokens (~166/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 78/100
  - Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 additions.
- **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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 guide.photographer/guide-registry MCP server?

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

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "guide-photographer-guide-registry": {
      "type": "http",
      "url": "https://photographer.guide/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-10-16 (score 83, −3)

- [security regression] Stability: pass → fail

### 2026-10-10 (score 86, +1)

- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “get_membership_offer” was removed
- [security] Stability: 0.97 → pass
- [functional improvement] Schema quality: 218 → 166
- [functional] New tool “get_answer”
- [functional] New tool “list_answers”
- [functional] New tool “list_conditions”
- [functional] New tool “list_disagreements”
- [functional] New tool “search_answers”
- [functional] New tool “search_guides”

### 2026-10-08 (score 85, +1)

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

### 2026-10-04 (score 84, +1)

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

### 2026-09-28 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-16 (score 0)

- [functional improvement] Schema quality: 261 → 218
- [functional] New tool “get_membership_offer”

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

- [functional improvement] Stability: unverified → 0.03

## MCP tools (10)

### `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)

### `search_guides` (~127 tokens)

Search guides, or refuse with the nearest owned

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.

Input parameters:

- `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, required): Topic or question in plain language. No model call — matched against registry taxonomy and the capability spine.

Output parameters:

- `api_version` (string)
- `covered` (boolean)
- `filters` (object)
- `guides` (array)
- `missing_topic`
- `nearest` (array)
- `query` (string)
- `suggest` (array)

### `list_disagreements` (~135 tokens)

List cross-book disagreements

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.

Input parameters:

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

Output parameters:

- `api_version` (string)
- `count` (number)
- `disagreements` (array)
- `filters` (object)
- `total_matching` (number)

### `list_conditions` (~164 tokens)

List organizational conditions

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.

Input parameters:

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

Output parameters:

- `address_status` (string)
- `api_version` (string)
- `conditions` (array)
- `count` (number)
- `filters` (object)
- `taxonomy` (object)
- `total_matching` (number)

### `get_answer` (~64 tokens)

Get an answer

Get one Answer — question, grounded answer, visible citations — by id or slug, in the Answer contract v0 shape (ANSWERS-PROGRAM.md). Read-only. Returns null if not found.

Input parameters:

- `id` (string, required): The Answer's stable id or slug.

Output parameters:

- `answer`

### `list_answers` (~66 tokens)

List answers

List Answers (contract v0), paginated with an opaque cursor. Read-only.

Input parameters:

- `cursor` (string): Opaque pagination cursor from a previous list_answers call's nextCursor.
- `limit` (integer): Max answers to return (default: loader's choice, capped 200).

Output parameters:

- `items` (array)
- `nextCursor`

### `search_answers` (~66 tokens)

Search answers

Search Answers by free-text query over question/answer text. Returns contract v0 records. Read-only.

Input parameters:

- `limit` (integer): Max results to return (default: loader's choice, capped 200).
- `query` (string, required): Free-text query matched against question/answer text.

Output parameters:

- `results` (array)

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 83
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 83
- 2026-10-27: 83
- 2026-10-26: 83
- 2026-10-25: 83
- 2026-10-24: 83
- 2026-10-23: 83
- 2026-10-22: 83
- 2026-10-21: 83
- 2026-10-20: 83
- 2026-10-19: 83
- 2026-10-18: 83
- 2026-10-17: 83
- 2026-10-16: 83
- 2026-10-15: 86
- 2026-10-14: 86
- 2026-10-13: 86
- 2026-10-12: 86
- 2026-10-10: 86
- 2026-10-08: 85
- 2026-10-06: 84
- 2026-10-04: 84
- 2026-10-03: 83

## Common questions

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

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

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

guide.photographer/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.photographer/guide-registry MCP server expose?

guide.photographer/guide-registry exposes 10 tools: list_guides, get_guide, list_taxonomy, list_capabilities, search_guides, and 5 more. Their descriptions and schemas cost roughly 1,669 tokens of context every time the server is loaded.

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

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

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

guide.photographer/guide-registry is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the guide.photographer/guide-registry MCP server?

VerifyMCP ran 13 checks on guide.photographer/guide-registry, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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