_ registry / mcp http-sse · checked 2h ago

mcp-typescript server on vercel

https://www.fursat.fun

Registry code: 7b028e6db2e9655e

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://www.fursat.fun/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is mcp-typescript server on vercel live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is mcp-typescript server on vercel free to use?
Yes — the hub reached it with no key and no payment.
What tools does mcp-typescript server on vercel have?
3 tools: get_listing, start_inquiry, search_listings.
Is mcp-typescript server on vercel safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
272ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 285 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search vacation homes in northeast india
  • get details of a vacation home
  • create a whatsapp booking inquiry link
takes → gives
text, data → data
tools
2 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_listings reads open 24h ago

    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.).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "city": {
          "type": "string",
          "description": "City filter, case-insensitive contains-match (e.g., 'cherrapunji', 'manali', 'shillong')."
        },
        "query": {
          "type": "string",
          "description": "Free-text keywords matched against title, city, location (e.g., 'mountain view Cherrapunji', 'lake Nainital')."
        },
        "state": {
          "type": "string",
          "description": "State slug (e.g., 'meghalaya', 'himachal-pradesh', 'uttarakhand', 'sikkim', 'arunachal-pradesh', 'nagaland', 'assam', 'tripura', 'manipur', 'mizoram', 'west-bengal')."
        },
        "minRating": {
          "type": "number",
          "description": "Minimum Google rating, default 4.3."
        },
        "maxResults": {
          "type": "number",
          "description": "Max results to return, default 10, capped at 20."
        }
      }
    }
    arguments 26 lines
  • get_listing reads unknown 24h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "URL slug of the listing (e.g., 'pudung-farm')."
        }
      }
    }
    arguments 13 lines
  • start_inquiry changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "URL slug of the Fursat listing (e.g., 'pudung-farm')."
        },
        "notes": {
          "type": "string",
          "description": "Free-text notes the assistant should include in the inquiry (e.g., 'celebrating an anniversary', 'need airport pickup quote'). Optional, keep under 280 chars."
        },
        "guests": {
          "type": "number",
          "description": "Total number of guests. Optional."
        },
        "checkIn": {
          "type": "string",
          "description": "Check-in date in ISO format YYYY-MM-DD. Optional; include only if the guest specified a date."
        },
        "checkOut": {
          "type": "string",
          "description": "Check-out date in ISO format YYYY-MM-DD. Optional; include only if the guest specified a date."
        }
      }
    }
    arguments 29 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 7b028e6db2e9655e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7b028e6db2e9655e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/7b028e6db2e9655e/badge.svg)](https://brick.blue/agent/7b028e6db2e9655e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.