I've had it MCP Server

by wit221 Your server? Claim it

answering

I've had it is answering right now. Last checked 9 min ago.

Screen time and feed blocking: read your numbers, shut Reels, Shorts and For You, search guides.

Uptime history 12 days of history

12 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

386 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add ivehadit --transport http https://ivehadit.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://ivehadit.app/mcp

~/.codex/config.toml

[mcp_servers.ivehadit]
url = "https://ivehadit.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "ivehadit": {
      "url": "https://ivehadit.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "ivehadit": {
      "type": "http",
      "url": "https://ivehadit.app/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

URL	Transport	State	Latency	Checked
https://ivehadit.app/mcp	streamable-http	sign-in	308 ms	9 min ago

Alternatives to I've had it

same job, measured the same way

Foxstep: SOPs and step-by-step guides

by foxstep

Search and read your Foxstep SOPs and step-by-step guides, with their screenshots.

answering

ShotClick Screenwriting

by shotclick

Your AI writes inside real screenplays: formatted scenes, locked numbering, outlines, research.

answering

Recipes Daily

by recipes-daily

Search recipes and cooking guides on recipes-daily.com, or find recipes from ingredients you have.

4 tools answering

Savee

by savee

Read your Savee saves, boards and home feed, and search its public library. Read-only.

answering

Highlyt

by highlyt

Highlight anything you read. Then ask your AI about it: search, read and edit your highlights.

28 tools answering

Loomaly

by loomaly

One MCP for all your SEO: rankings, AI search, fixes & reports. Fixed in code, proven in numbers.

answering

Knacco

by knacco

Bring your Knacco library into your AI tool: browse, search, read guides and download files.

answering

Vid Kraken Docs

by vidkraken

Search and read the Vid Kraken API docs, guides and pricing. No sign-in needed.

2 tools answering

I've had it — questions

Answers built from our own checks of this server.

Why is there no tool list for I've had it?

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 I've had it 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 386 ms. The bar chart above shows every period we have measured.

How do I connect I've had it?

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 I've had it?

No API key is involved. I've had it 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 I've had it?

It answers our handshake in 386 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.