_ registry / mcp + a2a streamable-http · checked 3h ago

dealerific

https://dealerific.com

Registry code: c91a0b5418155cde

api record

Current retail deals by category and store, with buying guides. Affiliate links.

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

endpoint
https://dealerific.com/api/mcp
door code
530bbf8b2d506316
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 dealerific live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is dealerific free to use?
Yes — the hub reached it with no key and no payment.
What tools does dealerific have?
3 tools: list_articles, list_categories, search_deals.
Is dealerific 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.5%

90 days 99.1%· all time 98.8%

latency
463ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 2341 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
payments & commerce shopping & products
used for
  • search current retail deals
  • list deal categories and stores
  • list buying guides
takes → gives
text → data
tools
3 reads
_ 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
3 open 3 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.

  • list_articles reads open 14h ago

    The buying guides and roundups published on the site, with what each covers.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_categories reads open 14h ago

    The deal categories, with the stores currently carrying deals.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • search_deals reads open 14h ago

    Current deals, filterable by category and store. Each carries its title, price, store and the link to buy. Links are affiliate links.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max results, default 20"
    },
    "query": {
      "type": "string",
      "description": "Keyword filter across title and description"
    },
    "store": {
      "type": "string",
      "description": "Store name, e.g. Amazon"
    },
    "category": {
      "type": "string",
      "description": "Category slug from list_categories, e.g. kitchen, tech, toys"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
_ try it over mcp 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 c91a0b5418155cde.

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