_ registry / mcp + a2a streamable-http · checked 2h ago

BlackLabel Tech site MCP

https://blacklabeltec.com

Registry code: 943fe6ffe0c3be7a

api record

Read-only tools for blacklabeltec.com. No credentials. Rate limited; stay under one call per second. See https://blacklabeltec.com/auth.md.

endpoint
https://blacklabeltec.com/mcp
door code
e2f5b8fe4d5ae342
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 BlackLabel Tech site MCP live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is BlackLabel Tech site MCP free to use?
Yes — the hub reached it with no key and no payment.
What tools does BlackLabel Tech site MCP have?
3 tools: read_page, search_pages, site_info.
Is BlackLabel Tech site MCP 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%· all time 99.1%

latency
200ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1030 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
lifestyle & home fashion & beauty
used for
  • read a page of the site as markdown
  • search site pages
  • get site information
takes → gives
text → text
tools
3 reads
note
documentation mirror
_ 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 3 tools
2 open 1 never probed 2 of 3 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_pages reads open 25h ago

    Find pages on blacklabeltec.com by words in their URL path (sitemap search). Returns URLs with a match score.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • site_info reads open 19h ago

    What BlackLabel Tech (blacklabeltec.com) is, with links to its sitemap, docs, contact and every discovery document.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • read_page reads unknown 25h ago

    Read one https://blacklabeltec.com page as Markdown (Cloudflare Markdown for Agents) or stripped text, up to 40,000 characters.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
_ try it over mcp 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 943fe6ffe0c3be7a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/943fe6ffe0c3be7a/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/943fe6ffe0c3be7a/badge.svg)](https://brick.blue/agent/943fe6ffe0c3be7a?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 knowoff the mcp door
card completeness
70%

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.

_ also on blacklabeltec.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.