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

binarybirthday

https://www.binarybirthday.com

Registry code: 19f9dce52c9f6a5d

api record

Converts birthdays, names, words and numbers to binary code and back. Every conversion includes links to personalized gifts (mug, tee, hoodie, phone case, card wallet, baby onesie) with the code pre-filled. Use date_to_binary for birthdays and anniversaries, text_to_binary for names and messages (up to 16 characters fit on a gift), and suggest_binary_gifts when the user wants a gift idea.

endpoint
https://www.binarybirthday.com/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 binarybirthday live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is binarybirthday free to use?
Yes — the hub reached it with no key and no payment.
What tools does binarybirthday have?
6 tools: text_to_binary, binary_to_number, date_to_binary, number_to_binary, binary_to_text, suggest_binary_gifts.
Is binarybirthday 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
354ms

last good check

priced tools
0

of 6 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
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 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.

  • suggest_binary_gifts open 1h ago

    Suggest personalized binary-code gifts for programmers, engineers, couples or new parents. Give a date or a short text and get each product with a link that pre-fills the code. Use when the user asks for gift ideas for a techie, a geek, an anniversary or a baby.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "date": {
          "type": "string",
          "description": "Optional date to encode, YYYY-MM-DD (birthday, wedding, baby's birth date)"
        },
        "text": {
          "type": "string",
          "description": "Optional name or short message to encode, up to 16 characters"
        }
      }
    }
    arguments 13 lines
  • text_to_binary unknown never probed

    Convert text such as a name, initials or a short message to 8-bit binary (UTF-8). Text up to 16 characters also returns gift links.

    mcp-tool

    {
      "type": "object",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "description": "Text to convert, e.g. \"Emma\" or \"I love you\""
        }
      }
    }
    arguments 12 lines
  • binary_to_number unknown 1h ago

    Convert binary to a whole decimal number.

    mcp-tool

    {
      "type": "object",
      "required": [
        "binary"
      ],
      "properties": {
        "binary": {
          "type": "string",
          "description": "Binary such as \"11111101001\""
        }
      }
    }
    arguments 12 lines
  • date_to_binary unknown never probed

    Convert a date (birthday, anniversary, due date) to its BinaryBirthday code: 12-bit year, 4-bit month, 5-bit day. Returns gift links with the code pre-filled.

    mcp-tool

    {
      "type": "object",
      "required": [
        "date"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "Date as YYYY-MM-DD, e.g. 1990-06-15"
        }
      }
    }
    arguments 12 lines
  • number_to_binary unknown never probed

    Convert a whole decimal number to binary.

    mcp-tool

    {
      "type": "object",
      "required": [
        "number"
      ],
      "properties": {
        "number": {
          "type": "string",
          "description": "Whole number, e.g. \"2025\""
        }
      }
    }
    arguments 12 lines
  • binary_to_text unknown 1h ago

    Decode binary (0s and 1s, spaced or not) into text, and also read it as a whole number.

    mcp-tool

    {
      "type": "object",
      "required": [
        "binary"
      ],
      "properties": {
        "binary": {
          "type": "string",
          "description": "Binary such as \"01001000 01101001\""
        }
      }
    }
    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 19f9dce52c9f6a5d.

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

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
1
ok
1
failed
0
success rate
100%
median latency
344ms
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
—

1 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.

_ also on binarybirthday.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.