# Melvea Local Honey Discovery (remote · mcp.melvea.com)

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

- Trust score: 56/100 (low)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.melvea.com`: 56/100 (this document), [markdown](https://verifymcp.io/servers/com-melvea-local-discovery/mcp.md), [page](https://verifymcp.io/servers/com-melvea-local-discovery/mcp)

## Channel facts

- Endpoint: `https://mcp.melvea.com`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1189 tokens (~297/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-melvea-local-discovery https://mcp.melvea.com/
```

### Codex

```toml
[mcp_servers.com-melvea-local-discovery]
url = "https://mcp.melvea.com/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-melvea-local-discovery": {
      "type": "remote",
      "url": "https://mcp.melvea.com/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-melvea-local-discovery --url https://mcp.melvea.com/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-melvea-local-discovery:
    url: "https://mcp.melvea.com/"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 55, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 56, +14)

- [functional improvement] Schema quality: unverified → excellent

### 2026-07-28 (score 42, −12)

- [functional regression] Schema quality: 236 → 297
- [functional regression] Schema quality: excellent → unverified

### 2026-07-27 (score 54, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 54)

First indexed and scored.

## MCP tools (4)

### `find_local_producers` (~626 tokens)

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.

Input parameters:

- `limit` (number): Maximum number of producers to return, ordered nearest first.
- `near` (string, required): REQUIRED. The place to search around — a city, town, ZIP, or US state name/code. Examples: 'Charlotte, NC', '28202', 'Asheville', 'Oregon', 'OR', 'North Carolina'. Do NOT put a honey varietal in this…
- `radius_km` (number): Search radius in kilometers for city/ZIP queries only (ignored for US state queries). Defaults to a standard local radius. Within the Southeastern US, the tool automatically widens to ~120 km (75 mil…
- `variety` (string): Optional honey varietal filter, e.g. 'sourwood', 'tupelo', 'clover', 'wildflower', 'orange blossom'. Pass this SEPARATELY from `near` — e.g. near='Asheville, NC' and variety='sourwood', never near='A…

### `get_producer` (~119 tokens)

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.

Input parameters:

- `slug` (string, required): The exact producer slug, as returned in the slug/id field of a find_local_producers or search result, e.g. 'cloister-honey', 'asheville-bee-charmer'.

### `search` (~161 tokens)

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.

Input parameters:

- `query` (string, required): A free-text local-honey query, e.g. 'sourwood honey near Asheville NC' or 'local honey producers in Charlotte'. The tool extracts the place and any varietal automatically; a varietal alone (e.g. 'tup…

### `fetch` (~105 tokens)

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.

Input parameters:

- `id` (string, required): The producer id/slug from a search result, e.g. 'cloister-honey'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-melvea-local-discovery/mcp#diagnostics

## Score history

- 2026-08-03: 56
- 2026-08-02: 55
- 2026-08-01: 55
- 2026-07-31: 55
- 2026-07-30: 56
- 2026-07-29: 56
- 2026-07-28: 42
- 2026-07-27: 54
- 2026-07-26: 54

## Links

- Remote endpoint: https://mcp.melvea.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-melvea-local-discovery/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-melvea-local-discovery/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-melvea-local-discovery/mcp