_ registry / mcp http-sse · checked 1h ago

com.unitebr.research/benchmark

https://research.unitebr.com

Registry code: 2b06c35c635bcd0e

api record

Read published Brazil Black Friday creative benchmarks, chart data and citations.

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

endpoint
https://research.unitebr.com/mcp
protocol
http-sse ·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 com.unitebr.research/benchmark live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is com.unitebr.research/benchmark free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.unitebr.research/benchmark have?
3 tools: get_chart_data, get_citation, list_charts.
Is com.unitebr.research/benchmark 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
272ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 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.

  • get_citation open 1h ago

    Retrieve source, canonical URL, dates, methodology, interpretation limits and reuse terms. Optionally include a chart-specific comparison, period and population.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "chart_id": {
      "enum": [
        "ch-hook",
        "ch-opp",
        "ch-bfmenu",
        "ch-bfhow",
        "ch-bfdur",
        "ch-place",
        "ch-ret",
        "ch-bflaunch",
        "ch-read",
        "ch-zero",
        "ch-bfday",
        "ch-bfweek",
        "ch-bfdates",
        "ch-bframp",
        "ch-bfsplit",
        "ch-scale",
        "ch-bffreq",
        "ch-bfpost",
        "ch-bfplan"
      ],
      "type": "string",
      "description": "A chart_id returned by list_charts."
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • list_charts open 1h ago

    Find published Black Friday Brazil research charts by topic. Returns chart IDs, column labels, comparisons, periods and population. Use get_chart_data to retrieve the values.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum items per page, from 1 to 50."
    },
    "query": {
      "type": "string",
      "maxLength": 160,
      "description": "Topic such as CPM, oferta, conversão or thumbstop."
    },
    "cursor": {
      "type": "string",
      "maxLength": 512,
      "description": "Opaque next_cursor from the previous response."
    },
    "offset": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Legacy zero-based offset. Use either cursor or offset."
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
  • get_chart_data unknown 1h ago

    Retrieve a published chart with its values, units, comparison, period, population, source and methodology. Values keep their Portuguese display formatting. Follow next_cursor for remaining rows.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "chart_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum items per page, from 1 to 50."
    },
    "cursor": {
      "type": "string",
      "maxLength": 512,
      "description": "Opaque next_cursor from the previous response."
    },
    "offset": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Legacy zero-based offset. Use either cursor or offset."
    },
    "chart_id": {
      "enum": [
        "ch-hook",
        "ch-opp",
        "ch-bfmenu",
        "ch-bfhow",
        "ch-bfdur",
        "ch-place",
        "ch-ret",
        "ch-bflaunch",
        "ch-read",
        "ch-zero",
        "ch-bfday",
        "ch-bfweek",
        "ch-bfdates",
        "ch-bframp",
        "ch-bfsplit",
        "ch-scale",
        "ch-bffreq",
        "ch-bfpost",
        "ch-bfplan"
      ],
      "type": "string",
      "description": "A chart_id returned by list_charts."
    }
  },
  "additionalProperties": false
}
    arguments 52 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 2b06c35c635bcd0e.

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