mcpbeat Sign in

ClaimyApp MCP Server

by claimtagg Your server? Claim it
answering

ClaimyApp is answering right now. Last checked moments ago.

Plan trips, packing lists and luggage in ClaimyApp: read, create and change them, undoable.

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

Nothing serious here today

Today is the operative word: we check ClaimyApp 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 0 min ago.

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

Alternatives to ClaimyApp

same job, measured the same way
Gisti — AI Checklists
by antonchuraev99

Read, AI-create, and edit your Gisti checklists in plain language from any MCP client.

answering
Plantrip
by plantrip

Travel planning: day-by-day itineraries, packing lists, weather insights, and trip cost estimates

48 installs/wk local only
Rosh MCP
by rosh-studio

Create interactive web apps, games, and 3D scenes using Rosh — a plain-English language

88 installs/wk local only
fortrabbit
by fortrabbit

Read apps and environments, and create them, on the fortrabbit PHP hosting platform.

answering
PageRadar
by pageradar

Monitor web pages for changes: create monitors, list detected changes and read diffs.

answering
Wachete
by wachete

Create, read and monitor Wachete website-change wachets for a signed-in user.

answering
3DPACK.ING — 3D Bin Packing
by 3dpack

3D bin packing for freight in Claude & ChatGPT: cartons and pallets, the fit, a 3D plan in the chat.

1 tools answering
Appy smart links
by appy

Create and edit Appy smart links for apps, and read their click and install stats.

11 tools answering

ClaimyApp — questions

Answers built from our own checks of this server.

Why is there no tool list for ClaimyApp?
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 ClaimyApp working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 253 ms. The bar chart above shows every period we have measured.
How do I connect ClaimyApp?
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 ClaimyApp?
No API key is involved. ClaimyApp 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 ClaimyApp?
It answers our handshake in 253 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.