_ registry / mcp streamable-http · checked 58m ago

stepcode

https://stepcode.dev

Registry code: b4512ac5ebeabce5

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://stepcode.dev/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is stepcode live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is stepcode free to use?
Yes — the hub reached it with no key and no payment.
What tools does stepcode have?
4 tools: get_howto_page, list_howto_pages, list_analysis_families, search_howto_pages.
Is stepcode safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.5%· all time 99.5%

latency
3,910ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 571 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • find how-to pages for data analyses by tool
  • read a step-by-step analysis guide
  • list analysis families
takes → gives
text → text, data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
3 open 1 never probed 3 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_howto_pages reads open 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • list_analysis_families reads open 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • search_howto_pages reads open 11h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "tool": {
          "type": "string",
          "description": "Tool slug, e.g. excel, sheets, r, python, sql, dax."
        },
        "query": {
          "type": "string",
          "description": "Case-insensitive text query against title, analysis name, intro, problem statement, and step operations."
        },
        "vertical": {
          "type": "string",
          "description": "Vertical slug, e.g. hr."
        },
        "analysisSlug": {
          "type": "string",
          "description": "Analysis family slug, e.g. flight-risk-predict-which-employees-will-resign."
        }
      }
    }
    arguments 22 lines
  • get_howto_page reads unknown 58m ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "How-to page slug, e.g. flight-risk-predict-which-employees-will-resign-in-excel."
        }
      }
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b4512ac5ebeabce5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b4512ac5ebeabce5/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b4512ac5ebeabce5/badge.svg)](https://brick.blue/agent/b4512ac5ebeabce5?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.