A
licenseA
qualityA
maintenanceMCP server for GoCertius: certified evidence, dossiers, notifications and chats via AI agents.
41
64 npm
MIT
Evlek — Northern Cyprus Property MCP Server
Officialby Evlek
Related Servers
Alternatives to Evlek — Northern Cyprus Property MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for a content-first knowledge base, enabling AI agents to search (full-text, semantic, hybrid) and retrieve Markdown documents, list content, and find related docs.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that gives AI agents the web as compact, ranked, verified evidence — no API keys, no cloud retrieval, all models local.20 npm1MIT
- AlicenseAqualityAmaintenanceMCP server enabling AI agents to search and retrieve evidence reviews from evipedia.ai on health and longevity interventions, and to suggest new interventions for review.820 npm2MIT
- AlicenseAqualityFmaintenanceMCP server for AgentFolio — the identity and reputation layer for AI agents. Query agent profiles, trust scores, verification status, and marketplace listings through 8 MCP tools.938 npm1MIT
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server for indexing and searching research materials (papers, notes, logs, READMEs) using SQLite FTS, with tools for memory management and evidence retrieval.MIT
TDQS
A3.9/5.0
Scored across 12 tools
Disambiguation2/5
Several tools have overlapping boundaries: `search` and `search_listings` serve the same data, `fetch`, `get_listing_detail`, and `get_listing_by_number` are all single-listing detail retrievers with subtle ID-type differences, and `payment_plan` currently duplicates `convert_currency`'s behavior. Descriptions help, but the distinctions are easy to get wrong.
Naming Consistency4/5
Most tool names follow a consistent `verb_noun` snake_case pattern (`search_listings`, `compare_cities`, `convert_currency`, `list_locations`). `search` and `fetch` are bare verbs and `payment_plan` is a noun phrase, which are minor deviations from an otherwise readable set.
Tool Count4/5
Twelve tools is a reasonable count for a property-data server, but a few tools are redundant (`search`, `fetch`, `get_listing_by_number`) or placeholder (`payment_plan`), so the set is slightly over-inclusive rather than tightly scoped.
Completeness4/5
The read-only property domain is well covered: listing search, detailed retrieval, price aggregates, city/district comparisons, currency conversion, and location inventory all exist. The main gaps are the promised payment-plan functionality that is not yet implemented and unavailability of holiday-home inventory, but core workflows succeed.
Maintenance
ActivityMaintained
ResponsivenessNo issues