mcpbeat Sign in

Fikst MCP Server

answering

Fikst is answering right now. Last checked 15 min ago.

CRM and field service for Dutch installation companies. Configure your whole environment.

Uptime history 48 days of history
48 days agonow
100.0%
Uptime 24h
90 of 90 checks
Tools
hidden behind auth
296 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

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

run in your terminal
claude mcp add crm --transport http https://mcp.fikst.cloud/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "crm": {
      "url": "https://mcp.fikst.cloud/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.crm]
url = "https://mcp.fikst.cloud/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "crm": {
      "url": "https://mcp.fikst.cloud/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "crm": {
      "url": "https://mcp.fikst.cloud/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://mcp.fikst.cloud/mcp streamable-http sign-in 259 ms 15 min ago

Alternatives to Fikst

same job, measured the same way
Deployment.io
by deployment-io

Deploy apps on your cloud. Create environments, configure infrastructure, and monitor jobs.

answering
Server Side Tracking
by tracklution

Server-side conversion tracking, installed and configured by your AI coding agent.

38 installs/wk local only
Aem MCP Server
by easingthemes

AEM MCP server. Chat with your AEM instance for content, component, and asset operations.

147 installs/wk local only
Mazingira MCP
by gabrielmahia

MCP server for environment and climate coordination in East Africa (mazingira = environment)

99 installs/wk local only
Env Contract MCP
by mrfentmen

Local value-free environment contract and configuration drift inspection. Tools include inspect...

local only
Codat
by usefulapi

MCP server for Codat — companies, connections, invoices, bills and financial statements.

28 tools answering
Idle9
by idle9

A persistent Linux computer for your AI: what it installs and writes survives the session.

answering
Config Weather MCP
by mrfentmen

Measure local configuration complexity and environment contract pressure without returning...

local only

Fikst — questions

Answers built from our own checks of this server.

Why is there no tool list for Fikst?
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 Fikst working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 90 checks got a reply (100.0%), average response time 296 ms. The bar chart above shows every period we have measured.
How do I connect Fikst?
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 Fikst?
No API key is involved. Fikst 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 Fikst?
It answers our handshake in 296 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.