Melvea Local Honey Discovery MCP server
com.melvea/local-discoverymelvea.comstreamable-httpv0.1.1Scanned
Citation-backed honey producer discovery by place or varietal. Free, no auth.
4 tools: 4 only read.
- Reads private data · 3
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Melvea Local Honey Discovery MCP server can do
The Melvea Local Honey Discovery MCP server is published by melvea.com, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools read private data (get_producer, search and fetch); 2 tools bring in text other people can write (search and fetch).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 0.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
fetchRetrieve the full Melvea record for one producer by id, returning name, location, declared honey types, contact info, verification status, and profile URL.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
What it can reach
- private-dataThe description's first sentence says "retrieve" and "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "retrieve" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
find_local_producersFind local honey producers near a specific place, optionally filtered by honey varietal.No findings
Why it is in this group
- The name "find_local_producers" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
get_producerGet the full directory profile for one specific producer by its slug, including location, declared honey types, contact channels, and verification status.Reads private dataNo findings
Why it is in this group
- The name "get_producer" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "directory": it reads files.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
searchSearch the Melvea local honey directory by free-text query and return matching producers as a list of results (id, title, url).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "search" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "directory": it reads files.
- untrusted-inputThe description's first sentence says "search" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:42 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.melvea.com/.well-known/oauth-protected-resource
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http local-discovery https://mcp.melvea.comclaude mcp add --transport http local-discovery https://mcp.melvea.comRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__local-discovery__find_local_producers",
"mcp__local-discovery__get_producer",
"mcp__local-discovery__search",
"mcp__local-discovery__fetch"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as local-discovery. Review it before you use it.
Capability tags behind 3 rules
- mcp__local-discovery__get_producer private-data
- mcp__local-discovery__search private-data, untrusted-input
- mcp__local-discovery__fetch private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.melvea/local-discovery/verify?hash=31bf2753290f43946de3223aa29e2443599323dd022cd41c525306136b37917d" | jq -e '.changed == false'Pinned hash 31bf2753290f, from Nov 13, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.melvea/local-discovery/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.melvea/local-discovery)Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.
Melvea Local Honey Discovery MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Melvea Local Honey Discovery MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Melvea Local Honey Discovery MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Melvea Local Honey Discovery MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Melvea Local Honey Discovery MCP server have?
- 4 tools: 4 read. find_local_producers, get_producer, search and fetch.
Does the Melvea Local Honey Discovery MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Melvea Local Honey Discovery MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Melvea Local Honey Discovery MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.