For developers
and autonomous agents
Connect your LLMs and chat apps to Spanish property search through the unified Fyn MCP server.
MCP endpoint configuration
Add Fyn's public URL as a remote MCP connector in Claude or any compatible client.
transport: Streamable HTTP
Connect it to Claude in three steps
- 1
Open Claude connectors
On Pro or Max, go to Customize → Connectors and choose Add custom connector. On Team or Enterprise, an owner must add it.
- 2
Paste the Fyn URL
Use the MCP URL shown above. Fyn does not require an app install or marketplace approval.
- 3
Enable it in a conversation
Open the + menu, enable Fyn under Connectors, then describe the property you want with a location, budget, and preferences.
It also works with clients and agents that support remote MCP servers over Streamable HTTP.
Agent quickstart
The public endpoint is free during this experimental phase and requires no account, API key, or OAuth. It is rate-limited and may change; there is currently no paid plan or SLA.
- 1
Connect the transport
Configure a Streamable HTTP MCP client with https://fynfyn.top/mcp. Do not send an Authorization header.
- 2
Discover and call the tool
Run tools/list, then call search_properties with city or locations and structured constraints.
- 3
Check coverage
Read diagnostics before answering. Preserve source links and disclose blocked or unavailable sources.
{
"locale": "en",
"transaction_type": "buy",
"property_types": ["house"],
"locations": ["Valencia"],
"max_price_eur": 350000,
"strict_constraints": true
}Limits, errors, and retries
MCP responses use structured JSON-RPC errors. A 429 includes Retry-After; respect it and use bounded exponential backoff with jitter. Responses also advertise RateLimit-Limit and RateLimit-Remaining. A 413 means the body is oversized, and a 500 represents a transient service failure.
Fyn only discovers listings. It does not reserve, buy, value, or legally verify property. Portal availability changes, and every result must be verified at its original link.
Agent documentation
Contract, examples, limitations, and recovery in one file.
OpenAPI 3.1
Machine-readable description of the MCP transport and health route.
MCP server card
Server, tool, and MCP Apps resource discovery.
System health checker
Verify endpoint health and runtime status for connector calls.
Schema endpoint
Open the MCP endpoint used by developer mode and compatible clients.
Source code
Explore the connectors, MCP contract, ranking, and experiment decisions on GitHub.