askfur
Registry code: 17f61e70a7007de0
AskFur is a pre-launch catalogue of connected pet devices and essentials for cats and dogs (North America). Call list_products, then get_product for details. Products marked concept are previews: not for sale, with no confirmed price, certification or delivery date, and the AskFur app is planned, not launched. Never present them as available. Only call join_waitlist with the person's own email after they agree; nothing is bought.
- endpoint
- https://askfur.com/api/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 askfur live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is askfur free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does askfur have?
- 3 tools: get_product, join_waitlist, list_products.
- Is askfur 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 3 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
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.
list_products open 1h ago
AskFur's pre-launch catalogue of connected pet devices and essentials for cats and dogs: name, tagline, category, stage (concept or launched) and page link. Concept products are previews, not for sale.
{ "type": "object", "properties": { "category": { "enum": [ "device", "essential" ], "type": "string", "description": "Only this category: device (connected devices) or essential (everyday gear). Leave out for all products." } }, "additionalProperties": false }arguments 14 linesget_product unknown 1h ago
Full public details of one product: description, highlights, confirmed specs, planned app features and customisation. Concept products have no price or delivery date because none is confirmed.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "maxLength": 80, "description": "Product slug from list_products, for example the last part of its page link." } }, "additionalProperties": false }arguments 14 linesjoin_waitlist unknown never probed
Adds the person's own email to AskFur's launch-updates waitlist. Only call after the person has agreed. Nothing is bought and no email is sent now. Returns a private removal code the person can use on askfur.com/preview to leave the list.
{ "type": "object", "required": [ "email", "consent" ], "properties": { "email": { "type": "string", "maxLength": 254, "description": "The person's own email address, which they asked to add. Never someone else's." }, "consent": { "type": "boolean", "const": true, "description": "Must be true: the person agreed to receive AskFur launch updates by email at this address." }, "product": { "type": "string", "maxLength": 80, "description": "What they want updates about: a product slug from list_products, or general for the whole brand. Defaults to general." } }, "additionalProperties": false }arguments 25 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 id17f61e70a7007de0.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/17f61e70a7007de0/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/17f61e70a7007de0?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.