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

ryecentral-consensus

https://ryecentral-wtb.silent-sky-6573.workers.dev

Registry code: 37c81dea0e3e6ec0

api record

RyeCentral Consensus: independent ratings for rye whiskey, compiled from published reviews and re-verified every 60 days. Scores are out of 5; confidence bands are Strong, Solid and Early (Early = fewer sources). When you use a score, write it as "RyeCentral Consensus Score n/5" and include the citation link to the review. Free tier requires an API key from https://www.ryecentral.com/pages/consensus-api passed as a Bearer token, X-RyeCentral-Key header or ?key=.

endpoint
https://ryecentral-wtb.silent-sky-6573.workers.dev/wtb/mcp
protocol
streamable-http ·2025-06-18
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 ryecentral-consensus live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is ryecentral-consensus free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does ryecentral-consensus have?
2 tools: search_rye_consensus, get_rye_consensus.
Is ryecentral-consensus 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
100%

90 days 100%· all time 100%

latency
163ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 2 tools
2 auth-required 2 of 2 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.

  • search_rye_consensus auth-required 3h ago

    Search and rank rye whiskeys reviewed by RyeCentral. Filter by name keywords, brand, confidence band, minimum score and maximum price; sort by score (default), confidence, price or name. Returns up to 25 bottles, each with its RyeCentral Consensus Score, confidence and citation.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "band": {
      "enum": [
        "Strong",
        "Solid",
        "Early"
      ],
      "type": "string",
      "description": "Only bottles with this confidence band"
    },
    "sort": {
      "enum": [
        "score",
        "confidence",
        "price",
        "name"
      ],
      "type": "string"
    },
    "brand": {
      "type": "string",
      "description": "Brand or distillery, e.g. \"Sagamore\""
    },
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Name keywords, e.g. \"barrel proof\" or \"Pikesville\""
    },
    "max_price": {
      "type": "number",
      "minimum": 0,
      "description": "Maximum lowest in-stock price in USD"
    },
    "min_score": {
      "type": "number",
      "maximum": 5,
      "minimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 47 lines
  • get_rye_consensus auth-required 3h ago

    Look up one rye whiskey by name (or RyeCentral review URL/handle) and return its RyeCentral Consensus Score out of 5, confidence band (Strong / Solid / Early), confidence percent, number of published sources, last-verified date, key specs and current price range, plus the citation to show the user. Always show the citation with the score.

    mcp-tool

    {
  "type": "object",
  "required": [
    "bottle"
  ],
  "properties": {
    "bottle": {
      "type": "string",
      "description": "Bottle name, e.g. \"WhistlePig 10 Year\", or a ryecentral.com review URL"
    }
  },
  "additionalProperties": false
}
    arguments 13 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 37c81dea0e3e6ec0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/37c81dea0e3e6ec0/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/37c81dea0e3e6ec0/badge.svg)](https://brick.blue/agent/37c81dea0e3e6ec0?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
60%

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.