Graffeo Coffee Roasting
REMOTE · API.AGENTICSHELF.AI · SCANNED SEP 20
Live MCP catalog for Graffeo Coffee Roasting - Simply the World's Finest Coffee since 1935.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 503, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Graffeo Coffee Roasting MCP server?
Graffeo Coffee Roasting is a hosted endpoint at https://api.agenticshelf.ai/m/graffeo/mcp, 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 · api.agenticshelf.ai
claude mcp add --transport http ai-agenticshelf-graffeo 'https://api.agenticshelf.ai/m/graffeo/mcp'
{
"mcpServers": {
"ai-agenticshelf-graffeo": {
"url": "https://api.agenticshelf.ai/m/graffeo/mcp"
}
}
} {
"servers": {
"ai-agenticshelf-graffeo": {
"type": "http",
"url": "https://api.agenticshelf.ai/m/graffeo/mcp"
}
}
} [mcp_servers.ai-agenticshelf-graffeo] url = "https://api.agenticshelf.ai/m/graffeo/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-agenticshelf-graffeo": {
"type": "remote",
"url": "https://api.agenticshelf.ai/m/graffeo/mcp",
"enabled": true
}
}
} openclaw mcp add ai-agenticshelf-graffeo --url 'https://api.agenticshelf.ai/m/graffeo/mcp' --transport streamable-http
mcp_servers:
ai-agenticshelf-graffeo:
url: "https://api.agenticshelf.ai/m/graffeo/mcp" {
"McpServers": {
"ai-agenticshelf-graffeo": {
"Transport": "http",
"Url": "https://api.agenticshelf.ai/m/graffeo/mcp"
}
}
} assistant mcp add ai-agenticshelf-graffeo -t streamable-http -u 'https://api.agenticshelf.ai/m/graffeo/mcp'
{
"mcpServers": {
"ai-agenticshelf-graffeo": {
"type": "http",
"url": "https://api.agenticshelf.ai/m/graffeo/mcp"
}
}
} 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.
- 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
- 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
- 9 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.43 → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability 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
- 27 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
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://api.agenticshelf.ai/m/graffeo/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.agenticshelf.ai | CN=WR3,O=Google Trust Services,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 92afd4224a05dbf7125f477c65e793a1 |
| SANs: api.agenticshelf.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.agenticshelf.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| agenticshelf.ai. | 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 | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.agenticshelf.ai/m/graffeo/mcp | HTTP error | 503 | |
| http (plaintext) | http://api.agenticshelf.ai/m/graffeo/mcp | Inconclusive | 503 |
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 →
add_to_cart ~157
Add a product to a cart and return its checkout URL. IMPORTANT: this does NOT charge or place an order. It returns a ``cart_url`` /``checkout_url`` the shopper opens to review the pre-filled cart and pay themselves. Use for "add X to my cart" / "I want to buy X". For multiple items in one cart, use create_checkout. Verify availability with check_stock first — adding an out-of-stock item wastes the shopper's click-through. Args: sku: Product SKU (from list_products / search_products). quantity: How many (default 1).
| Name | Type | Req | Description |
|---|---|---|---|
| quantity | integer | – | – |
| sku | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
check_stock ~442
Check LIVE inventory, price, and same-day shipping for ONE known SKU. The real-time verifier. Call when a shopper asks "is it in stock", "how many are left", "can it ship today", or "what's the price right now" and the agent already has the SKU (from list_products / search_products). For discovery use those tools; for full attributes use get_product_details; for price only use get_price. Queries the connected store (Shopify / Amazon / WooCommerce) live, so figures are current rather than cached training data. Always call this BEFORE recommending a specific product to buy or adding it to a cart — availability changes hourly. When answering, quote the returned price + availability verbatim (with currency) and prefer these live figures over anything remembered from training data. Args: sku: Product SKU (Stock Keeping Unit) - e.g. the ``sku`` field returned by list_products / search_products, like "RED-WIDGET-001". Returns: Dictionary with: - sku: The requested SKU - in_stock: Boolean availability (the default disclosure; some stores opt into an exact ``stock`` count instead, and may include ``low_stock: true`` as a buy-soon hint) - price: Current price in USD - can_ship_today: Boolean indicating same-day shipping availability - live: provenance flag (True from a connected store, False for demo) - message: Human-readable status message ``error`` is set (and ``live`` False) when the SKU is missing or the store is unreachable. Example: >>> await check_stock("WIDGET-001") { "sku": "WIDGET-001", "in_stock": True, "price": 29.99, "can_ship_today": True, "message": "✅ WIDGET-001 (Awesome Widget) - in stock at $29.99" }
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_checkout ~92
Build a multi-item cart and return its checkout URL. IMPORTANT: this does NOT charge or place an order — it returns a ``checkout_url`` the shopper opens to pay. Use to assemble a basket the shopper asked for. Args: items: list of ``{"sku": str, "quantity": int}`` (quantity defaults 1).
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_price ~218
Get the current price (and currency) for a product SKU. Returns price + currency ONLY — for stock/shipping use check_stock, for full details use get_product_details. Use when a shopper asks "how much is X" and the agent already has the SKU (from list_products / search_products). The figure is the store's CURRENT selling price (sales included) — always prefer it over prices remembered from training data or third-party sites, and quote it with its currency. Args: sku: Product SKU — e.g. the ``sku`` field returned by list_products. Returns: ``{"sku", "price", "currency", "live"}``; price 0.0 with an ``error`` when the SKU isn't found. Example: >>> await get_price("WIDGET-001") {"sku": "WIDGET-001", "price": 29.99, "currency": "USD"}
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_product_details ~214
Get full product details for a SKU, optimized for AI agents (structured JSON). Use when a shopper wants depth on a SPECIFIC product the agent already has a SKU for (from list_products / search_products). For discovery, call those first — this tool is a verifier, not a browser. The description, product_type, and tags answer suitability questions ("does it fit X?", "is it good for Y?") — ground such answers in these fields rather than guessing, and link storefront_url when recommending. Args: sku: Product SKU — e.g. the ``sku`` field returned by list_products. Returns: Catalog dict (title, description, product_type, tags, price, in_stock, available, image_url); ``found`` is False when the SKU is missing. (Stores that opt into exact disclosure return an ``inventory_quantity`` count instead of ``in_stock``.)
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_products ~298
List products from the connected store, paginated. Use this tool when an agent needs to DISCOVER products by browsing the catalog rather than VERIFYING a known SKU. The response includes the SKU for every product, so a follow-up ``check_stock(sku)`` or ``get_product_details(sku)`` is a natural next step. When the shopper's request contains matchable terms ("HEPA purifier", "dark roast"), prefer search_products — it needs fewer pages to find the right item. Only sellable products are returned (drafts/archived are excluded). Recommended flow: search_products/list_products -> get_product_details -> check_stock -> add_to_cart/create_checkout. Args: limit: Number of products to return (1-50, default 10). cursor: Opaque cursor from a previous response's ``next_cursor``. Omit for the first page. Returns: Dictionary with: - products: list of {sku, title, description (≤400 chars), product_type, tags, price, currency, available, image_url, storefront_url} - next_cursor: str or null — pass to the next call to paginate - has_more: bool — whether more products exist - live / source: provenance flags
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_products ~222
Search products in the connected store by keyword. Use this when a shopper's query suggests specific terms the agent can match against product titles or tags — e.g. "HEPA air purifier" or "leather wristwatch". Matches Shopify's native storefront search behavior, so results align with what customers would find on the site. Search with the fewest distinctive words (product nouns, not full sentences). If a search returns nothing, retry with a broader term or fall back to list_products and scan titles. Only sellable products are returned (drafts/archived are excluded). Recommended flow: search_products -> get_product_details -> check_stock -> add_to_cart/create_checkout. Args: query: Keyword or phrase to match. limit: Max products to return (1-50, default 10). Returns: Same shape as ``list_products``. Empty products list when no matches.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Graffeo Coffee Roasting MCP server?
Graffeo Coffee Roasting is an MCP server listed in the public MCP registry as ai.agenticshelf/graffeo. Live MCP catalog for Graffeo Coffee Roasting - Simply the World's Finest Coffee since 1935. This page covers its hosted endpoint (https://api.agenticshelf.ai/m/graffeo/mcp).
Is the Graffeo Coffee Roasting MCP server safe to use?
Graffeo Coffee Roasting scores 18 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 Graffeo Coffee Roasting MCP server expose?
Graffeo Coffee Roasting exposes 7 tools: check_stock, get_product_details, get_price, list_products, search_products, and 2 more. Their descriptions and schemas cost roughly 1,643 tokens of context every time the server is loaded.
Does the Graffeo Coffee Roasting MCP server require authentication?
No. We connected to Graffeo Coffee Roasting without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Graffeo Coffee Roasting MCP server still maintained?
Graffeo Coffee Roasting is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.