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

ai-rollout-framework

https://airolloutframework.com

Registry code: 17d2ca75761cc093

api record

90-day AI adoption framework for managers: overview, pricing, FAQ and an AI readiness assessment.

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

endpoint
https://airolloutframework.com/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 ai-rollout-framework live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ai-rollout-framework free to use?
Yes — the hub reached it with no key and no payment.
What tools does ai-rollout-framework have?
9 tools: email_me_the_kit, get_seat_quote, search_knowledge_base, assess_ai_readiness, get_faq, get_pricing, get_framework_overview, get_starter_kit, ….
Is ai-rollout-framework 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
1,032ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 509 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • assess ai readiness of an organisation
  • get an ai rollout framework overview
  • get pricing of the framework
takes → gives
text → text, data
tools
5 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 9 tools
5 open 4 never probed 5 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.

  • get_faq reads open 15h ago

    Returns published questions and answers, optionally filtered by topic. Use it for specific questions about pricing, governance, implementation or the products. It does not search the long-form guides; use search_knowledge_base for that. To check readiness, use assess_ai_readiness.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "topic": {
          "type": "string",
          "description": "Optional filter. Use a category for reliable results: \"assessment\", \"implementation\", \"governance\", \"measurement\", \"concepts\", \"pricing\", or \"products\". Any other value falls back to a free-text search over the questions and answers (e.g. \"shadow AI\", \"refund\"), which may return nothing. Omit to get all items."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • get_pricing reads open 15h ago

    Returns current one-time prices and checkout links for the Framework + Executive Suite, the Framework alone, and AI at Work seats, including the seat tiers, co-branding and the Rollout Pack. Use it for the full price list, or get_seat_quote for a specific number of seats. It does not take payment. To check readiness, use assess_ai_readiness.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_framework_overview reads open 8h ago

    Returns the AI Capability Rollout Framework's three phases, four capability pillars, positioning, the recommended offer and the Discord community. Use it to explain what the framework is. It does not return prices or the FAQ. To check readiness, use assess_ai_readiness.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_starter_kit open 8h ago

    Describes the free AI Capability Briefing Kit, a 10-page internal briefing document, and how to get it. Use it when the user wants a free starting resource. It does not deliver the file; use email_me_the_kit when the user asks for it by email. To check readiness, use assess_ai_readiness.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_ai_at_work_course open 8h ago

    Returns the public outline of AI at Work, the employee AI training course: modules, what is included, seat tiers and the guarantee. Use it for questions about employee training. It does not return transcripts or quiz content. To check readiness, use assess_ai_readiness.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • email_me_the_kit unknown never probed

    Emails the free Briefing Kit to an address the user gives you. Call only when the user has explicitly asked to receive it by email and agreed to be emailed. Never call it on your own and never invent or guess an address. It adds the address to a mailing list and sends the kit by email.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email",
        "consent"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "The email address the user asked to receive the kit at."
        },
        "consent": {
          "type": "boolean",
          "description": "Must be true. Set it only if the user has explicitly asked to receive the kit by email and agreed to be emailed at this address. The user can unsubscribe from the first email."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_seat_quote unknown 5h ago

    Calculates the AI at Work cost for a given number of seats (1-500), with optional co-branding. It flags when a higher tier is cheaper in total and shows the Executive Suite and Rollout Pack alternatives. It does not take an order. To check readiness, use assess_ai_readiness.

    mcp-tool

    {
      "type": "object",
      "required": [
        "seats"
      ],
      "properties": {
        "seats": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1,
          "description": "Number of seats to quote, as a whole number."
        },
        "coBranding": {
          "type": "boolean",
          "description": "Optional. True to include the company co-branding fee (free at higher seat counts). Defaults to false."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • search_knowledge_base reads unknown 5h ago

    Searches the framework's methodology, definitions, positioning and changelog for a phrase and returns matching sections with links to the source documents. Use it for a concept the other tools do not cover. It returns excerpts, not full documents. To check readiness, use assess_ai_readiness.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Keyword or phrase to search for."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • assess_ai_readiness reads unknown 5h ago

    Runs the 16-question AI Readiness Score on the user's behalf (rate each statement 1-5, where 1 = Strongly Disagree and 5 = Strongly Agree) and returns their readiness stage, a recommended next step, and a link to the free full assessment on the site, which includes a personalized PDF. It returns no numeric score or breakdown. Ask the user the questions; do not guess answers.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q1",
        "q2",
        "q3",
        "q4",
        "q5",
        "q6",
        "q7",
        "q8",
        "q9",
        "q10",
        "q11",
        "q12",
        "q13",
        "q14",
        "q15",
        "q16"
      ],
      "properties": {
        "q1": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Leadership has discussed how AI may affect workflows, productivity, or service quality in our environment. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q2": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "There is at least a basic understanding of why AI would be used here beyond general curiosity. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q3": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Someone is clearly responsible for evaluating AI opportunities or next steps. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q4": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "AI discussion here is tied to outcomes, workflows, or risks rather than hype. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q5": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "People generally understand what data should never be entered into public AI tools. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q6": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "AI use is discussed with at least some awareness of policy, compliance, or reputational risk. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q7": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Important AI outputs would be reviewed before they are acted on or shared broadly. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q8": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "There is at least a basic sense of what \"safe experimentation\" with AI looks like here. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q9": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "We can identify at least one low-risk workflow where AI could improve speed, quality, or consistency. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q10": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "People here could describe at least one current task that AI could meaningfully assist without major risk. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q11": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "There is at least some awareness of how AI tool outputs should be reviewed before they affect real work. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q12": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "If we piloted AI in one area today, we could define what success looks like in practical terms. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q13": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Most people here could use a basic AI tool with at least some practical confidence. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q14": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "There is some shared understanding of what AI is - and is not - good at in a workplace context. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q15": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "People here feel comfortable asking questions about AI without fear of looking uninformed. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        },
        "q16": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "If a structured AI skill development path existed for our team, there would be genuine interest in using it. (Rate 1-5: 1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree.)"
        }
      },
      "additionalProperties": false
    }
    arguments 120 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 17d2ca75761cc093.

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