mcpbeat Sign in

FITsociety MCP Server

by fitsociety Your server? Claim it
answering

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

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

Uptime history 46 days of history · worst day 93%
46 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
501 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 1 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.fitsociety.io/mcp/v1
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.fitsociety.io/mcp/v1"
    }
  }
}

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.fitsociety.io/mcp/v1 streamable-http sign-in 273 ms 1 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
ProjectSend
by projectsend

Share files with your clients from your AI assistant. Free and paid ProjectSend Cloud accounts.

answering
FoxyInvoice
by foxyinvoice

Invoicing tools for AI assistants: clients, draft invoices with computed tax, and email sending.

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
Nimble CRM
by nimble-app

Connect AI assistants to Nimble CRM to access and work with customer relationship data.

answering
EK Bridge
by bereciartua

Scoped Apple Calendar and Reminders access for AI agents, with per-client grants and approvals

local only
Muvia BI
by muviabi

Company and industrial data for AI assistants: datasets, SQL, dashboards, alarms, with approvals.

answering

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 92 of 92 checks got a reply (100.0%), average response time 501 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 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 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 501 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.