tecconcursos-mcp
Related Servers
Alternatives to tecconcursos-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables analyzing Codeforces activity through local MCP tools, including weekly practice summaries, problem recommendations, user comparisons, weak-topic detection, contest tracking, and rating progress.-
- AlicenseNot gradedqualityDmaintenanceProvides a local CBT exam system as MCP tools for Codex, managing study sessions, scoring, wrong answer tracking, and review queues with deterministic Python engine and optional Notion integration.MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying Brazilian public data through MCP tools, including IBGE geography, CNPJ/CEP/CPF lookups, BCB rates, FIPE vehicles, PNCP procurement, gazettes, OAB records, the slave-labour blacklist, and CNES health facilities, with local CPF validation.82 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search, read and cross-check a local, offline SQLite corpus of STJ and TJSC appellate decisions (ementas), accepted repetitive themes and súmulas, plus citations between them, through five read-only tools. Coverage is partial and declared, so every search reports its sources, delays and gaps.1MIT
- FlicenseNot gradedqualityCmaintenanceProvides local MCP tools for searching, filtering, adding, updating, and analyzing a catalog of study projects, with statistics and GitHub publication readiness checks, all backed by SQLite.-
- AlicenseBqualityBmaintenanceEnables answering questions about your disc golf rounds, courses, hole-by-hole scores and scoring trends, plus practice-throw speed, distance, spin and angle, read entirely from your own CSV exports with no credentials or network access.13MIT
TDQS
Scored across 11 tools
Several tools target the same underlying data with only subtly different framing: `desempenho` (grouped by materia/assunto/banca/...) heavily overlaps `desempenho_assuntos` (acertos por matéria/assunto), and `pontos_fracos` is essentially `desempenho` sorted ascending with a min-questions filter. `resumo_geral`, `listar_exports` and `progresso` also blur together around 'what data do I have'. The mentoria pair (preparar vs registrar) is clearly distinct, but the analytics cluster will invite misselection.
All names are Portuguese snake_case, readable and consistent in style, with clear verb_noun forms for actions (`listar_exports`, `buscar_questao`, `salvar_estatisticas_qconcursos`, `registrar_lancamentos_mentoria`). The deviation is that several read tools are bare noun phrases (`desempenho`, `desempenho_assuntos`, `progresso`, `pontos_fracos`) with no verb, so the action is not encoded in the name.
11 tools is a well-scoped size for an analytics-plus-mentoria server, and each covers a plausible workflow step. The count is slightly inflated by near-duplicates (`desempenho_assuntos`, `pontos_fracos`) that could arguably be parameter modes of `desempenho`.
Read coverage is strong (overview, performance, weak points, wrong questions, search, progress) and both write paths exist (saving QConcursos days, recording mentoria launches). However there is no tool to read back `mentoria_lancados.json`, so the agent cannot check what was already launched — a dead end for the stated anti-duplicate workflow — and there is no undo/removal for recorded launches or any ingestion path for TecConcursos spreadsheets beyond the exports folder.