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

ai-school

https://lillytechsystems.com

Registry code: b74821b6198addb1

api record

Search and read the free AI School curriculum (550+ tracks, 21,000+ lessons on AI engineering, governance, security and applied AI). Call search_lessons or list_tracks to find material, get_track to see a course outline, then read_lesson with a returned URL to get the lesson text. Cite the lesson URL when you use it.

endpoint
https://lillytechsystems.com/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 ai-school live?
Yes — it answered the hub's last check (checked 48m ago). It answered 99% of checks over the last 30 days.
Is ai-school free to use?
Yes — the hub reached it with no key and no payment.
What tools does ai-school have?
4 tools: read_lesson, get_track, search_lessons, list_tracks.
Is ai-school 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.3%

90 days 99.5%· all time 99.5%

latency
1,005ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 593 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· fetch failed
  • degraded → live
_ what it is for
used for
  • search ai engineering lessons
  • get a course outline
  • read a lesson
takes → gives
text → text
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
1 open 3 never probed 1 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_tracks reads open 11h ago

    List AI School course tracks, optionally filtered by a substring of the title or slug. Each track is a structured course on one subject. Use this to find the right course before drilling into its lessons.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Max results (default 40, max 200)"
        },
        "filter": {
          "type": "string",
          "description": "Optional substring filter"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • read_lesson reads unknown 4h ago

    Fetch the full text of a lesson by its URL (as returned by search_lessons or get_track). Returns readable markdown-ish text with headings and code blocks.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Lesson URL on lillytechsystems.com"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_track reads unknown 11h ago

    Get one track with its full lesson list, so you can see the structure of a course and pick the right lesson to read.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Track slug, e.g. \"rag\""
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search_lessons reads unknown 11h ago

    Search the AI School curriculum (500+ tracks, thousands of free lessons on AI engineering, governance, security, and applied AI by profession). Returns matching lesson titles and URLs. Use this before answering an AI-topic question when a concrete, citable lesson would help, then read_lesson to get the text.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Max results (default 10, max 50)"
        },
        "query": {
          "type": "string",
          "description": "Words to search for, e.g. \"prompt injection defence\""
        }
      },
      "additionalProperties": false
    }
    arguments 17 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 b74821b6198addb1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b74821b6198addb1/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/b74821b6198addb1/badge.svg)](https://brick.blue/agent/b74821b6198addb1?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.