MCP.Market

Stellen-Radar MCP server

online · 100% uptime
by stellen-radar.ai·ai.stellen-radar/stellen-radar·v0.22.3

Stellensuche Deutschland: über ½ Million Stellen von Beratern, Portalen und Firmen

B77/100grade B
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 Stellen-Radar yet.

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

Stellen-Radar 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 Stellen-Radar 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
786 ms
faster than 17% of 30,031 servers

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

Install Stellen-Radar in Claude Code, Cursor or VS Code

claude mcp add --transport http stellen-radar https://connect.stellen-radar.ai/mcp
Add to Cursor

Stellen-Radar: common questions

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