mcpbeat Sign in

FITsociety MCP Server

by fitsociety Your server? Claim it
answering

FITsociety is answering right now. Last checked 9 min ago.

Access approved FITsociety clients, schedules, bookings and coaching data with AI assistants.

Uptime history 16 hours of history
16 hours agonow
100.0%
Uptime 24h
58 of 58 checks
Tools
hidden behind auth
318 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

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

run in your terminal
claude mcp add mcp --transport http https://mcp.fitsociety.io/mcp/v1
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.fitsociety.io/mcp/v1"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.fitsociety.io/mcp/v1"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.fitsociety.io/mcp/v1"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.fitsociety.io/mcp/v1"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.fitsociety.io/mcp/v1 streamable-http needs key 256 ms 9 min ago

Alternatives to FITsociety

same job, measured the same way
42min
by 42min

Scheduling for AI assistants: bookings, availability, meeting polls and routing forms.

answering
Statistikdata
by statistikdata

Swedish open data for Claude and other AI assistants - verified, with sources.

answering
OnlineFitness.app
by onlinefitness

Manage fitness coaching clients, workouts, programs, chats and funnels from your assistant.

answering
Webull OpenAPI
by webull-inc

MCP server for Webull OpenAPI: trading and market data access for AI assistants

554 installs/wk local only
MCP Devkit Server
by mapbox

Provides AI assistants with direct access to Mapbox developer APIs and documentation.

302 installs/wk answering
Spines
by superagentic

Access book collections, reading lists, and bookshelf recognition from AI assistants.

22 installs/wk local only
Conarium
by dogrucanemek-alt

Governed database access for AI assistants: masking, signed receipts, coverage reconciliation.

705 installs/wk local only
SqlAugur
by mbentham

MCP server providing AI assistants with safe, read-only SQL Server access

local only

FITsociety — questions

Answers built from our own checks of this server.

Why is there no tool list for FITsociety?
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 FITsociety working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 58 of 58 checks got a reply (100.0%), average response time 318 ms. The bar chart above shows every period we have measured.
How do I connect FITsociety?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path 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 FITsociety?
No API key is involved. FITsociety 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 FITsociety?
It answers our handshake in 318 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.