_ registry / mcp streamable-http · checked 55m ago

aiden-mcp

https://aidenmcp.ravenhoward.org

Registry code: f18ad16d6cbb4cb3

api record

Controls Fellow Aiden smart coffee brewer profiles through natural language, with tools to create, delete, and share brewing recipes.

from a public catalogue that lists it, not from the operator

endpoint
https://aidenmcp.ravenhoward.org/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 aiden-mcp live?
Yes — it answered the hub's last check (checked 55m ago). It answered 99% of checks over the last 30 days.
Is aiden-mcp 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 aiden-mcp have?
13 tools: fetch_coffee_details, brewing_guidelines, delete_schedule, create_profile, update_profile, delete_profile, share_profile, flash_brew, ….
Is aiden-mcp 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
99.3%

90 days 99.5%· all time 99.5%

latency
415ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 408 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
iot & hardware devices & sensors
used for
  • create a brew profile on a coffee brewer
  • schedule a coffee brew
  • get brewing guidelines for a coffee
  • share a brew profile link
takes → gives
text, data → data
tools
6 reads7 changes data
_ 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 13 tools
12 auth-required 1 never probed 12 of 13 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.

  • brewing_guidelines reads auth-required never probed

    Get Aiden-specific brewing guidelines tailored to a coffee's characteristics. Returns brewing principles + a starting-point recipe. Use this AFTER fetching coffee details (or when user provides them directly), then design the actual create_profile call using the returned principles. IMPORTANT: if the user already has a profile made for this exact coffee (Fellow Drops or a roaster-shared profile), do NOT redesign it from these principles — it was dialed by people who tasted this coffee. Adjust it one variable at a time (1–2°C max) toward what the user disliked. Does NOT require Aiden auth.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "roast": {
      "type": "string",
      "description": "Roast level from the bag: light, medium-light, medium, medium-dark, dark. The strongest temperature driver in expert profiles — ASK the user if not stated."
    },
    "grinder": {
      "type": "string",
      "description": "User's grinder, so the grind setting comes back on their dial instead of the Baratza Encore reference scale. Supported: Baratza Encore ESP, Baratza Encore, Baratza Virtuoso+, Fellow Ode + SSP MP burrs, Fellow Ode Gen 2, Fellow Ode Gen 1, Fellow Opus, Comandante C40, 1Zpresso J/JX, Timemore C2/C3, DF64, Niche Zero. ASK the user what grinder they have if they haven't said."
    },
    "process": {
      "type": "string",
      "description": "Process: washed, natural, honey, anaerobic, etc."
    },
    "elevation": {
      "type": "string",
      "description": "Elevation, e.g. '1,800–2,000 masl' or '1750m'"
    },
    "varieties": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Varietal names, e.g. ['Bourbon', 'SL28']"
    },
    "brew_basket": {
      "type": "string",
      "description": "Only for modded brew chambers: 'v60', 'orea', or 'kalita' if the user has swapped the stock flat-bottom basket for a dripper via an adapter. Omit for a stock Aiden. Adjusts grind and pulse pacing for the different drawdown geometry."
    },
    "flavor_goal": {
      "type": "string",
      "description": "What the user is trying to achieve, e.g. 'more fruit', 'less acidity', 'bolder body'. Drives explicit recipe adjustments."
    },
    "tasting_notes": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Notes on the bag, e.g. ['fig', 'strawberry', 'honey']"
    },
    "user_preference_ratio": {
      "type": "number",
      "description": "User's typical ratio (e.g. 15 for 1:15). Defaults to 1:15 washed, 1:16 natural."
    }
  },
  "additionalProperties": false
}
    arguments 49 lines
  • delete_schedule changes data auth-required never probed

    Delete a scheduled brew by its id. Use list_schedules first to find the id.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scheduleId"
  ],
  "properties": {
    "scheduleId": {
      "type": "string",
      "minLength": 1,
      "description": "Schedule id from list_schedules"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • create_profile changes data auth-required never probed

    Create a new brew profile on your Aiden and return a brew.link URL. The profile will appear in the Fellow iOS app immediately. If the device is at its 14-profile cap, you'll get an error — call delete_profile first to free a slot.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "title",
    "ratio",
    "bloomRatio",
    "bloomDuration",
    "bloomTemperature",
    "ssPulsesNumber",
    "ssPulsesInterval",
    "ssPulseTemperatures",
    "batchPulsesNumber",
    "batchPulsesInterval",
    "batchPulseTemperatures"
  ],
  "properties": {
    "ratio": {
      "type": "number",
      "maximum": 20,
      "minimum": 8
    },
    "title": {
      "type": "string",
      "pattern": "^[A-Za-z0-9 _\\-.,'’()&!]+$",
      "maxLength": 50,
      "minLength": 1
    },
    "bloomRatio": {
      "type": "number",
      "maximum": 3,
      "minimum": 1
    },
    "profileType": {
      "type": "integer",
      "default": 0
    },
    "bloomEnabled": {
      "type": "boolean",
      "default": true
    },
    "bloomDuration": {
      "type": "integer",
      "maximum": 120,
      "minimum": 1
    },
    "ssPulsesNumber": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1
    },
    "ssPulsesEnabled": {
      "$ref": "#/properties/bloomEnabled",
      "default": true
    },
    "bloomTemperature": {
      "type": "number",
      "maximum": 99,
      "minimum": 50
    },
    "ssPulsesInterval": {
      "type": "integer",
      "maximum": 60,
      "minimum": 5
    },
    "batchPulsesNumber": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1
    },
    "batchPulsesEnabled": {
      "$ref": "#/properties/bloomEnabled",
      "default": true
    },
    "batchPulsesInterval": {
      "type": "integer",
      "maximum": 60,
      "minimum": 5
    },
    "ssPulseTemperatures": {
      "type": "array",
      "items": {
        "$ref": "#/properties/bloomTemperature"
      }
    },
    "batchPulseTemperatures": {
      "$ref": "#/properties/ssPulseTemperatures"
    }
  },
  "additionalProperties": false
}
    arguments 91 lines
  • update_profile changes data auth-required never probed

    Update an existing brew profile on your Aiden in place. Pass the profile id (or exact title) plus ANY subset of the profile fields you want to change — unspecified fields keep their current values. Useful for dialing in an existing recipe (e.g. nudge ratio, drop a temperature) without delete-and-recreate. The brew.link URL stays the same since the profile id doesn't change.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "idOrTitle"
  ],
  "properties": {
    "ratio": {
      "type": "number",
      "maximum": 20,
      "minimum": 8
    },
    "title": {
      "type": "string",
      "maxLength": 50,
      "minLength": 1,
      "description": "New title (optional)"
    },
    "idOrTitle": {
      "type": "string",
      "minLength": 1,
      "description": "Profile id (e.g. 'p1') or exact case-sensitive title (e.g. 'Mpemba v3')"
    },
    "bloomRatio": {
      "type": "number",
      "maximum": 3,
      "minimum": 1
    },
    "bloomEnabled": {
      "type": "boolean"
    },
    "bloomDuration": {
      "type": "integer",
      "maximum": 120,
      "minimum": 1
    },
    "ssPulsesNumber": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1
    },
    "ssPulsesEnabled": {
      "$ref": "#/properties/bloomEnabled"
    },
    "bloomTemperature": {
      "type": "number",
      "maximum": 99,
      "minimum": 50
    },
    "ssPulsesInterval": {
      "type": "integer",
      "maximum": 60,
      "minimum": 5
    },
    "batchPulsesNumber": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1
    },
    "batchPulsesEnabled": {
      "$ref": "#/properties/bloomEnabled"
    },
    "batchPulsesInterval": {
      "type": "integer",
      "maximum": 60,
      "minimum": 5
    },
    "ssPulseTemperatures": {
      "type": "array",
      "items": {
        "type": "number",
        "maximum": 99,
        "minimum": 50
      }
    },
    "batchPulseTemperatures": {
      "type": "array",
      "items": {
        "type": "number",
        "maximum": 99,
        "minimum": 50
      }
    }
  },
  "additionalProperties": false
}
    arguments 86 lines
  • delete_profile changes data auth-required never probed

    Delete a brew profile from your Aiden. Pass either the profile id (e.g. 'p10') or the exact title (e.g. 'Mpemba v2'). Use list_profiles first if you don't know the id.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "idOrTitle"
  ],
  "properties": {
    "idOrTitle": {
      "type": "string",
      "minLength": 1,
      "description": "Either the profile id (e.g. 'p10') or the exact case-sensitive title"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • share_profile changes data auth-required never probed

    Generate a brew.link URL for an existing profile on your Aiden. Use this to re-share a profile you already have. (create_profile already returns a brew.link, so you only need this for profiles created via the Fellow app or another tool.)

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "idOrTitle"
  ],
  "properties": {
    "idOrTitle": {
      "type": "string",
      "minLength": 1,
      "description": "Profile id (e.g. 'p10') or exact case-sensitive title"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • flash_brew reads auth-required never probed

    Plan a flash brew (Japanese iced coffee) on the Aiden: a hot, concentrated brew directly onto ice in the carafe. The default plan is honest: it sets the profile ratio to the true 1:9-1:12 hot-concentrate ratio (Fellow's API accepts ratios below the app's 1:14 minimum), so the machine's displayed dose and bloom sizing are simply correct. Returns the ice/water split, profile ratio to set, dose, grind adjustment, and technique steps. Pass machine_profile_ratio ONLY to brew with an existing 1:14+ profile unchanged — that returns the classic dose-misreport workaround instead. Pure math, no Aiden auth. Use brewing_guidelines first for the coffee's profile temps.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "dose_g": {
      "type": "number",
      "maximum": 120,
      "minimum": 10,
      "description": "Coffee the user wants to use, in grams. Provide this OR target_volume_ml."
    },
    "grinder": {
      "type": "string",
      "description": "User's grinder, to convert the flash-brew grind setting to their dial."
    },
    "total_ratio": {
      "type": "number",
      "maximum": 20,
      "minimum": 10,
      "description": "True ratio including ice melt. Default 15 (Counter Culture uses 17, Lance Hedrick 12 — lower = stronger)."
    },
    "ice_fraction": {
      "type": "number",
      "maximum": 0.5,
      "minimum": 0.1,
      "description": "Share of total liquid that is ice in the carafe. Default 0.3; published recipes use 0.25-0.33."
    },
    "target_volume_ml": {
      "type": "number",
      "maximum": 2000,
      "minimum": 150,
      "description": "Final drink size in ml (ice melt included). Used to derive the dose if dose_g not given."
    },
    "machine_profile_ratio": {
      "type": "number",
      "maximum": 20,
      "minimum": 8,
      "description": "Only set this to brew with an existing profile whose ratio stays as-is — the plan becomes the dose-misreport workaround for that ratio. Omit it (default) for the honest plan, where the profile ratio is set to the true hot-concentrate ratio."
    }
  },
  "additionalProperties": false
}
    arguments 41 lines
  • create_schedule changes data auth-required never probed

    Create a scheduled brew on your Aiden. The Aiden hardware fires the brew at the specified time on the specified days. Time is in DEVICE LOCAL TIME (the timezone configured on the brewer). The schedule is RECURRING — for a one-time 'today at 2pm' brew, set days[] with only today's day enabled, and either delete the schedule after it fires or use toggle_schedule to disable it. Days array indexes: [Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday]. Find the profileId by calling list_profiles first.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "profileId",
    "time",
    "days",
    "amountOfWater"
  ],
  "properties": {
    "days": {
      "type": "array",
      "items": {
        "type": "boolean"
      },
      "maxItems": 7,
      "minItems": 7,
      "description": "7 booleans for [Sun, Mon, Tue, Wed, Thu, Fri, Sat]. e.g. [false,true,true,true,true,true,false] = weekdays only."
    },
    "time": {
      "type": "string",
      "pattern": "^([01]?\\d|2[0-3]):[0-5]\\d$",
      "description": "Local time of day in 24-hour HH:MM format, e.g. '07:00' for 7am, '14:00' for 2pm"
    },
    "enabled": {
      "$ref": "#/properties/days/items",
      "default": true,
      "description": "Whether the schedule starts active. Default: true."
    },
    "profileId": {
      "type": "string",
      "pattern": "^(p|plocal)\\d+$",
      "description": "Profile id from list_profiles, e.g. 'p1' for Mpemba v3 or 'plocal0' for Light Roast"
    },
    "amountOfWater": {
      "type": "integer",
      "maximum": 1500,
      "minimum": 150,
      "description": "Brew volume in milliliters, 150–1500. A standard cup is ~240mL, full carafe is ~1000mL."
    }
  },
  "additionalProperties": false
}
    arguments 43 lines
  • toggle_schedule changes data auth-required never probed

    Enable or disable an existing scheduled brew without deleting it. Useful for pausing a recurring schedule (e.g. weekday morning brew) during vacation.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scheduleId",
    "enabled"
  ],
  "properties": {
    "enabled": {
      "type": "boolean",
      "description": "true to activate the schedule, false to pause it"
    },
    "scheduleId": {
      "type": "string",
      "minLength": 1,
      "description": "Schedule id from list_schedules"
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • get_device_info reads auth-required 14h ago

    Get info about your connected Aiden brewer (name, profile count, slot usage). Lightweight call useful for verifying credentials work before doing heavier operations.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • list_profiles reads auth-required 14h ago

    List all brew profiles currently on your Fellow Aiden, grouped by category (custom, stock, shared). The 14-profile cap applies only to user-created custom profiles.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • list_schedules reads auth-required 14h ago

    List all scheduled brews on your Aiden. Each schedule has a recurrence pattern (which days of the week), a time of day, a profile to brew, and a water amount. Schedules can be enabled/disabled individually.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "include_raw": {
      "type": "boolean",
      "default": false,
      "description": "Include the raw schedule JSON from Fellow. Off by default because it is very large (it embeds a full copy of each schedule's profile). Turn on only when diagnosing non-standard fields."
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • fetch_coffee_details reads unknown 11h ago

    Fetch a coffee from a roaster's product page (Counter Culture, Onyx, Sey, Heart, etc. — any Shopify-based roaster) and return structured details: name, varieties, process, elevation, country, tasting notes, story. Use this when the user pastes a URL and wants you to design a brew profile from it. Does NOT require Aiden auth — works on URLs alone.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri",
      "description": "Roaster product page URL, e.g. https://counterculturecoffee.com/products/mpemba"
    }
  },
  "additionalProperties": false
}
    arguments 15 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 f18ad16d6cbb4cb3.

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

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.