mcpbeat Sign in

Idlefy MCP Server

answering

Idlefy is answering right now. Last checked 7 min ago.

Lease AWS and GCP VMs for a set time and let them stop themselves.

Uptime history 18 days of history
18 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
187 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Idlefy every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.idlefy.com/mcp/
Settings → Connectors → Add custom connector, then paste this address
https://mcp.idlefy.com/mcp/
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.idlefy.com/mcp/"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.idlefy.com/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.idlefy.com/mcp/"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.idlefy.com/mcp/ streamable-http sign-in 190 ms 7 min ago

Alternatives to Idlefy

same job, measured the same way
clawops
by dfridkin

Deploy self-hosted OpenClaw to AWS, GCP, Azure or a local VM — a CLI and an MCP server in one.

344 installs/wk local only
API Key Case
by melavern

Local MCP tools for secret status and guarded deployment. Values never reach the agent.

168 installs/wk local only
Serverlessrun
by cloudcorprecords

AWS Lambda functions, versions, aliases, layers and settings as MCP tools.

291 installs/wk local only
Clouddocs
by cloudcorprecords

Search, read, and get recommendations for AWS documentation pages.

118 installs/wk local only
AWS CLI MCP Server
by musaddiq-dev

Python MCP server for AWS CLI inspection and operations

122 installs/wk local only
Dokku MCP Server
by dokku-mcp

MCP server for Dokku: let LLMs create, deploy, scale, configure and inspect Dokku apps.

local only
A
AWS Spapi MCP
by cesarobedfl

MCP server for Amazon SP-API - real-time inventory health, sales metrics, and price updates

78 installs/wk local only
ebman
by tombaldwin

MCP server for AWS Elastic Beanstalk: read the fleet; --allow-writes adds two-phase writes.

local only

Idlefy — questions

Answers built from our own checks of this server.

Why is there no tool list for Idlefy?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Idlefy working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 187 ms. The bar chart above shows every period we have measured.
How do I connect Idlefy?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Idlefy?
No API key is involved. Idlefy answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Idlefy?
It answers our handshake in 187 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.