_ registry / mcp streamable-http · checked 21m ago

vibesignet

https://vibesignet.com

Registry code: b0f84e5a324dfe99

api record

Vibesignet is a library of website templates sold as build prompts. Use search_templates to find a template by sector or style, get_template to see its sections, then get_prompt to fetch the full build prompt and follow it exactly: it asks for a plan first, then checkpoint frames, then the build. get_prompt needs the user's Vibesignet access key.

endpoint
https://vibesignet.com/api/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 vibesignet live?
Yes — it answered the hub's last check (checked 21m ago). It answered 100% of checks over the last 30 days.
Is vibesignet free to use?
Yes — the hub reached it with no key and no payment.
What tools does vibesignet have?
5 tools: get_component_prompt, get_template, get_prompt, search_components, search_templates.
Is vibesignet 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
246ms

last good check

priced tools
0

of 5 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 5 tools
2 open 3 never probed 2 of 5 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.

  • search_components open 21m ago

    Search the Vibesignet components: single scenes, backgrounds, interactions and sections, each one standalone, to drop into an existing site. Returns each component's id, kind and one line. No access key needed. Call with no arguments to list them all.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Words to match against the name, kind and description, for example \"ripple\" or \"scroll gallery\"."
        }
      }
    }
    arguments 9 lines
  • search_templates open 21m ago

    Search the Vibesignet template library. Returns matching templates with their key, sector, look and a one-line description. No access key needed. Call with no arguments to list every template.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "look": {
          "enum": [
            "light",
            "mid",
            "dark"
          ],
          "type": "string",
          "description": "Limit to light, mid-tone or dark templates."
        },
        "query": {
          "type": "string",
          "description": "Words to match against the name, sector, product and description, for example \"flight school\" or \"watch\"."
        },
        "sector": {
          "type": "string",
          "description": "Limit to one sector, for example \"Hospitality\"."
        }
      }
    }
    arguments 22 lines
  • get_component_prompt unknown 21m ago

    The full build prompt for one component. Needs the access key of a paid Vibesignet plan (Monthly, Yearly or Founders), sent as the Authorization header or as access_key. Components have their own allowance (15 new in any 30 days on Monthly) and never use a template unlock; fetching one again is free.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The component id from search_components, for example \"ripple\"."
        },
        "access_key": {
          "type": "string",
          "description": "The user's access key (starts with vs_), if it was not set on the connection."
        }
      }
    }
    arguments 16 lines
  • get_template unknown never probed

    One template's public details: what it is for, its sections in order with a one-line summary each, how many photographs and films the build needs, and its page on vibesignet.com. No access key needed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "key"
      ],
      "properties": {
        "key": {
          "type": "string",
          "description": "The template key from search_templates, for example \"kestrel\"."
        }
      }
    }
    arguments 12 lines
  • get_prompt unknown never probed

    The full build prompt for one template. Needs the user's Vibesignet access key, sent as the Authorization header of this connection or as the access_key argument. A free key unlocks 1 template of the user's choice; fetching it again is free.

    mcp-tool

    {
      "type": "object",
      "required": [
        "key"
      ],
      "properties": {
        "key": {
          "type": "string",
          "description": "The template key, for example \"kestrel\"."
        },
        "access_key": {
          "type": "string",
          "description": "The user's access key (starts with vs_), if it was not set on the connection."
        }
      }
    }
    arguments 16 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 b0f84e5a324dfe99.

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

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.