A Model Context Protocol (MCP) server that provides native access to Quip documents from any MCP-compatible AI client (Claude Desktop, Claude Code, or custom integrations). Search, browse, and read Quip documents as clean markdown.
A Model Context Protocol (MCP) server for interacting with Quip spreadsheets. It provides tools to read spreadsheet data from Quip documents and return the content in CSV format.
Enables AI agents in Cursor and other MCP clients to connect to Sberbank's webQUIK terminal over WebSocket, allowing them to view portfolios, quotes, orders, trades, limits, and place or cancel orders within isolated user sessions.
MCP server that exposes qui's JSON REST API as tools for monitoring and managing qBittorrent instances, torrents, automations, cross-seeding, RSS, backups, and related services.
Enables an LLM to act as a quiz master by generating and saving quiz questions, then issuing tests and recording results for long-term tracking and analysis. This lets users identify weak points and monitor progress over time.
Enables Alexa+ or any MCP client to conduct bilingual Tamil/English exam coaching for TNPSC, UPSC, and CTET, with adaptive quizzes, verified explanations, streaks, and topic browsing.
Je dois répondre en JSON avec name et description. Name = "jevmem" (le nom du serveur MCP publié). Description : décrit ce que le serveur permet, sans répéter le nom. Par exemple : "Saves decisions, rules, bugs, to-dos and dead ends from Claude Code and Cursor chats into a versioned JEVMEM.md file in the repository, then brings the relevant lines back in later sessions and checks tool calls against saved rules before they run." Je dois vérifier : ne pas citer de personne/mainteneur/organisation. Ne pas répéter le nom. Deux phrases max. Éviter de mentionner "jevmem" comme nom. Je peux dire "Saves..." sans nom. Ça mentionne JEVMEM.md, ce n'est pas le nom du serveur mais le fichier, c'est autorisé ? La consigne : la description ne doit pas reprendre le nom. Le nom est "jevmem" ; "JEVMEM.md" contient jevmem. Mieux éviter. Je vais dire "a markdown memory file in the repository". Éviter aussi les noms d'organisations (TypeSafe, Anthropic, Claude Code...). Claude Code est un produit, pas une personne/organisation. Mais prudence : ne pas citer de mainteneur ou d'organisation. Je peux dire "coding-agent chats". La description doit dire ce que le serveur permet. Je vais faire deux phrases.
Provides 100 IT/programming quiz questions with tools to retrieve questions by category, get random questions, check answers, and list categories, usable via Claude Desktop MCP or REST API.
Enables users to run and interact with a quiz application through Claude Desktop or claude.ai, supporting user registration, question retrieval, answer validation, leaderboard generation, and answer review.
Enables users to run an interactive quiz through natural language, registering players, retrieving questions, validating answers, and generating leaderboards or answer reviews via MCP tools.
Enables running interactive quizzes through natural language, with tools to register users, fetch questions, validate answers, generate leaderboards, and review answers. It works locally with Claude Desktop over stdio or remotely with claude.ai over HTTP, optionally backed by MySQL.
Enables interactive quiz sessions via natural language, supporting user registration, question retrieval, answer validation, leaderboard generation, and answer review, with optional MySQL persistence.
Enables users to run and manage quizzes through natural language, including registering users, fetching questions, validating answers, and generating leaderboards, over both local stdio and remote HTTP connections.
Enables quiz gameplay through natural language, including user registration, retrieving questions, validating answers, generating leaderboards, and reviewing answers. It runs locally via stdio for Claude Desktop or remotely over HTTP for claude.ai, with optional MySQL-backed persistence.
Enables agents and users to run interactive, one-question-at-a-time quiz sessions over stdio or HTTP, backed optionally by a MySQL database. Exposes tools for registering users, fetching questions, validating answers, generating leaderboards, and reviewing responses.
Enables creating and administering multiple quizzes, adding questions, registering participants, validating answers, reviewing responses, and managing leaderboards through MCP, accessible locally via stdio or remotely over HTTP.
An interactive programming quiz server that provides assessment tools across ten tech categories with three difficulty levels. It enables users to launch quiz interfaces, receive graded feedback with explanations, and request hints through MCP-compatible tools.