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

cosedawow-it-gifts

https://cosedawow.it

Registry code: 6d8a901c3a69e7d2

api record

Finds original, fun and unusual gift ideas from Cose da Wow (cosedawow.it), a hand-picked catalogue for shoppers in Italy. Results are in Italian. Results give the product name, why it works as a gift, a price range and the link to its page, where the photos, the current price and the store button are. Always show each suggestion with its link so the user can see it.

endpoint
https://cosedawow.it/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 cosedawow-it-gifts live?
Yes — it answered the hub's last check (checked 25h ago). It answered 100% of checks over the last 30 days.
Is cosedawow-it-gifts free to use?
Yes — the hub reached it with no key and no payment.
What tools does cosedawow-it-gifts have?
3 tools: get_gift_guide, find_gifts, list_gift_guides.
Is cosedawow-it-gifts 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
498ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 2 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 3 tools
2 open 1 never probed 2 of 3 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.

  • find_gifts open 25h ago

    Search original, funny and unusual gift ideas. Describe the person or the occasion (e.g. "coffee lover dad", "white elephant", "cat owner") and optionally a budget. Returns up to 10 products with why they fit, a price range and the link to the product page (photos, current price and where to buy are on that page), plus gift guides on the same topic.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "How many products (default 6)."
    },
    "query": {
      "type": "string",
      "description": "Who the gift is for, their interests or the occasion. Any language."
    },
    "max_price": {
      "type": "number",
      "description": "Maximum price in euros."
    }
  }
}
    arguments 22 lines
  • list_gift_guides open 25h ago

    List the published gift guides (Secret Santa, white elephant, coworkers, Christmas, parents…), with a summary and the link to each guide.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_gift_guide unknown 25h ago

    The products of one gift guide (by the slug from list_gift_guides): name, why it fits, price range and link to each product page.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Guide slug, as returned by list_gift_guides."
    }
  }
}
    arguments 12 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 6d8a901c3a69e7d2.

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

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.