Home / MCP registry index / com.ripostiq/ripostiq
Ripostiq
com.ripostiq/ripostiq in the official MCP registry.
Endpoint https://ripostiq.com/mcp.
The registry describes it as: Courses that argue back: learn adaptively, build real work, then defend it to an AI stakeholder.
We read its 24 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
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
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-ripostiq-ripostiq)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.