expiry-tracker-storage-guide
Registry code: c1cf872fdaa3385d
Storage guide of the Expiry Tracker (SKT Takip) app: how long 100 common foods keep in the fridge, freezer and pantry, opened and unopened, with spoilage signs, freezing advice and official sources (USDA FSIS, FoodKeeper, national food agencies). Use search_foods to find a food from a word or a product name, then get_storage_guide with its slug. Answer in the user's language and pass the language code when it is one of tr, en, de, es, fr, it, ru, ja, ar. Cite the page URL from the result. A use-by date on the package beats any chart, and the guide is not medical advice.
- endpoint
- https://getexpirytracker.com/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 expiry-tracker-storage-guide live?
- Yes — it answered the hub's last check (checked 15h ago). It answered 100% of checks over the last 30 days.
- Is expiry-tracker-storage-guide free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does expiry-tracker-storage-guide have?
- 2 tools: search_foods, get_storage_guide.
- Is expiry-tracker-storage-guide 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.
90 days 100%· all time 100%
last good check
of 2 tools
- unknown → live
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.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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_foods unknown 15h ago
Finds foods in the storage guide for a food word or a product name in Turkish, English, German, Spanish, French, Italian, Russian, Japanese or Arabic (for example 'yoğurt', 'opened milk', 'Kaşar peyniri', 'Hähnchenbrust'). Returns up to 8 foods with their slug, a one-line summary and the page URL. Use the slug with get_storage_guide.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "maxLength": 100, "minLength": 1, "description": "A food or product name, a few words at most." }, "language": { "enum": [ "tr", "en", "de", "es", "fr", "it", "ru", "ja", "ar" ], "type": "string", "description": "Language of the answer: tr, en, de, es, fr, it, ru, ja or ar. Defaults to the language the food was found in." } }, "additionalProperties": false }arguments 30 linesget_storage_guide unknown 15h ago
Returns how long one food keeps in the fridge, freezer and pantry, for each state the guide lists (unopened, opened, cooked, ...), with the best way to store it, spoilage signs, freezing and thawing, myths, advice for people at higher risk, common questions, sources and the page URL. Pass a slug from search_foods, or a food name.
{ "type": "object", "required": [ "food" ], "properties": { "food": { "type": "string", "maxLength": 100, "minLength": 1, "description": "A slug from search_foods (for example 'yogurt') or a food name." }, "language": { "enum": [ "tr", "en", "de", "es", "fr", "it", "ru", "ja", "ar" ], "type": "string", "description": "Language of the answer: tr, en, de, es, fr, it, ru, ja or ar. Defaults to the language the food was found in." } }, "additionalProperties": false }arguments 30 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idc1cf872fdaa3385d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c1cf872fdaa3385d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c1cf872fdaa3385d?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.