mcpbeat Sign in

Kukie.io MCP Server

answering

Kukie.io is answering right now. Last checked 4 min ago.

Read your Kukie.io sites, make previewed changes to banners and settings, and start scans.

Uptime history 10 days of history · worst day 99%
10 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
264 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Kukie.io missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

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 4 min ago.

run in your terminal
claude mcp add ai-connector --transport http https://app.kukie.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.kukie.io/mcp
~/.codex/config.toml
[mcp_servers.ai-connector]
url = "https://app.kukie.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ai-connector": {
      "url": "https://app.kukie.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "ai-connector": {
      "type": "http",
      "url": "https://app.kukie.io/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://app.kukie.io/mcp streamable-http sign-in 278 ms 4 min ago

Alternatives to Kukie.io

same job, measured the same way
I
index365 MCP
by index365usa

Start index365 scans and read prioritized findings your coding agent can use.

55 installs/wk local only
Routine Run
by routinerun

Read, start and move the routines on your iPhone; suggest changes you approve on the phone.

answering
Foyer
by hifoyer

Read and search your Foyer AI call screener: calls, voicemails, what callers said. Change settings.

answering
SeggWat
by seggwat

Manage feedback, ratings, surveys, changelogs, and review tasks in your SeggWat projects.

answering
Kasset
by kasset

Search and read your Kasset meetings and conversations: notes, transcripts and action items.

answering
cubic
by cubic

Triage cubic AI code review findings, start PR reviews, and read wikis, scans, and team learnings.

answering
Auditon security assessments
by auditon

Read-only access to your Auditon vulnerability scans: findings, endpoints, reports and changes.

answering
N
Notify Me! Back in Stock, Pre-Order & Wishlist
by notify-me

Read analytics and change back-in-stock, pre-order, wishlist and low-stock settings on Shopify.

answering

Kukie.io — questions

Answers built from our own checks of this server.

Why is there no tool list for Kukie.io?
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 Kukie.io 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 264 ms. The bar chart above shows every period we have measured.
How do I connect Kukie.io?
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 Kukie.io?
No API key is involved. Kukie.io 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 Kukie.io?
It answers our handshake in 264 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.