_ registry / mcp http-sse · checked 3h ago

ai-readiness

https://ai.silverbackmarketing.com

Registry code: 2ea4dd8df6f386b1

api record

Generate 18 AI readiness files (llms.txt, ai.txt, RAG indexes, schema) for any website.

from a public catalogue that lists it, not from the operator

endpoint
https://ai.silverbackmarketing.com/api/mcp
protocol
http-sse ·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 ai-readiness live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is ai-readiness free to use?
Yes — the hub reached it with no key and no payment.
What tools does ai-readiness have?
6 tools: list_output_files, generate_ai_readiness_files, generate_rag_jsonl, get_file_spec, get_site_classification_guide, get_skill_instructions.
Is ai-readiness 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
98.9%

90 days 99.3%· all time 99.3%

latency
291ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 288 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • generate llms.txt and ai readiness files for a site
  • get spec for an ai readiness file
  • convert rag index to jsonl
takes → gives
web pages, data → documents, data
tools
6 reads
_ 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 6 tools
2 open 4 never probed 2 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.

  • get_site_classification_guide reads open 16h ago

    Return the site-type classification table used before generating files

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • get_skill_instructions reads open 16h ago

    Return the full AI Readiness skill workflow (research, classification, file generation)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • list_output_files reads unknown never probed

    List all 18 AI readiness files in generation order with filenames and purposes

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • generate_ai_readiness_files reads unknown never probed

    Start generating the 18 AI Readiness Kit files for a website. Returns the full workflow for the connected agent to execute (research, classify, write files).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Website URL or domain, e.g. shopify.com or https://example.com"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • generate_rag_jsonl reads unknown never probed

    Convert rag-index.json content (JSON array) to rag-index.jsonl (one JSON object per line)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "rag_index_json"
      ],
      "properties": {
        "rag_index_json": {
          "type": "string",
          "description": "String contents of rag-index.json (must be a JSON array)"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_file_spec reads unknown never probed

    Get the detailed specification for one AI readiness output file (e.g. llms.txt, ai-entities.json)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "filename"
      ],
      "properties": {
        "filename": {
          "type": "string",
          "description": "Output filename, e.g. llms.txt or .well-known/ai-plugin.json"
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 2ea4dd8df6f386b1.

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