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

can-ai-recommend-my-business

https://canairecommendmybusiness.com

Registry code: 9728d506ade8a9bc

api record

This MCP server exposes the canonical "assess_ai_recommendation_readiness" tool. Call tools/list to discover it, then tools/call with businessSize, dataMaturity, technicalStack, and optional goals.

endpoint
https://canairecommendmybusiness.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 can-ai-recommend-my-business live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is can-ai-recommend-my-business free to use?
Yes — the hub reached it with no key and no payment.
What tools does can-ai-recommend-my-business have?
2 tools: assess_ai_recommendation_readiness, get_ai_readiness_framework.
Is can-ai-recommend-my-business 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 99.7%· all time 99.7%

latency
640ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 304 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • assess a business's readiness to be recommended by ai
  • get the ai readiness scoring framework
takes → gives
data → data
tools
2 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 2 tools
1 open 1 never probed 1 of 2 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_ai_readiness_framework reads open 8h ago

    Returns the AI Recommendation Readiness scoring framework: the scored dimensions and their weights, the four readiness tiers with score ranges, and every valid input option (business sizes, data maturity levels, technical stacks, and goals). Read-only and deterministic; use it to understand how the assessment is scored and to build valid inputs for assess_ai_recommendation_readiness.

    mcp-tool

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

    Assesses whether a business is ready to be understood, verified, trusted, recommended, and used by AI systems, based on structured inputs (business size, data availability/maturity, technical stack/infrastructure, and goals). Returns a readiness score, tier, gap analysis, priority actions, and a phased implementation roadmap. Deterministic and read-only: it performs no consequential actions and does not guarantee any ranking or recommendation.

    mcp-tool

    {
      "type": "object",
      "required": [
        "businessSize",
        "dataMaturity",
        "technicalStack"
      ],
      "properties": {
        "goals": {
          "type": "array",
          "items": {
            "enum": [
              "ai_visibility",
              "lead_generation",
              "trust_authority",
              "content_coverage",
              "conversion_optimization",
              "structured_data",
              "agent_readiness",
              "reputation_management"
            ],
            "type": "string"
          },
          "default": [
            "ai_visibility"
          ],
          "maxItems": 8,
          "minItems": 1,
          "description": "One or more readiness goals the business wants to prioritize (1–8, unique values from the enum).",
          "uniqueItems": true
        },
        "industry": {
          "type": "string",
          "description": "Optional industry/category for context."
        },
        "businessName": {
          "type": "string",
          "description": "Optional, non-sensitive business name for context."
        },
        "businessSize": {
          "enum": [
            "solo",
            "micro",
            "small",
            "midmarket",
            "enterprise"
          ],
          "type": "string",
          "description": "Size of the business/organization."
        },
        "dataMaturity": {
          "enum": [
            "none",
            "basic",
            "developing",
            "structured",
            "advanced"
          ],
          "type": "string",
          "description": "Availability and maturity of the structured/machine-readable data of the business."
        },
        "technicalStack": {
          "enum": [
            "minimal",
            "standard",
            "modern",
            "advanced"
          ],
          "type": "string",
          "description": "Technical stack / infrastructure sophistication."
        }
      }
    }
    arguments 73 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 9728d506ade8a9bc.

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

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.