MCP.Market

GreatWait MCP server

online · 100% uptime
by greatwait.dev·dev.greatwait/mcp·v1dd3afbdd459a08832df82e5e24a2ae4c19bc837
No reviews yet

Reliable one-off and recurring HTTPS callbacks for apps and agents.

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 GreatWait yet.

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

GreatWait 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 GreatWait 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
1,106 ms
faster than 9% of 30,031 servers

Release history: 21 versions in the registry since 2026-10-11, latest 2026-11-04, typically one every 1 day.

Install GreatWait in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://api.greatwait.dev/mcp
Add to Cursor

GreatWait: common questions

Is GreatWait MCP server safe?
Mostly: it is graded B (77/100). Read the GreatWait safety report
How do I install GreatWait?
It runs remotely at api.greatwait.dev. 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 GreatWait need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is GreatWait maintained?
The latest release is v1dd3afbdd459a08832df82e5e24a2ae4c19bc837.
Is GreatWait up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does GreatWait 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 1,106 ms (faster than 9% of 30,031 servers). Full comparison.