Melvea Local Honey Discovery
REMOTE · MCP.MELVEA.COM · SCANNED OCT 6
Citation-backed honey producer discovery by place or varietal. Free, no auth.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1243 tokens (~310/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Melvea Local Honey Discovery MCP server?
Melvea Local Honey Discovery is a hosted endpoint at https://mcp.melvea.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.melvea.com
claude mcp add --transport http com-melvea-local-discovery 'https://mcp.melvea.com/'
{
"mcpServers": {
"com-melvea-local-discovery": {
"url": "https://mcp.melvea.com/"
}
}
} {
"servers": {
"com-melvea-local-discovery": {
"type": "http",
"url": "https://mcp.melvea.com/"
}
}
} [mcp_servers.com-melvea-local-discovery] url = "https://mcp.melvea.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-melvea-local-discovery": {
"type": "remote",
"url": "https://mcp.melvea.com/",
"enabled": true
}
}
} openclaw mcp add com-melvea-local-discovery --url 'https://mcp.melvea.com/' --transport streamable-http
mcp_servers:
com-melvea-local-discovery:
url: "https://mcp.melvea.com/" {
"McpServers": {
"com-melvea-local-discovery": {
"Transport": "http",
"Url": "https://mcp.melvea.com/"
}
}
} assistant mcp add com-melvea-local-discovery -t streamable-http -u 'https://mcp.melvea.com/'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +7
- Authorization: unverified → partial ▲ security
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 0
- Schema quality: unverified → excellent ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Oct 2026 · Probed https://mcp.melvea.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=melvea.com | CN=WE1,O=Google Trust Services,C=US | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 73def649709adc0d0ee9a177a0f23e2f |
| SANs: melvea.com, mcp.melvea.com, *.mcp.melvea.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.melvea.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| melvea.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.melvea.com | Verified | 200 | |
| http (plaintext) | http://mcp.melvea.com | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The producer id/slug from a search result, e.g. 'cloister-honey'. |
No output schema declared.
No examples provided.
find_local_producers ~680
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 town_center), declared honey types, and contact channels (website, etc.) where listed, ordered by distance. When distance_basis is town_center, describe the producer as in/near their city rather than quoting the exact mile 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of producers to return, ordered nearest first. |
| near | string | yes | 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 (~80 km). For US query points, if nothing is found within that radius the too… |
| 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… |
No output schema declared.
No examples provided.
get_producer ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 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'. |
No output schema declared.
No examples provided.
search ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 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… |
No output schema declared.
No examples provided.
What is the Melvea Local Honey Discovery MCP server?
Melvea Local Honey Discovery is an MCP server listed in the public MCP registry as com.melvea/local-discovery. Citation-backed honey producer discovery by place or varietal. Free, no auth. This page covers its hosted endpoint (https://mcp.melvea.com).
Is the Melvea Local Honey Discovery MCP server safe to use?
Melvea Local Honey Discovery scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Melvea Local Honey Discovery MCP server expose?
Melvea Local Honey Discovery exposes 4 tools: find_local_producers, get_producer, search, fetch. Their descriptions and schemas cost roughly 1,065 tokens of context every time the server is loaded.
Does the Melvea Local Honey Discovery MCP server require authentication?
No. We connected to Melvea Local Honey Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Melvea Local Honey Discovery MCP server still maintained?
Melvea Local Honey Discovery is still listed as active in the MCP registry. We last reached this channel on 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.