# dev.stepcode/stepcode (remote · stepcode.dev)

Read-only MCP access to stepcode.dev's how-to corpus: analysis pages by tool.

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

## Components

- remote · `stepcode.dev`: 79/100 (this document), [markdown](https://verifymcp.io/servers/dev-stepcode-stepcode/api-mcp.md), [page](https://verifymcp.io/servers/dev-stepcode-stepcode/api-mcp)

## Channel facts

- Endpoint: `https://stepcode.dev/api/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-20.

- **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**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 395 tokens (~79/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 dev.stepcode/stepcode MCP server?

dev.stepcode/stepcode is a hosted endpoint at https://stepcode.dev/api/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 dev-stepcode-stepcode 'https://stepcode.dev/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-stepcode-stepcode": {
      "url": "https://stepcode.dev/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-stepcode-stepcode": {
      "type": "http",
      "url": "https://stepcode.dev/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-stepcode-stepcode]
url = "https://stepcode.dev/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-stepcode-stepcode": {
      "type": "remote",
      "url": "https://stepcode.dev/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-stepcode-stepcode --url 'https://stepcode.dev/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-stepcode-stepcode:
    url: "https://stepcode.dev/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-stepcode-stepcode": {
      "Transport": "http",
      "Url": "https://stepcode.dev/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-stepcode-stepcode -t streamable-http -u 'https://stepcode.dev/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-stepcode-stepcode": {
      "type": "http",
      "url": "https://stepcode.dev/api/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-19 (score 79, +1)

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

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

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

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

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

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

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

### 2026-09-11 (score 75, 0)

- [functional regression] Schema quality: 351 → 395
- [functional] Schema quality: excellent → good
- [functional] New tool “get_membership_offer”

### 2026-09-10 (score 75, +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-09 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-08 (score 74)

First indexed and scored.

## MCP tools (5)

### `list_howto_pages` (~69 tokens)

List stepcode's how-to pages

List every published how-to page on stepcode.dev — 36 analysis x tool cells (Excel, Google Sheets, R, Python, SQL, DAX/Power BI) with slug, title, analysis family, tool, vertical and whether the tool's approach diverges from the others.

Output parameters:

- `count` (number)
- `pages` (array)

### `search_howto_pages` (~146 tokens)

Search stepcode's how-to pages

Filter the how-to index by analysis family, tool, vertical, and/or a case-insensitive text query against title + analysis name. All filters are optional and combine with AND; call with no arguments to get every page (same as list_howto_pages).

Input parameters:

- `analysisSlug` (string): Analysis family slug, e.g. flight-risk-predict-which-employees-will-resign.
- `query` (string): Case-insensitive substring match against title + analysis name.
- `tool` (string): Tool slug, e.g. excel, sheets, r, python, sql, dax.
- `vertical` (string): Vertical slug, e.g. hr.

Output parameters:

- `count` (number)
- `pages` (array)

### `get_howto_page` (~88 tokens)

Get one stepcode how-to page

Get the full howto/v2 contract for one page by slug (from list_howto_pages /  search_howto_pages): intro, per-step teach/intent/code, divergence notes, cross-tool links, and grounding.

Input parameters:

- `slug` (string, required): How-to page slug, e.g. flight-risk-predict-which-employees-will-resign-in-excel.

Output parameters:

- `page` (object)

### `list_analysis_families` (~48 tokens)

List stepcode's analysis families

List the analysis families on stepcode.dev (e.g. flight-risk, diversity-index-EBIT-impact) with the tools each is shown in and how many pages exist for it.

Output parameters:

- `count` (number)
- `families` (array)

### `get_membership_offer` (~44 tokens)

Get the Bicycle Cooperative membership offer

Return this front's Bicycle Cooperative membership offer with the People Analytics chapter substituted, all five options (membership and rent), and the join URL. Read-only; no payment.

Output parameters:

- `api_version` (string)
- `chapter` (string)
- `join_url` (string)
- `offer` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-stepcode-stepcode/api-mcp#diagnostics

## Score history

- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 76
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 75
- 2026-09-09: 74
- 2026-09-08: 74

## Common questions

### What is the dev.stepcode/stepcode MCP server?

dev.stepcode/stepcode is an MCP server listed in the public MCP registry as dev.stepcode/stepcode. Read-only MCP access to stepcode.dev's how-to corpus: analysis pages by tool. This page covers its hosted endpoint (https://stepcode.dev/api/mcp).

### Is the dev.stepcode/stepcode MCP server safe to use?

dev.stepcode/stepcode scores 79 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 dev.stepcode/stepcode MCP server expose?

dev.stepcode/stepcode exposes 5 tools: list_howto_pages, search_howto_pages, get_howto_page, list_analysis_families, get_membership_offer. Their descriptions and schemas cost roughly 395 tokens of context every time the server is loaded.

### Does the dev.stepcode/stepcode MCP server require authentication?

No. We connected to dev.stepcode/stepcode without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the dev.stepcode/stepcode MCP server still maintained?

dev.stepcode/stepcode is still listed as active in the MCP registry. We last reached this channel on 20 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://stepcode.dev/api/mcp
- Repository: https://github.com/people-analyst/stepcode
- Website: https://stepcode.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-stepcode-stepcode/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-stepcode-stepcode/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-stepcode-stepcode/api-mcp