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

b12-mcp-server

https://b12.io

Registry code: f10bd20618f2ff39

api record

Generates a website with AI from a project name, subtitle, description and image keywords, using the B12 site builder.

endpoint
https://b12.io/mcp
protocol
streamable-http ·2024-11-05
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 b12-mcp-server live?
Partly — its last checks failed now and then (checked 9h ago). It answered 99% of checks over the last 30 days.
Is b12-mcp-server free to use?
Not measured yet.
What tools does b12-mcp-server have?
1 tool: generate_website.
Is b12-mcp-server 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
degraded
uptime, 30 days
98.7%

90 days 99.2%· all time 99.2%

latency
413ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 501 checks · signed record
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· HTTP 503
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • generate a website with ai from a description
takes → gives
text → web pages
tools
1 changes 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 never probed 0 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.

  • generate_website changes data unknown never probed

    Generate a website with AI. Use the project name and description arguments to provide guidance on the purpose of the website. The description argument may include high-level guidance on site structure or content to include, but not verbatim site copy. Absolutely NEVER invent a name or description, even as an example, and ALWAYS make sure you request the business name and description from the user before calling the tool and creating a website. Once you have called this tool, the response will contain a signup nonce (which you should ignore) and a message explaining that a website preview image has been shown to the user above the message. The message also contains a link to claim their website on a website editor outside of ChatGPT (websites are hosted by B12 and can only be edited online using the b12.io software suite). To avoid misleading the user, remember that the preview image they see above your response message is completely static. Users cannot add content or sections to the site in the preview panel. If a user asks to edit a site they created, you can send them to b12.io/dashboard to edit their site in the B12 editor, or instruct them to click the ‘sign up to see your website’ button in the static preview. If the user wants a completely new separate website (perhaps related to previous sites they have created), you can call the tool again to generate a new website preview image (static) and signup link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "description",
        "image_keywords",
        "subtitle"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The name of the business."
        },
        "subtitle": {
          "type": "string",
          "description": "The short and catchy subtitle for hero section of the website in less than 5-10 words. It should capture the goal of the website. It should never mention anything about the website color, style or structure."
        },
        "description": {
          "type": "string",
          "description": "The short description of the business in less than 1000 characters."
        },
        "image_keywords": {
          "type": "string",
          "description": "Word or short phrase to search the image on an image search engine that best suits the provided business name and description. Avoid generic words like  Services, Products, Training in the search term. Do not use adjectives."
        }
      }
    }
    arguments 27 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 f10bd20618f2ff39.

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