Fursat
REMOTE · WWW.FURSAT.FUN · SCANNED SEP 20
AI-bookable curated vacation homes in Northeast India and the Himalayas. Book on WhatsApp.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 532 tokens (~177/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Fursat MCP server?
Fursat is a hosted endpoint at https://www.fursat.fun/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.fursat.fun
claude mcp add --transport http fursatdev-tech-fursat 'https://www.fursat.fun/api/mcp'
{
"mcpServers": {
"fursatdev-tech-fursat": {
"url": "https://www.fursat.fun/api/mcp"
}
}
} {
"servers": {
"fursatdev-tech-fursat": {
"type": "http",
"url": "https://www.fursat.fun/api/mcp"
}
}
} [mcp_servers.fursatdev-tech-fursat] url = "https://www.fursat.fun/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fursatdev-tech-fursat": {
"type": "remote",
"url": "https://www.fursat.fun/api/mcp",
"enabled": true
}
}
} openclaw mcp add fursatdev-tech-fursat --url 'https://www.fursat.fun/api/mcp' --transport streamable-http
mcp_servers:
fursatdev-tech-fursat:
url: "https://www.fursat.fun/api/mcp" {
"McpServers": {
"fursatdev-tech-fursat": {
"Transport": "http",
"Url": "https://www.fursat.fun/api/mcp"
}
}
} assistant mcp add fursatdev-tech-fursat -t streamable-http -u 'https://www.fursat.fun/api/mcp'
{
"mcpServers": {
"fursatdev-tech-fursat": {
"type": "http",
"url": "https://www.fursat.fun/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Sept 26 +1
- Stability: 0.97 → pass security
- 5 Sept 26 −1
- Tool “start_inquiry” rewrote its description, which is the text the model reads security
- Stability: pass → 0.97 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.40 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 6 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.33 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://www.fursat.fun/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.fursat.fun | CN=YR1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | RSA 2048 | SHA256-RSA | 6650488d4681d26b0c7db45446a31749d70 |
| SANs: www.fursat.fun | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.fursat.fun. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fun. | present | 47728 | 13 | Verified |
| fursat.fun. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.fursat.fun/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.fursat.fun/api/mcp | HTTPS enforced | 308 | https://www.fursat.fun/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_listing ~54
Get details for a single Fursat home by its URL slug. Returns the canonical detail URL plus a short summary.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | URL slug of the listing (e.g., 'pudung-farm'). |
No output schema declared.
No examples provided.
search_listings ~249
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.).
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City filter, case-insensitive contains-match (e.g., 'cherrapunji', 'manali', 'shillong'). |
| maxResults | number | – | Max results to return, default 10, capped at 20. |
| minRating | number | – | Minimum Google rating, default 4.3. |
| query | string | – | Free-text keywords matched against title, city, location (e.g., 'mountain view Cherrapunji', 'lake Nainital'). |
| state | string | – | State slug (e.g., 'meghalaya', 'himachal-pradesh', 'uttarakhand', 'sikkim', 'arunachal-pradesh', 'nagaland', 'assam', 'tripura', 'manipur', 'mizoram', 'west-bengal'). |
No output schema declared.
No examples provided.
start_inquiry ~229
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkIn | string | – | Check-in date in ISO format YYYY-MM-DD. Optional; include only if the guest specified a date. |
| checkOut | string | – | Check-out date in ISO format YYYY-MM-DD. Optional; include only if the guest specified a date. |
| guests | number | – | Total number of guests. Optional. |
| notes | string | – | Free-text notes the assistant should include in the inquiry (e.g., 'celebrating an anniversary', 'need airport pickup quote'). Optional, keep under 280 chars. |
| slug | string | yes | URL slug of the Fursat listing (e.g., 'pudung-farm'). |
No output schema declared.
No examples provided.
What is the Fursat MCP server?
Fursat is an MCP server listed in the public MCP registry as io.github.fursatdev-tech/fursat. AI-bookable curated vacation homes in Northeast India and the Himalayas. Book on WhatsApp. This page covers its hosted endpoint (https://www.fursat.fun/api/mcp).
Is the Fursat MCP server safe to use?
Fursat scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Fursat MCP server expose?
Fursat exposes 3 tools: search_listings, get_listing, start_inquiry. Their descriptions and schemas cost roughly 532 tokens of context every time the server is loaded.
Does the Fursat MCP server require authentication?
No. We connected to Fursat without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fursat MCP server still maintained?
Fursat is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.