Fursat MCP Server

by fursatdev-tech Your server? Claim it

not responding

Fursat is listed as active in the registry but did not answer our last check. It exposes 3 tools.

AI-bookable curated vacation homes in Northeast India and the Himalayas. Book on WhatsApp.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 2%

91 days agonow

13.0%

Uptime 24h

12 of 92 checks

Tools

read from the server

413 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 4 September 2026. No other catalogue keeps this.

29 Oct 3 tools changed the parameters they ask for get_listing, search_listings, start_inquiry

4 Sep a tool description was rewritten start_inquiry

Fursat does not always answer

Over the last week it answered 15.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add fursat --transport http https://www.fursat.fun/api/mcp

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

https://www.fursat.fun/api/mcp

~/.codex/config.toml

[mcp_servers.fursat]
url = "https://www.fursat.fun/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "fursat": {
      "url": "https://www.fursat.fun/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "fursat": {
      "type": "http",
      "url": "https://www.fursat.fun/api/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

listing

get_listing

Get details for a single Fursat home by its URL slug. Returns the canonical detail URL plus a short summary.

listings

search_listings

Search Fursat's curated catalog of vacation homes in Northeast India and the Himalayas. Returns published homes with a Google rating of 4.3 or higher. Use this when a traveler asks about accommodation suggestions in this region (Meghalaya, Himachal, Uttarakhand, Sikkim, Assam, Arunachal Pradesh, etc.).

start

start_inquiry

Generate a WhatsApp inquiry link for a Fursat home. Returns a wa.me URL that opens WhatsApp with a prefilled message identifying the listing and (optionally) the guest's dates, party size, and notes. Use this when a traveler wants to actually book or inquire about a specific home after seeing it in search results. Bookings on Fursat happen on WhatsApp - there is no online checkout.

Endpoints

URL	Transport	State	Latency	Checked
https://www.fursat.fun/api/mcp	streamable-http	answering	82 ms	0 min ago

Alternatives to Fursat

same job, measured the same way

Atendio

by atendio

Read WhatsApp conversations and analytics, and manage AI assistant rules in Atendio.

answering

Chatfuel

by chatfuel

Create AI agents that answer customers on WhatsApp, Instagram, Messenger, TikTok and web chat.

answering

Ebenova Fieldops

by dgtalquantumleap-ai

WhatsApp booking, staff coordination, and invoice recovery for services.

44 installs/wk local only

Kommo

by mcp-dir

Kommo CRM (formerly amoCRM), the conversation-first sales CRM (WhatsApp, Instagram, Telegram) used b

48 tools answering

Amomic-AI Docs

by amomic

Search the Amomic-AI docs and REST API for AI agents on calls, WhatsApp, chat and email.

3 tools answering

Whatsapp MCP

by meharajm

WhatsApp MCP Server - Human-in-the-loop for AI agents via WhatsApp

189 installs/wk local only

ConverZAP — WhatsApp (official API)

by converzap

WhatsApp via the official Meta API: contacts, conversations, messages, CRM deals and campaigns.

answering

DarkFunnels documentation

by darkfunnels

Search and read the DarkFunnels docs: WhatsApp AI sales agents connected by QR, no Meta Cloud API.

3 tools answering

Fursat — questions

Answers built from our own checks of this server.

What can Fursat do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_listing, search_listings, start_inquiry. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Fursat working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 12 of 92 checks got a reply (13.0%), average response time 413 ms. The bar chart above shows every period we have measured.

Is Fursat still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists Fursat as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Fursat?

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.

Does Fursat need an API key?

No. Fursat completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Fursat?

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