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

winder

https://mcp.withblueberry.com

Registry code: 48c56cc10f2babcb

api record

Winder hub data and actions require OAuth. This anonymous connection exposes only public connection_reauthenticate guidance. Ask whether to reauthenticate first; call confirmed=true only after the user agrees. Let this client complete OAuth, refresh its tool list and verify with connection_context before resuming the original task.

endpoint
https://mcp.withblueberry.com/mcp
protocol
streamable-http ·2025-06-18
authentication
bearer
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 winder live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is winder free to use?
Yes — the hub reached it with no key and no payment.
What tools does winder have?
1 tool: connection_reauthenticate.
Is winder 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.6%

90 days 99.4%· all time 99.4%

latency
2,040ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 356 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
ai & agents memory & context
used for
  • search saved knowledge and memories
  • update hub content
takes → gives
text → text, data
_ 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 1 tools
1 open 1 of 1 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.

  • connection_reauthenticate open 19h ago

    Use when a Winder call reports UNAUTHORIZED, invalid_token, or that the app connection requires reauthentication. First ask the user whether to reauthenticate; confirmed=false returns the question without opening OAuth. After explicit agreement call confirmed=true to request the client's OAuth linking UI and return reconnect links. This public tool returns guidance only, never user data or tokens. A client that blocks the app before sending requests may require reconnecting in its settings.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "client": {
      "enum": [
        "chatgpt",
        "claude",
        "codex",
        "other"
      ],
      "type": "string",
      "default": "other"
    },
    "confirmed": {
      "type": "boolean",
      "default": false,
      "description": "True only after the user explicitly agrees to reauthenticate this Winder app connection."
    }
  },
  "additionalProperties": false
}
    arguments 22 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 48c56cc10f2babcb.

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

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.