# ReportRaja

> Weekly client reports: accomplishments, hours, blockers. Free.

- name: io.github.everyai-com/report-raja
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 90/100 flags: duplicate-repo
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.everyai-com%2Freport-raja
- tools: https://api.protogrid.dev/v1/servers/io.github.everyai-com%2Freport-raja/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "report-raja": {
      "type": "http",
      "url": "https://report-raja.magicteams.ai/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 99
- freshness: 100
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-97% +updated-18d-ago -duplicate-repo(15 names)
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list carries no ttlMs, so clients re-fetch it

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 4 of 4 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 977 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 8 tool changes in 30 days
- fail `stability.rug_pull`: 8 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 4, about 977 tokens to load them all
- tool set hash: 2aa037767ffa9b2cca44bf70825bcc89
- tools last changed: 2026-10-10T10:28:50.749Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.everyai-com/report-raja.svg)](https://protogrid.dev/servers/io.github.everyai-com/report-raja)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-10 `week_bounds` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Calculate week bounds for a given date. Use when you need to know the start and end of a week for a specific date. Do NOT use when you need to generate a report, use create_weekly_report.
  - after: 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.
- 2026-10-10 `report_templates` changed (description, outputSchema, annotations) **meaning changed**
  - before: List all built-in report templates. Use when you need to see available templates, NOT when you need to create a custom report (use create_weekly_report).
  - after: 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.
- 2026-10-10 `render_report_text` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Generate a weekly report as plain text. Use when you need a simple text output for email or messaging. Do NOT use when you need a formatted document; use report_templates instead.
  - after: 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.
- 2026-10-10 `create_weekly_report` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Generate a weekly report for a client. Use when you need a formatted report. Do NOT use when you need to adjust the report's text; use render_report_text instead.
  - after: 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.
- 2026-10-06 `week_bounds` changed (title, description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Monday..Sunday bounds for the week containing a date (YYYY-MM-DD).
  - after: Calculate week bounds for a given date. Use when you need to know the start and end of a week for a specific date. Do NOT use when you need to generate a report, use create_weekly_report.
- 2026-10-06 `report_templates` changed (title, description, outputSchema, annotations) **meaning changed**
  - before: List built-in report templates (freelancer, agency, standup).
  - after: List all built-in report templates. Use when you need to see available templates, NOT when you need to create a custom report (use create_weekly_report).
- 2026-10-06 `render_report_text` changed (title, description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Render a weekly report as plain text (same inputs as create_weekly_report).
  - after: Generate a weekly report as plain text. Use when you need a simple text output for email or messaging. Do NOT use when you need a formatted document; use report_templates instead.
- 2026-10-06 `create_weekly_report` changed (title, description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Build a weekly client report from accomplishments, hours, blockers and next-week plans. Nothing stored.
  - after: Generate a weekly report for a client. Use when you need a formatted report. Do NOT use when you need to adjust the report's text; use render_report_text instead.

Full history: https://api.protogrid.dev/v1/servers/io.github.everyai-com%2Freport-raja/changes

## Remotes

- https://report-raja.magicteams.ai/mcp (streamable-http, auth none, reachable true, uptime30d 0.9705882)

## Packages

_none_

## Tools (4)

- `create_weekly_report`: 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.
- `render_report_text`: 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.
- `report_templates`: 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.
- `week_bounds`: 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.