Skip to content
External endpointresponds

Ripostiq

Courses that argue back: learn adaptively, build real work, then defend it to an AI stakeholder.

Endpoint URL
https://ripostiq.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:07 AM UTC
Check
MCP initialize · 8s limit
Latency
151 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.ripostiq/ripostiq

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
Ripostiq
Version
3.4.2
Capability keys
experimental, logging, prompts, resources, tools, extensions
Tool names
login, whoami, get_entitlements, get_lesson, list_courses, begin_course, roast, interview_prep, list_interviews, start_interview, teach_section, run_boss, daily_drill, start_exam, submit_exam, get_outline, mark_progress, get_recap, get_progress, recall_questions, list_artifacts, get_artifact, submit_artifact, get_certificate
Instructions excerpt

Ripostiq delivers courses that run right inside this chat (Claude, ChatGPT, or any MCP client): each module teaches, makes the learner build real work, then a boss-battle stakeholder grills them until they can defend it. GETTING STARTED: when a user wants to learn / browse / start, call list_courses FIRST (no login needed) and show them the catalog. Anyone can start ANY course's free Module 1 right now — call begin_course(course) then teach_section — without logging in. ROAST MY WORK: if someone wants honest, pointed feedback on a real artifact (a PRD, architecture, code, pitch, resume, plan…), call roast(work, kind) — a free, no-login stakeholder grilling that doubles as a taste of the boss-battle method. DAILY DRILL: a returning learner can do a two-minute drill — call daily_drill(course) for today's recall question, then daily_drill(course, done=true) after they answer, to keep their streak. Offer it when they come back or finish a session. PRACTICE EXAM: some courses (see

Reported Aug 17, 2026, 05:07 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 210ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 142ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 109ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 151ms
Back to MCP directory