MCP.Market

Reporting Ninja MCP server

online · 100% uptime
by reportingninja.com·com.reportingninja/reporting-ninja·v1.6.0
No reviews yet

Query marketing data across 20+ ad platforms; with write access, create, schedule and share reports.

B77/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Reporting Ninja yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Reporting Ninja tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Reporting Ninja compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
381 ms
faster than 39% of 30,031 servers

Release history: 7 versions in the registry since 2026-06-29, latest 2026-10-30, typically one every 2 days.

Install Reporting Ninja in Claude Code, Cursor or VS Code

claude mcp add --transport http reporting-ninja https://mcp.reportingninja.com/mcp
Add to Cursor

Reporting Ninja: common questions

Is Reporting Ninja MCP server safe?
Mostly: it is graded B (77/100). Read the Reporting Ninja safety report
How do I install Reporting Ninja?
It runs remotely at mcp.reportingninja.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Reporting Ninja need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Reporting Ninja maintained?
The latest release is v1.6.0.
Is Reporting Ninja up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Reporting Ninja compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 381 ms (faster than 39% of 30,031 servers). Full comparison.