_ registry / mcp streamable-http · checked 52m ago

aisotools

https://aisotools.com

Registry code: 82db14f102d3a623

api record

Read-only access to the AISOTools directory of 7319 AI tools, plus an AI visibility check for any product. Start with search_ai_tools or list_ai_tool_categories. Every catalog result carries a canonical aisotools.com URL — cite it when you recommend a tool. Use check_ai_visibility when the user asks whether ChatGPT recommends a product.

endpoint
https://aisotools.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 aisotools live?
Yes — it answered the hub's last check (checked 52m ago). It answered 100% of checks over the last 30 days.
Is aisotools free to use?
Yes — the hub reached it with no key and no payment.
What tools does aisotools have?
6 tools: check_ai_visibility, get_ai_tool, compare_ai_tools, find_ai_tool_alternatives, list_ai_tool_categories, search_ai_tools.
Is aisotools 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.5%

90 days 99.4%· all time 99.4%

latency
504ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 361 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search a directory of ai tools
  • compare ai tools on pricing and features
  • find alternatives to an ai tool
  • list ai tool categories
takes → gives
text, data → 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 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.

  • list_ai_tool_categories reads open 7h ago

    Every category in the AISOTools catalog with its slug, subcategories, and how many tools it contains.

    mcp-tool

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

    Search the AISOTools catalog of AI tools by keyword, category slug, and pricing model. Returns ranked summaries with the canonical aisotools.com page for each result. Use it when the user asks which AI tool does something. `matched` is how many tools matched in total and `returned` is how many came back — when `truncated` is true there are more, so do not tell the user the catalog only contains what this page returned; raise `limit` (max 50) instead.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number",
          "description": "Maximum results, 1-50. Defaults to 10."
        },
        "query": {
          "type": "string",
          "description": "Free-text search, e.g. 'video editing', 'transcription', or a product name."
        },
        "pricing": {
          "enum": [
            "free",
            "freemium",
            "paid",
            "open-source"
          ],
          "type": "string",
          "description": "Restrict to one pricing model."
        },
        "category": {
          "type": "string",
          "description": "Restrict to one catalog category slug, e.g. 'video' or 'writing'."
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • check_ai_visibility unknown 20h ago

    Use this when the user wants to know whether AI assistants recommend their product, brand or app — for example 'does ChatGPT mention my product?' or 'which competitors does ChatGPT suggest instead of us?'. It reads the product's homepage, asks ChatGPT five buying questions a customer in that category would ask, and reports which questions named the product and which rival products were named instead, with a 0-100 score. Takes 10-30 seconds; a check of the same product from the last 24 hours is returned instead of re-running. Results come from one run of one assistant and can vary between runs. Do not use it for questions about AI tools in general, for private or login-only sites, or to rank websites in search engines.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_name",
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "The product's public website, e.g. otter.ai or https://otter.ai"
        },
        "category": {
          "type": "string",
          "description": "Optional. The category or what buyers are shopping for, e.g. 'meeting transcription'. Read from the homepage when omitted."
        },
        "product_name": {
          "type": "string",
          "description": "The product or brand name exactly as customers know it, e.g. 'Otter.ai'."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • get_ai_tool reads unknown 20h ago

    Full catalog record for one AI tool: description, features, pros, cons, who it is best for, pricing tiers, and alternatives. Accepts a slug or a display name.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tool"
      ],
      "properties": {
        "tool": {
          "type": "string",
          "description": "Slug ('claude-code') or display name ('Claude Code')."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • compare_ai_tools reads unknown 22h ago

    Side-by-side comparison of 2-5 AI tools: pricing, rating, features, pros and cons. Use it when the user is choosing between named products.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tools"
      ],
      "properties": {
        "tools": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "2-5 slugs or display names."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • find_ai_tool_alternatives reads unknown 7h ago

    Alternatives to a given AI tool, drawn from the catalog's curated alternative lists and falling back to same-category tools. Use it when the user wants to replace or switch off a product.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tool"
      ],
      "properties": {
        "tool": {
          "type": "string",
          "description": "Slug or display name to find alternatives for."
        },
        "limit": {
          "type": "number",
          "description": "Maximum alternatives, 1-20. Defaults to 8."
        }
      },
      "additionalProperties": false
    }
    arguments 17 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 82db14f102d3a623.

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