# ReportRaja (remote · report-raja.magicteams.ai)

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

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `report-raja.magicteams.ai`: 74/100 (this document), [markdown](https://verifymcp.io/servers/everyai-com-report-raja/report-raja.md), [page](https://verifymcp.io/servers/everyai-com-report-raja/report-raja)

## Channel facts

- Endpoint: `https://report-raja.magicteams.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-07.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 424 tokens (~106/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ReportRaja MCP server?

ReportRaja is a hosted endpoint at https://report-raja.magicteams.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http everyai-com-report-raja 'https://report-raja.magicteams.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "everyai-com-report-raja": {
      "url": "https://report-raja.magicteams.ai/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.everyai-com-report-raja]
url = "https://report-raja.magicteams.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "everyai-com-report-raja": {
      "type": "remote",
      "url": "https://report-raja.magicteams.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add everyai-com-report-raja --url 'https://report-raja.magicteams.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  everyai-com-report-raja:
    url: "https://report-raja.magicteams.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "everyai-com-report-raja": {
      "Transport": "http",
      "Url": "https://report-raja.magicteams.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add everyai-com-report-raja -t streamable-http -u 'https://report-raja.magicteams.ai/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-07 (score 74, +6)

- [security] Tool “create_weekly_report” rewrote its description, which is the text the model reads
- [security] Tool “render_report_text” rewrote its description, which is the text the model reads
- [security] Tool “report_templates” rewrote its description, which is the text the model reads
- [security] Tool “week_bounds” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 54 → 106
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Tool “create_weekly_report” now declares an output schema
- [functional improvement] Tool “render_report_text” now declares an output schema
- [functional improvement] Tool “report_templates” now declares an output schema
- [functional improvement] Tool “week_bounds” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: fair → good
- [cosmetic] “create_weekly_report” reworded the description of “accomplishments”
- [cosmetic] “create_weekly_report” reworded the description of “blockers”
- [cosmetic] “create_weekly_report” reworded the description of “client_name”
- [cosmetic] “create_weekly_report” reworded the description of “hours_logged”
- [cosmetic] “create_weekly_report” reworded the description of “next_week”
- [cosmetic] “create_weekly_report” reworded the description of “week_start”
- [cosmetic] “render_report_text” reworded the description of “accomplishments”
- [cosmetic] “render_report_text” reworded the description of “blockers”
- [cosmetic] “render_report_text” reworded the description of “client_name”
- [cosmetic] “render_report_text” reworded the description of “hours_logged”
- [cosmetic] “render_report_text” reworded the description of “next_week”
- [cosmetic] “render_report_text” reworded the description of “week_start”
- [cosmetic] “week_bounds” reworded the description of “date”
- [cosmetic] Tool “create_weekly_report” changed its title: Create weekly report
- [cosmetic] Tool “render_report_text” changed its title: Render report text
- [cosmetic] Tool “report_templates” changed its title: Report templates
- [cosmetic] Tool “week_bounds” changed its title: Week bounds

### 2026-10-05 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-03 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-02 (score 66)

First indexed and scored.

## MCP tools (4)

### `create_weekly_report` (~150 tokens)

Create weekly report

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.

Input parameters:

- `accomplishments` (array, required): A list of accomplishments achieved during the week
- `blockers` (array): A list of issues or obstacles encountered during the week
- `client_name` (string, required): The name of the client for whom the report is being generated
- `hours_logged` (number): The total number of hours worked during the week
- `next_week` (array): A list of tasks planned for the next week
- `week_start` (string, required): The start date of the week in YYYY-MM-DD format

Output parameters:

- `accomplishments` (array): List of accomplishments for the week.
- `blockers` (array): List of blockers encountered during the week.
- `client_name` (string): The name of the client for whom the report is generated.
- `hours_logged` (number): Total hours logged for the week.
- `next_week` (array): List of plans for the next week.
- `report_id` (string): Unique identifier for the generated report.
- `report_text` (string): The formatted text of the weekly report.
- `week_start` (string): The start date of the week for which the report is generated.

### `render_report_text` (~150 tokens)

Render report text

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.

Input parameters:

- `accomplishments` (array, required): A list of accomplishments achieved during the week
- `blockers` (array): A list of issues or obstacles encountered during the week
- `client_name` (string, required): The name of the client for whom the report is being generated
- `hours_logged` (number): The total number of hours worked during the week
- `next_week` (array): A list of tasks planned for the next week
- `week_start` (string, required): The start date of the week in YYYY-MM-DD format

Output parameters:

- `accomplishments` (array): The list of accomplishments for the week.
- `blockers` (array): The list of blockers encountered during the week.
- `client_name` (string): The name of the client for whom the report is generated.
- `hours_logged` (number): The total hours logged for the week.
- `next_week` (array): The list of tasks planned for the next week.
- `report_text` (string): The generated plain text report.
- `week_start` (string): The start date of the week covered by the report.

### `report_templates` (~40 tokens)

Report templates

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).

Output parameters:

- `results` (array): List of report templates entries.

### `week_bounds` (~65 tokens)

Week bounds

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.

Input parameters:

- `date` (string, required): The date in YYYY-MM-DD format.

Output parameters:

- `endDate` (string): The end date of the week (Sunday) in YYYY-MM-DD format.
- `startDate` (string): The start date of the week (Monday) in YYYY-MM-DD format.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/everyai-com-report-raja/report-raja#diagnostics

## Score history

- 2026-10-07: 74
- 2026-10-05: 68
- 2026-10-04: 67
- 2026-10-03: 67
- 2026-10-02: 66

## Common questions

### What is the ReportRaja MCP server?

ReportRaja is an MCP server listed in the public MCP registry as io.github.everyai-com/report-raja. Weekly client reports: accomplishments, hours, blockers. Free. This page covers its hosted endpoint (https://report-raja.magicteams.ai/mcp).

### Is the ReportRaja MCP server safe to use?

ReportRaja scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ReportRaja MCP server expose?

ReportRaja exposes 4 tools: create_weekly_report, render_report_text, report_templates, week_bounds. Their descriptions and schemas cost roughly 405 tokens of context every time the server is loaded.

### Does the ReportRaja MCP server require authentication?

No. We connected to ReportRaja without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ReportRaja MCP server still maintained?

ReportRaja is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://report-raja.magicteams.ai/mcp
- Repository: https://github.com/everyai-com/sahadeva
- Changelog RSS feed: https://verifymcp.io/servers/everyai-com-report-raja/report-raja.xml
- Changelog JSON feed: https://verifymcp.io/servers/everyai-com-report-raja/report-raja.json
- HTML version of this page: https://verifymcp.io/servers/everyai-com-report-raja/report-raja