MCP.Market

PRRO.cloud MCP server

online · 100% uptime
by prro-cloud·io.github.prro-cloud/prro-mcp·v0.4.0
No reviews yet

Read-only access to PRRO.cloud fiscal cash registers, shifts, tasks, billing and webhooks.

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

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed PRRO.cloud yet.

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

PRRO.cloud 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 PRRO.cloud compares

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

Safety score
70/100
higher than 35% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
747 ms
faster than 18% of 30,031 servers

Release history: 3 versions in the registry since 2026-10-14, latest 2026-10-31, typically one every 9 days.

Install PRRO.cloud in Claude Code, Cursor or VS Code

claude mcp add --transport http prro-mcp https://mcp.prro.cloud/mcp
Add to Cursor

PRRO.cloud: common questions

Is PRRO.cloud MCP server safe?
Mostly: it is graded B (70/100). Read the PRRO.cloud safety report
How do I install PRRO.cloud?
It runs remotely at mcp.prro.cloud. 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 PRRO.cloud need an API key?
Yes. The registry entry asks for PRRO_TOKEN, Authorization.
Is PRRO.cloud maintained?
The last commit was 21 days ago (2026-10-14). The latest release is v0.4.0.
Is PRRO.cloud up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does PRRO.cloud compare with other MCP servers?
safety score 70/100 (higher than 35% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 747 ms (faster than 18% of 30,031 servers). Full comparison.