MCP.Market

Invisible Exit MCP server

online · 100% uptime
by kindrat86·io.github.kindrat86/invisibleexit·v1.0.0
No reviews yet

Faceless micro-SaaS system for employed professionals. Build $4K/mo without quitting

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

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Invisible Exit yet.

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

Invisible Exit tools (3)

write = sends, deletes, buys or posts
  • search_freedom_calculatorFree

    Calculate your freedom number, the monthly recurring revenue needed to cover living expenses and optionally leave your job.

  • search_side_business_guidesFree

    Search side-business guides and micro-SaaS playbooks by topic.

  • validate_ideaFree

    Validate a micro-SaaS idea against 500+ scored blueprints. Get industry fit, revenue potential, and time-to-launch estimates.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

1 low
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 915ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenanceno repository listed3/15
  • Maintainer identityno repository or website to verify2/10

Findings (1)

  • lowNo source repository listedmaint.no-repo
Overall 67/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Invisible Exit compares

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

Safety score
67/100
higher than 25% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
312 ms
faster than 46% of 30,031 servers

What its tools let an agent do: 3 read

Install Invisible Exit in Claude Code, Cursor or VS Code

claude mcp add --transport http invisibleexit https://invisibleexit.com/api/mcp
Add to Cursor

Invisible Exit: common questions

Is Invisible Exit MCP server safe?
With care: it is graded C, so read the findings first (67/100). Read the Invisible Exit safety report
How do I install Invisible Exit?
It runs remotely at invisibleexit.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 Invisible Exit need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Invisible Exit maintained?
The latest release is v1.0.0.
Is Invisible Exit up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Invisible Exit compare with other MCP servers?
safety score 67/100 (higher than 25% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from kindrat86 →