mcpbeat

Melvea Local Honey Discovery MCP Server

com.melvea/local-discovery
answering

Melvea Local Honey Discovery is answering right now. Last checked 14 min ago. It exposes 4 tools.

Citation-backed honey producer discovery by place or varietal. Free, no auth.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
108 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add local-discovery --transport http https://mcp.melvea.com
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "local-discovery": {
      "url": "https://mcp.melvea.com"
    }
  }
}
~/.codex/config.toml
[mcp_servers.local-discovery]
url = "https://mcp.melvea.com"
.cursor/mcp.json
{
  "mcpServers": {
    "local-discovery": {
      "url": "https://mcp.melvea.com"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "local-discovery": {
      "url": "https://mcp.melvea.com"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fetch
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 answers, fetch the top several search results rather than just one, so varietal and contact detail are populated across the set.
local
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, declared honey types, and contact channels (website, etc.) where listed, ordered by distance. Use this when the user asks to find, buy, or visit local honey near a town, city, ZIP, or US state — e.g. 'local honey near Asheville,' 'who sells honey near me in Charlotte,' 'sourwood honey near Atlanta,' 'honey producers in Oregon.' Put the PLACE in `near` and any VARIETAL in `variety` (separate fields) — do not combine them into one string. US state names (e.g. 'Oregon', 'North Carolina') list producers across that state; cities and ZIPs search a local radius. Named sub-state regions (e.g. 'Florida Panhandle') are not supported — use a city or the state name instead. Coverage is deepest in the Southeastern US, where most locations have a listed producer within 25 miles — the rural Mississippi Delta is the exception; coverage across the rest of the US is expanding. Don't use this for general honey questions (what is sourwood honey, health benefits, recipes) — it only returns directory listings, not knowledge. If no producer is listed nearby, the tool returns an honest empty result with a coverage note; relay that rather than inventing producers.
producer
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 a particular listing. Don't use this to browse or search — it requires an exact producer slug.
search
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 or implies a place; the tool parses place and varietal from the query. Returns an honest empty list when nothing matches — never fabricate. Pair with fetch to retrieve full producer detail.

Endpoints

URLTransportStateLatencyChecked
https://mcp.melvea.com streamable-http answering 131 ms 14 min ago

Melvea Local Honey Discovery — questions

Answers built from our own checks of this server.

What can Melvea Local Honey Discovery do?
It exposes 4 tools, read directly from the server on our last check. Among them: fetch, find_local_producers, get_producer, search. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Melvea Local Honey Discovery working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 108 ms. The bar chart above shows every period we have measured.
How do I connect Melvea Local Honey Discovery?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Melvea Local Honey Discovery need an API key?
No. Melvea Local Honey Discovery completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Melvea Local Honey Discovery?
It answers our handshake in 108 ms on average, which is faster than 82% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.