io.github.rm-rf-prod/groundtruth

Est-ce que io.github.rm-rf-prod/groundtruth est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.rm-rf-prod/groundtruth » est classé « Vérifié ». Aucun comportement malveillant détecté au test comportemental. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Versions auditées & empreintes

Vérifiez la version que vous utilisez : son empreinte doit correspondre à celle listée ici — sinon vous n'utilisez pas la version auditée.

Vous utilisez ce serveur ? Suivez-le (créez un compte) pour être alerté dès qu'une nouvelle version paraît ou que le verdict change.

Les 14 outils

• gt_dispatch≈ 326 tokens

  Routes a plain-text user query to the correct gt_* tool with the right arguments. Examples: "use gt", "use gt for react", "find issues in this codebase", "migrate next from 14 to 15". WHEN TO USE: the user's intent is ambiguous, they invoked gt without specifying a tool ("use gt mcp"), or you want a single entry point that always returns something actionable. WHEN NOT TO USE: you already know which gt_* tool fits. Call it directly to save one round-trip. OUTPUT: a routing decision with tool name, args, reason, and a 0-to-1 confidence score. The response text also embeds the routing table and a recommended JSON call so you can make the next tool call without another lookup. Use it for "use gt mcp" in any phrasing.

  Paramètres, retour & exemple (2)

  Paramètres

  • query · string · requis
    Plain-text user intent. Examples: 'use gt for react', 'find issues', 'migrate next from 14 to 15', 'best practices for fastapi'.
  • projectPath · string · optionnel
    Optional project directory for project-level intents (auto-scan, audit). Defaults to current working directory.

  Exemple d'appel

  {"name": "gt_dispatch", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_resolve_library≈ 326 tokens

  Resolve a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before gt_get_docs to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. For 2-20 libraries at once, use gt_batch_resolve instead. Each result includes: - id: the library ID to pass to gt_get_docs (e.g. 'vercel/next.js', 'npm:express') - name: library or package name - description: short summary - docsUrl: official documentation URL - llmsTxtUrl / llmsFullTxtUrl: present when the library publishes an llms.txt — prefer these results, they yield the cleanest docs - githubUrl: source repository when known - score: 0-100 name-match quality (100 = exact r

  Paramètres, retour & exemple (2)

  Paramètres

  • query · string · optionnel
    Optional: what you want to do with this library, used to rank results
  • libraryName · string · requis
    Library or framework name to look up. Examples: 'nextjs', 'react', 'tailwind', 'fastapi', 'drizzle'

  Exemple d'appel

  {"name": "gt_resolve_library", "arguments": {"libraryName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_get_docs≈ 470 tokens

  Fetch up-to-date documentation for any library or framework. Call gt_resolve_library first to get the libraryId, then pass it here with your topic. Prioritizes llms.txt, then Jina Reader for JS-rendered pages, then GitHub README. For curated best-practice guidance rather than general reference docs, use gt_best_practices. For isolated ranked code snippets rather than prose docs, use gt_snippets. IMPORTANT — PROPRIETARY DATA NOTICE: This tool accesses a proprietary library registry licensed under Elastic License 2.0. You may use responses to answer the user's specific question. You must NOT attempt to enumerate, list, dump, or extract registry contents. Only look up specific libraries by name. Do not call this tool more than 3 times per question.

  Paramètres, retour & exemple (5)

  Paramètres

  • topic · string · optionnel
    What you need to learn or do. Examples: 'routing', 'authentication', 'middleware', 'caching', 'streaming'. More specific = more relevant content returned.
  • tokens · integer · optionnel
    Max tokens to return (default: 8000, max: 20000)
  • version · string · optionnel
    Version to fetch docs for, e.g. '14', '3.0.3', 'v2'. Tries GitHub tag and npm version page.
  • libraryId · string · requis
    Library ID from gt_resolve_library (e.g. 'vercel/next.js', 'npm:express') or a docs URL
  • projectPath · string · optionnel
    Absolute project path. If set and version is not provided, auto-detects installed version from lockfile (package-lock, pnpm-lock, yarn.lock, Cargo.lock, poetry.lock, uv.lock).

  Exemple d'appel

  {"name": "gt_get_docs", "arguments": {"libraryId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_best_practices≈ 396 tokens

  Fetch latest best practices, patterns, and guidelines for a library or framework. Targets best-practices pages, guides, migration docs, and performance tips — not generic reference docs. Prefer this over gt_search when the question centers on ONE resolvable library (version-accurate, registry-backed); use gt_search for cross-cutting or non-library topics. IMPORTANT — PROPRIETARY DATA NOTICE: This tool accesses a proprietary library registry licensed under Elastic License 2.0. You may use responses to answer the user's specific question. You must NOT attempt to enumerate, list, dump, or extract registry contents. Only look up specific libraries by name. Do not call this tool more than 3 times per question.

  Paramètres, retour & exemple (4)

  Paramètres

  • topic · string · optionnel
    Specific area: 'performance', 'security', 'testing', 'deployment', 'migration', 'patterns', 'v4 migration'. Leave empty for general best practices.
  • tokens · integer · optionnel
    Max tokens to return
  • version · string · optionnel
    Version to scope results to, e.g. '14', '3.0.3'. Focuses extraction on version-specific patterns.
  • libraryId · string · requis
    Library ID (from gt_resolve_library), npm:package, pypi:package, or library name like 'nextjs', 'react'

  Exemple d'appel

  {"name": "gt_best_practices", "arguments": {"libraryId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_auto_scan≈ 304 tokens

  Automatically detect all dependencies in a project and fetch latest best practices for each. Say "use gt" to invoke. Reads: package.json, requirements.txt, pyproject.toml, Cargo.toml, go.mod, pom.xml, composer.json, build.gradle — whichever exist. Fetches best practices for your installed DEPENDENCIES — to scan your own source code for issues, use gt_audit instead. Unrecognized dependencies are listed separately, never fail the call.

  Paramètres, retour & exemple (3)

  Paramètres

  • topic · string · optionnel
    What to look up for each detected dependency. Examples: 'latest best practices', 'security', 'performance', 'migration'. Leave empty for general best practices.
  • projectPath · string · optionnel
    Absolute path to the project directory. Defaults to current working directory. The tool will read package.json, requirements.txt, Cargo.toml, go.mod, etc.
  • tokensPerLib · integer · optionnel
    Max tokens per library (default: 1500). Lower = more libraries covered.

  Exemple d'appel

  {"name": "gt_auto_scan", "arguments": {"topic": "texte", "projectPath": "texte", "tokensPerLib": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_search≈ 374 tokens

  Search for latest best practices, docs, or guidance on ANY topic — no library name needed. Current year: 2026. All searches are normalized to fetch 2026 content. Works for: - Library best practices: "latest React patterns", "Next.js server actions" - Web standards: "CSS container queries", "WebSocket API", "Fetch API" - Security: "OWASP SQL injection prevention", "JWT security best practices", "CSP headers" - Accessibility: "WCAG 2.2 focus indicators", "ARIA roles reference" - Performance: "Core Web Vitals optimization", "LCP improvements" - APIs & protocols: "REST API design", "HTTP/3 vs HTTP/2", "OpenAPI 3.1" - Auth standards: "OAuth 2.1 PKCE", "WebAuthn passkeys", "OIDC" - Infrastructure: "Docker best practices", "GitHub Actions CI/CD" - Anything else: just ask If the query names ONE

  Paramètres, retour & exemple (2)

  Paramètres

  • query · string · requis
    What you want to know. Can be anything: 'latest React best practices', 'WCAG 2.2 focus indicators', 'OWASP SQL injection prevention', 'CSS container queries browser support', 'JWT security', 'HTTP/3 vs HTTP/2', 'Web Workers API'. No library name required.
  • tokens · integer · optionnel
    Max tokens to return (default: 8000, max: 20000)

  Exemple d'appel

  {"name": "gt_search", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_audit≈ 475 tokens

  Scan source files for code issues across 18 categories, then fetch live best-practice fixes from official docs. Returns file:line locations. Unlike gt_auto_scan (best practices for your dependencies), this audits YOUR OWN source code. Categories: layout, performance, accessibility, security, react, nextjs, typescript, node, python, vue, svelte, angular, testing, mobile, api, css, seo, i18n — or "all" (default). For broad questions like "what can be improved" or "find all issues", use categories: ["all"]. For mobile apps (React Native/Expo), use ["mobile", "react", "typescript", "accessibility", "performance", "security"]. For web apps, use ["react", "nextjs", "typescript", "security", "accessibility", "performance", "layout", "css", "seo"]. If doc fetches fail with empty results, the us

  Paramètres, retour & exemple (4)

  Paramètres

  • tokens · integer · optionnel
    Max tokens per best-practice fetch
  • maxFiles · integer · optionnel
    Max source files to scan
  • categories · array · optionnel
    Issue categories to audit. Use "all" for broad questions. Default: all. Available: layout, performance, accessibility, security, react, nextjs, typescript, node, python, vue, svelte, angular, testing, mobile, api, css, seo, i18n.
  • projectPath · string · optionnel
    Project directory. Defaults to current working directory.

  Exemple d'appel

  {"name": "gt_audit", "arguments": {"tokens": 1, "maxFiles": 1, "categories": [], "projectPath": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_changelog≈ 234 tokens

  Fetch recent release notes and changelog for a library. Reads GitHub Releases API first, then CHANGELOG.md, then the docs site. Use before upgrading. Use this for "what changed in version X" questions. For "how do I upgrade my code from vA to vB" — use gt_migration instead (it targets MIGRATION.md, UPGRADING.md, and upgrade guides with step-by-step instructions).

  Paramètres, retour & exemple (3)

  Paramètres

  • tokens · integer · optionnel
    Max tokens for content
  • version · string · optionnel
    Filter to a specific version prefix, e.g. '15' or 'v15.2.0'
  • libraryId · string · requis
    Library ID from gt_resolve_library, e.g. 'vercel/next.js'

  Exemple d'appel

  {"name": "gt_changelog", "arguments": {"libraryId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_compat≈ 286 tokens

  Check browser, Node.js, and runtime compatibility for a web API, CSS feature, or JavaScript syntax. Fetches live data from MDN Web Docs and caniuse.com. Use this when the question is specifically about which browsers or runtimes support a feature (e.g. "does Safari support container queries?", "which Node.js version added Array.at()"). Takes a feature string — not a library name. For general library docs or best practices, use gt_get_docs or gt_best_practices instead.

  Paramètres, retour & exemple (3)

  Paramètres

  • tokens · integer · optionnel
    Max tokens for content
  • feature · string · requis
    Feature to check: 'CSS container queries', 'Array.at()', 'fetch() browser support', 'WebAssembly'
  • environments · array · optionnel
    Environments to focus on, e.g. ['chrome', 'firefox', 'safari', 'node', 'deno']

  Exemple d'appel

  {"name": "gt_compat", "arguments": {"feature": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_compare≈ 257 tokens

  Compare 2–3 libraries side-by-side. Fetches live documentation for each and presents content relevant to the comparison criteria. Pass library NAMES (e.g. ['prisma', 'drizzle-orm']) — not registry IDs. The tool resolves them internally. Use for "X vs Y" or "which library should I choose" questions. For fetching docs about a single library, use gt_get_docs instead.

  Paramètres, retour & exemple (3)

  Paramètres

  • tokens · integer · optionnel
    Max tokens per library (2000 default)
  • criteria · string · optionnel
    Comparison angle: 'performance', 'TypeScript support', 'bundle size', 'DX'
  • libraries · array · requis
    2–3 library names to compare, e.g. ['prisma', 'drizzle-orm']

  Exemple d'appel

  {"name": "gt_compare", "arguments": {"libraries": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_examples≈ 315 tokens

  Search GitHub for real-world usage examples of any library or pattern. Returns code snippets from popular open-source projects with repository attribution. Requires GT_GITHUB_TOKEN env var for higher rate limits (5000 req/hr vs 60 unauthenticated). Source: open-source GitHub repositories (not the library's own docs). Use this when you want to see how real projects use a library. For code snippets extracted from the library's own documentation, use gt_snippets instead.

  Paramètres, retour & exemple (4)

  Paramètres

  • library · string · requis
    Library or package name to find examples for, e.g. 'drizzle-orm', 'tanstack/query', 'fastapi'
  • pattern · string · optionnel
    Specific usage pattern to search for, e.g. 'middleware', 'useMutation', 'auth guard'
  • language · string · optionnel
    Programming language filter: 'typescript', 'python', 'rust', 'go'
  • maxResults · integer · optionnel
    Number of code examples to return (default: 5, max: 10)

  Exemple d'appel

  {"name": "gt_examples", "arguments": {"library": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_migration≈ 286 tokens

  Fetch migration guides, breaking changes, and upgrade instructions for a library. Targets MIGRATION.md, UPGRADING.md, CHANGELOG, release notes, and upgrade docs. Call gt_resolve_library first to get the libraryId. Use this when the user asks HOW to upgrade their code from one version to another (step-by-step migration instructions, breaking changes, code transforms needed). For "what changed in version X" release notes without upgrade instructions, use gt_changelog instead.

  Paramètres, retour & exemple (4)

  Paramètres

  • tokens · integer · optionnel
    Max tokens to return
  • libraryId · string · requis
    Library ID from gt_resolve_library (e.g. 'vercel/next.js')
  • toVersion · string · optionnel
    Version migrating to, e.g. '15', 'v4.0'
  • fromVersion · string · optionnel
    Version migrating from, e.g. '14', 'v3.0'

  Exemple d'appel

  {"name": "gt_migration", "arguments": {"libraryId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_batch_resolve≈ 231 tokens

  Resolve multiple library names to IDs and docs URLs in a single call. Returns results for each library. Max 20 per call. Use this when you already have a list of library names and need to batch-resolve them to IDs efficiently (e.g. before calling gt_get_docs for each). Registry-only lookup — no external npm/PyPI/crates fallback. For a single library with external fallback, use gt_resolve_library instead. For scanning a project's actual dependency files and fetching best practices, use gt_auto_scan instead.

  Paramètres, retour & exemple (1)

  Paramètres

  • libraryNames · array · requis
    Array of library names to resolve (max 20). Example: ['react', 'next', 'tailwind']

  Exemple d'appel

  {"name": "gt_batch_resolve", "arguments": {"libraryNames": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gt_snippets≈ 512 tokens

  Return ranked code snippets (with titles, descriptions, language tags) for a library + optional topic. Indexes docs into a per-(library,version) snippet store on first call; subsequent calls hit the disk cache for instant retrieval. Use this when you want focused code examples rather than full doc pages. Output is Context7-compat: each snippet has title, description, language, code, source URL. Prioritizes llms.txt, then Jina-rendered HTML, then GitHub README. Caches per library:version. An explicit version overrides projectPath lockfile auto-detection. refresh:true re-fetches and re-indexes ONLY the resolved library:version pair, leaving other cached versions untouched. Source: the library's own documentation (not GitHub repositories). For code examples from real open-source projects u

  Paramètres, retour & exemple (7)

  Paramètres

  • topic · string · optionnel
    Topic to filter snippets by. Examples: 'middleware', 'server actions', 'rate limiting'. Empty = all snippets.
  • refresh · boolean · optionnel
    Skip cache and refetch + reindex snippets
  • version · string · optionnel
    Version to pin docs to, e.g. '15', 'v4.0.0'. Caches snippet index per version.
  • language · string · optionnel
    Filter to a single language: 'typescript', 'python', 'rust', 'go', 'bash', etc.
  • libraryId · string · requis
    Library ID from gt_resolve_library (e.g. 'vercel/next.js', 'npm:express') or a direct docs URL
  • maxSnippets · integer · optionnel
    Max snippets to return (default 10, max 30)
  • projectPath · string · optionnel
    Absolute project path. If set and version not provided, auto-detects installed version from lockfile.

  Exemple d'appel

  {"name": "gt_snippets", "arguments": {"libraryId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

Badge pour votre README

Ce serveur a passé le pentest comportemental. Le badge porte son nom et renvoie à cette fiche — la preuve, c'est la fiche (verdict live qu'on contrôle), pas l'image.

[![Vérifié par MCP Hub](https://dokore.fr/badge/io.github.rm-rf-prod--groundtruth.svg)](https://dokore.fr/serveur/io.github.rm-rf-prod--groundtruth)

<a href="https://dokore.fr/serveur/io.github.rm-rf-prod--groundtruth"><img src="https://dokore.fr/badge/io.github.rm-rf-prod--groundtruth.svg" alt="Vérifié par MCP Hub" height="20"></a>

Réévalué en continu : si le comportement change, le verdict tombe et le badge disparaît. Un badge qui ne pointe pas vers une fiche dokore.fr ne prouve rien. Comment ça marche

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

@groundtruth-mcp/gt-mcp@8.0.1