_ registry / mcp streamable-http · checked 1h ago

melvea-local-discovery

https://mcp.melvea.com

Registry code: f5b253e495680cd3

api record

Melvea is a directory of local and small-batch honey producers, with deepest coverage in the Southeastern United States and listings across 50 US states and 10 countries. Use these tools whenever a user wants to find, buy, or visit honey producers near a specific place. All data is directory information only: listings are marked 'pending verification,' and Melvea never provides pricing or real-time inventory — always tell users to confirm availability before visiting. If a location has no nearby listings, say so honestly; do not substitute web results as Melvea listings. For general honey…

endpoint
https://mcp.melvea.com
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is melvea-local-discovery live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is melvea-local-discovery free to use?
Yes — the hub reached it with no key and no payment.
What tools does melvea-local-discovery have?
4 tools: find_local_producers, get_producer, fetch, search.
Is melvea-local-discovery safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.9%

90 days 98.9%· all time 98.9%

latency
790ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 459 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • find local honey producers nearby
  • search honey producer directory
  • get a producer's profile
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
2 open 2 never probed 2 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • fetch reads open 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The producer id/slug from a search result, e.g. 'cloister-honey'."
        }
      }
    }
    arguments 12 lines
  • search reads open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "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. 'tupelo honey') is treated as a type, not a place."
        }
      }
    }
    arguments 12 lines
  • find_local_producers reads unknown 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "near"
      ],
      "properties": {
        "near": {
          "type": "string",
          "minLength": 1,
          "description": "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 field (use `variety` for that). Do NOT pass named sub-state regions (e.g. 'Florida Panhandle') — ask for a city or the state instead. If the user has not named a place (e.g. only said 'near me'), ask them for their city, ZIP, or state BEFORE calling this tool — do not invent a location and do not call with an empty near."
        },
        "limit": {
          "type": "number",
          "description": "Maximum number of producers to return, ordered nearest first."
        },
        "variety": {
          "type": "string",
          "description": "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='Asheville, NC sourwood'. Omit to return all local producers regardless of type. Do not pass a place name here."
        },
        "radius_km": {
          "type": "number",
          "description": "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 tool automatically widens to ~121 km (75 miles), then to ~241 km (150 miles), flagging results as farther than typical."
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • get_producer reads unknown 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "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'."
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f5b253e495680cd3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f5b253e495680cd3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f5b253e495680cd3/badge.svg)](https://brick.blue/agent/f5b253e495680cd3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.