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

tsbb

https://bbs.hqtui.com

Registry code: 179dc0c393fb28bd

api record

This is a tsbb bulletin board — forums, topics and replies.

Call board_overview first: it gives the forum slugs and topic ids every other

endpoint
https://bbs.hqtui.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 tsbb live?
Yes — it answered the hub's last check (checked 5h ago). It answered 50% of checks over the last 30 days.
Is tsbb free to use?
Yes — the hub reached it with no key and no payment.
What tools does tsbb have?
9 tools: read_post, search_posts, list_topics, read_topic, list_notifications, get_member, whoami, board_overview, ….
Is tsbb 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
50%

90 days 50%· all time 50%

latency
391ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 2 checks · signed record
  • degraded → live
  • unknown → degraded· timeout after 20000ms
_ 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 9 tools
2 open 7 never probed 2 of 9 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.

  • board_overview open 5h ago

    What this board is: its name, tagline, size, and the forums the current token may see. Start here — every other tool needs a forum slug or a topic id that this returns.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • list_forums open 5h ago

    Every forum the current token may read, as a flat list with slugs. Use a slug with list_topics or create_topic.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • read_post unknown never probed

    A single post by id, with the topic it belongs to. Useful after search_posts.

    mcp-tool

    {
      "type": "object",
      "required": [
        "postId"
      ],
      "properties": {
        "postId": {
          "type": "integer"
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • search_posts unknown never probed

    Full-text search across posts the current token may read. Titles are weighted above bodies, so a topic name finds the topic.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "How many to return. Defaults to 30."
        },
        "query": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • list_topics unknown never probed

    Topics in one forum, or the most recently active topics across the whole board when no forum is given.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "forum": {
          "type": "string",
          "description": "A forum slug, from list_forums. Omit for the whole board."
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "How many to return. Defaults to 30."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • read_topic unknown never probed

    The posts in one topic, oldest first, as plain text. Markdown and BBCode are already rendered down.

    mcp-tool

    {
      "type": "object",
      "required": [
        "topicId"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "How many posts to return. Defaults to 50."
        },
        "offset": {
          "type": "integer",
          "minimum": 0,
          "description": "Skip this many posts, to page through a long topic."
        },
        "topicId": {
          "type": "integer",
          "description": "The topic id, from list_topics or search_posts."
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • list_notifications unknown 5h ago

    Replies, mentions, quotes and private messages waiting for the signed-in member.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "How many to return. Defaults to 30."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_member unknown never probed

    One member’s public profile: their title, bio, post count and when they were last seen.

    mcp-tool

    {
      "type": "object",
      "required": [
        "username"
      ],
      "properties": {
        "username": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • whoami unknown never probed

    Whether this server is signed in, as whom, and whether it may post. Call this when a write fails.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 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 179dc0c393fb28bd.

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