io.github.everyai-com/report-raja

Est-ce que io.github.everyai-com/report-raja est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.everyai-com/report-raja » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. 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.

Les 4 outils

• create_weekly_report≈ 650 tokens

  Build a structured weekly client report (report ID, week start/end, accomplishments, hours, blockers, next-week plan) as data fields. Nothing is stored. Use when the report data will be processed or shown as fields. Do NOT use for a ready-to-send text version; use render_report_text.

  Paramètres, retour & exemple (6)

  Paramètres

  • blockers · array · optionnel
    Open issues blocking progress, one per entry, e.g. ["Waiting on API review"]. Default none.
  • next_week · array · optionnel
    Planned tasks for next week, one per entry. Default none.
  • week_start · string · requis
    First day of the reported week, YYYY-MM-DD (normally the Monday; use week_bounds to find it), e.g. 2026-09-28. The week ends 6 days later.
  • client_name · string · requis
    Client the report is for, e.g. "Globex"
  • hours_logged · number · optionnel
    Total hours worked this week, >= 0, e.g. 32. Omit if not tracked.
  • accomplishments · array · requis
    What was done this week, one short item per entry (at least one), e.g. ["Shipped login", "Fixed 3 bugs"]

  Exemple d'appel

  {"name": "create_weekly_report", "arguments": {"week_start": "texte", "client_name": "texte", "accomplishments": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"blockers": [], "week_end": "texte", "next_week": [], "report_id": "texte", "week_start": "texte", "client_name": "texte", "hours_logged": 1, "accomplishments": []}}

• render_report_text≈ 454 tokens

  Build a weekly client report from the same inputs as create_weekly_report and return it as plain text (header, accomplishments, hours, blockers, next week) ready to paste into an email or chat. Use when the user wants a readable report to send. Do NOT use when structured fields are needed; use create_weekly_report.

  Paramètres, retour & exemple (6)

  Paramètres

  • blockers · array · optionnel
    Open issues blocking progress, one per entry, e.g. ["Waiting on API review"]. Default none.
  • next_week · array · optionnel
    Planned tasks for next week, one per entry. Default none.
  • week_start · string · requis
    First day of the reported week, YYYY-MM-DD (normally the Monday; use week_bounds to find it), e.g. 2026-09-28. The week ends 6 days later.
  • client_name · string · requis
    Client the report is for, e.g. "Globex"
  • hours_logged · number · optionnel
    Total hours worked this week, >= 0, e.g. 32. Omit if not tracked.
  • accomplishments · array · requis
    What was done this week, one short item per entry (at least one), e.g. ["Shipped login", "Fixed 3 bugs"]

  Exemple d'appel

  {"name": "render_report_text", "arguments": {"week_start": "texte", "client_name": "texte", "accomplishments": []}}

  Exemple de retour

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

• report_templates≈ 267 tokens

  List the built-in report layouts (freelancer weekly, agency client update, standup digest) and the sections each one covers. Use when the user asks what report styles exist or which sections to include. Do NOT use to build a report; use create_weekly_report or render_report_text.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "report_templates", "arguments": {}}

  Exemple de retour

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

• week_bounds≈ 221 tokens

  Return the Monday-to-Sunday week containing a given date (UTC). Use to turn a date like 'Oct 2' into the week_start for a report. Do NOT use to build the report itself; use create_weekly_report or render_report_text.

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Any date in the week, YYYY-MM-DD, e.g. 2026-10-02

  Exemple d'appel

  {"name": "week_bounds", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"week_end": "texte", "week_start": "texte"}}

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

https://report-raja.magicteams.ai/mcp