dev.stepcode/stepcode
REMOTE · STEPCODE.DEV · SCANNED OCT 4
Read-only MCP access to stepcode.dev's how-to corpus: analysis pages by tool.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 404 tokens (~101/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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
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.
remote · stepcode.dev
claude mcp add --transport http dev-stepcode-stepcode 'https://stepcode.dev/api/mcp'
{
"mcpServers": {
"dev-stepcode-stepcode": {
"url": "https://stepcode.dev/api/mcp"
}
}
} {
"servers": {
"dev-stepcode-stepcode": {
"type": "http",
"url": "https://stepcode.dev/api/mcp"
}
}
} [mcp_servers.dev-stepcode-stepcode] url = "https://stepcode.dev/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-stepcode-stepcode": {
"type": "remote",
"url": "https://stepcode.dev/api/mcp",
"enabled": true
}
}
} openclaw mcp add dev-stepcode-stepcode --url 'https://stepcode.dev/api/mcp' --transport streamable-http
mcp_servers:
dev-stepcode-stepcode:
url: "https://stepcode.dev/api/mcp" {
"McpServers": {
"dev-stepcode-stepcode": {
"Transport": "http",
"Url": "https://stepcode.dev/api/mcp"
}
}
} assistant mcp add dev-stepcode-stepcode -t streamable-http -u 'https://stepcode.dev/api/mcp'
{
"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.
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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Sept 26 0
- Tool “search_howto_pages” rewrote its description, which is the text the model reads security
- Schema quality: 87 → 101 ▼ functional
- Schema quality: excellent → good functional
- “search_howto_pages” reworded the description of “query” cosmetic
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 6 Oct 2026 · Probed https://stepcode.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stepcode.dev | CN=YR1,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | RSA 2048 | SHA256-RSA | 6333b3c4e68a953ae49ab72aa0785a0d890 |
| SANs: stepcode.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 stepcode.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| stepcode.dev. | 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://stepcode.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://stepcode.dev/api/mcp | HTTPS enforced | 308 | https://stepcode.dev/api/mcp |
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 →
get_howto_page Get one stepcode how-to page ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | How-to page slug, e.g. flight-risk-predict-which-employees-will-resign-in-excel. |
| Name | Type | Req | Description |
|---|---|---|---|
| page | object | yes | – |
No examples provided.
list_analysis_families List stepcode's analysis families ~48
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| families | array | yes | – |
No examples provided.
list_howto_pages List stepcode's how-to pages ~69
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| pages | array | yes | – |
No examples provided.
search_howto_pages Search stepcode's how-to pages ~199
Filter the how-to index by analysis family, tool, vertical, and/or a case-insensitive text query against title, analysis name, intro, problem statement, and step operations (with practitioner-synonym coverage, e.g. attrition/turnover/churn, logistic regression/classifier, power bi/dax, diversity/simpson/blau). All filters are optional and combine with AND; call with no arguments to get every page (same as list_howto_pages).
| Name | Type | Req | Description |
|---|---|---|---|
| analysisSlug | string | – | Analysis family slug, e.g. flight-risk-predict-which-employees-will-resign. |
| query | string | – | Case-insensitive text query against title, analysis name, intro, problem statement, and step operations. |
| tool | string | – | Tool slug, e.g. excel, sheets, r, python, sql, dax. |
| vertical | string | – | Vertical slug, e.g. hr. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| pages | array | yes | – |
No examples provided.
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 86 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 4 tools: list_howto_pages, search_howto_pages, get_howto_page, list_analysis_families. Their descriptions and schemas cost roughly 404 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 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.