Skip to content
Melvea logo

Melvea MCP server

Which servers in the official MCP registry are Melvea's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Melvea

Whose server it is
  • Registry namecom.melvea/local-discoveryverified in the MCP registry

The registry name sits under melvea.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14
  • Stateanswerschecked 2026-10-14
  • Tools4
  • Server calls itselfmelvea-local-discovery
  • Server version0.1.0
  • Protocol version2024-11-05

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 67 ms.

Tools it offers4 tools · read 2026-10-14
  • find_local_producers

    Find local honey producers near a specific place, optionally filtered by honey varietal. Requires a place name in `near` — never call this tool without one. Returns producer name, location, distance, distance_basis (farm_location vs…

  • get_producer

    Get the full directory profile for one specific producer by its slug, including location, declared honey types, contact channels, and verification status. Use this after find_local_producers (or search) when the user wants more detail on…

  • search

    Search the Melvea local honey directory by free-text query and return matching producers as a list of results (id, title, url). Designed for ChatGPT Deep Research and Company Knowledge. Use for any local-honey discovery query that names…

  • fetch

    Retrieve the full Melvea record for one producer by id, returning name, location, declared honey types, contact info, verification status, and profile URL. Use after search to pull complete detail on a result. For richer Deep Research…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "local-discovery": {
      "type": "http",
      "url": "https://mcp.melvea.com"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.