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

kitscout

https://mcp.kitscout.dev

Registry code: d5d9595fbfc5c833

api record

KitScout indexes ~88,000 AI agent tools: MCP servers (official MCP Registry and GitHub), Agent Skills (GitHub SKILL.md) and Claude Code plugins, with GitHub activity, publisher identity and a daily live check of every remote MCP server (live = answers, some need sign-in; free_to_try = a read-only call worked with no API key).

Tools: search_tools finds tools by product or task keywords; get_tool returns details, install or connect lines and a remote server's tool list; check_tools verifies tools the user already has in mind (maker, maintenance, adoption, live status, alternatives);…

endpoint
https://mcp.kitscout.dev/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 kitscout live?
Yes — it answered the hub's last check (checked 17m ago). It answered 100% of checks over the last 30 days.
Is kitscout free to use?
Yes — the hub reached it with no key and no payment.
What tools does kitscout have?
5 tools: watchlist, search_tools, get_tool, check_tools, list_categories.
Is kitscout 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
86ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 5 tools
1 open 4 never probed 1 of 5 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_categories open 17m ago

    All KitScout categories (id, name, group, tool count). Useful to see what kinds of tools exist before searching.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • watchlist unknown never probed

    Your KitScout watch list (needs a free key: connect with https://mcp.kitscout.dev/mcp?key=<key>, get one at kitscout.dev/watch). Tools you check_tools with a key are added automatically; KitScout emails you when one is renamed, archived, deprecated or stops answering. Shows each watched tool with its last verdict; pass remove to stop watching tools.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "remove": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Tool names or URLs to stop watching (as listed)"
        }
      }
    }
    arguments 12 lines
  • search_tools unknown never probed

    Search ~88k AI agent tools (MCP servers, Agent Skills, Claude Code plugins) by keywords. Returns ranked matches with type, category, GitHub stars, badges (first_party = made by the product's own maker, verified_publisher, live, free_to_try), install line and KitScout page. Use short keywords: product + action, e.g. 'postgres', 'slack post message', 'pdf extract tables'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "type": {
          "enum": [
            "mcp",
            "skill",
            "plugin"
          ],
          "type": "string",
          "description": "Only this kind of tool"
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max results (default 10)"
        },
        "query": {
          "type": "string",
          "description": "Keywords (product names and actions work best)"
        },
        "only_live": {
          "type": "boolean",
          "description": "Only remote MCP servers that answered our latest daily check (including ones that answer with a sign-in/OAuth request)"
        },
        "only_official": {
          "type": "boolean",
          "description": "Deprecated alias of only_verified"
        },
        "only_verified": {
          "type": "boolean",
          "description": "Only verified publishers (domain-verified registry namespace, Anthropic marketplace). Does not mean made by the product's vendor; see the first_party badge"
        },
        "only_free_to_try": {
          "type": "boolean",
          "description": "Only remote MCP servers that worked without an API key"
        }
      }
    }
    arguments 43 lines
  • get_tool unknown 17m ago

    Details for one KitScout tool by its exact name: description, badges, stars, repo, install or connect instructions, and for remote MCP servers the actual tool list the server exposes (from our live check).

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Exact tool name as listed in KitScout"
        }
      }
    }
    arguments 12 lines
  • check_tools unknown 17m ago

    Before installing tools you found elsewhere (web search, a README, a blog), verify them: is it the product maker's own tool, maintained (last code change, archived?), adopted (stars), does the remote server answer right now, where does your data go — with a verdict (ok / caution / avoid) and better alternatives. Pass up to 5 GitHub URLs, package ids (npm/pypi), remote MCP URLs or names per call.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tools"
      ],
      "properties": {
        "tools": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 5,
          "description": "e.g. https://github.com/owner/repo, @scope/package, https://mcp.example.com/mcp"
        }
      }
    }
    arguments 16 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 d5d9595fbfc5c833.

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

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.