ReportRaja
REMOTE · REPORT-RAJA.MAGICTEAMS.AI · SCANNED OCT 7
Weekly client reports: accomplishments, hours, blockers. Free.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 424 tokens (~106/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · report-raja.magicteams.ai
claude mcp add --transport http everyai-com-report-raja 'https://report-raja.magicteams.ai/mcp'
{
"mcpServers": {
"everyai-com-report-raja": {
"url": "https://report-raja.magicteams.ai/mcp"
}
}
} {
"servers": {
"everyai-com-report-raja": {
"type": "http",
"url": "https://report-raja.magicteams.ai/mcp"
}
}
} [mcp_servers.everyai-com-report-raja] url = "https://report-raja.magicteams.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"everyai-com-report-raja": {
"type": "remote",
"url": "https://report-raja.magicteams.ai/mcp",
"enabled": true
}
}
} openclaw mcp add everyai-com-report-raja --url 'https://report-raja.magicteams.ai/mcp' --transport streamable-http
mcp_servers:
everyai-com-report-raja:
url: "https://report-raja.magicteams.ai/mcp" {
"McpServers": {
"everyai-com-report-raja": {
"Transport": "http",
"Url": "https://report-raja.magicteams.ai/mcp"
}
}
} assistant mcp add everyai-com-report-raja -t streamable-http -u 'https://report-raja.magicteams.ai/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Oct 26 +6
- 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 security
- Schema quality: 54 → 106 ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Tool “create_weekly_report” now declares an output schema ▲ functional
- Tool “render_report_text” now declares an output schema ▲ functional
- Tool “report_templates” now declares an output schema ▲ functional
- Tool “week_bounds” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: fair → good functional
- “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 cosmetic
- 5 Oct 26 +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.
- 3 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Oct 2026 · Probed https://report-raja.magicteams.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=magicteams.ai | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 43f5107c9c7b250a13323639a29386fc |
| SANs: magicteams.ai, report-raja.magicteams.ai, *.report-raja.magicteams.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of report-raja.magicteams.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| magicteams.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://report-raja.magicteams.ai/mcp | Verified | 200 | |
| http (plaintext) | http://report-raja.magicteams.ai/mcp | HTTPS enforced | 301 | https://report-raja.magicteams.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_weekly_report Create weekly report ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accomplishments | array | yes | A list of accomplishments achieved during the week |
| blockers | array | – | A list of issues or obstacles encountered during the week |
| client_name | string | yes | 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 | yes | The start date of the week in YYYY-MM-DD format |
| Name | Type | Req | Description |
|---|---|---|---|
| accomplishments | array | yes | List of accomplishments for the week. |
| blockers | array | – | List of blockers encountered during the week. |
| client_name | string | yes | 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 | yes | Unique identifier for the generated report. |
| report_text | string | yes | The formatted text of the weekly report. |
| week_start | string | yes | The start date of the week for which the report is generated. |
No examples provided.
render_report_text Render report text ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accomplishments | array | yes | A list of accomplishments achieved during the week |
| blockers | array | – | A list of issues or obstacles encountered during the week |
| client_name | string | yes | 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 | yes | The start date of the week in YYYY-MM-DD format |
| Name | Type | Req | Description |
|---|---|---|---|
| accomplishments | array | yes | The list of accomplishments for the week. |
| blockers | array | – | The list of blockers encountered during the week. |
| client_name | string | yes | 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 | yes | The generated plain text report. |
| week_start | string | yes | The start date of the week covered by the report. |
No examples provided.
report_templates Report templates ~40
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).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | List of report templates entries. |
No examples provided.
week_bounds Week bounds ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | The date in YYYY-MM-DD format. |
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | The end date of the week (Sunday) in YYYY-MM-DD format. |
| startDate | string | yes | The start date of the week (Monday) in YYYY-MM-DD format. |
No examples provided.
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.