Skip to main content
Glama

Search agents

search_agents
Read-onlyIdempotent

Find agents and MCP servers that can do a task you describe in plain words. Use it whenever you need a capability you do not have; then get_agent for one result in full, or verify_endpoint when you already hold a URL. Ranked on what the hub measured — answers its checks, open, paid or key-required, price per call — not on what operators claim. Read-only, no account. Returns the matches with endpoints, tools, liveness and price, so you can pick one and call it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoWhat needs doing, in natural language or keywords
kindNoLimit to one protocol
limitNoMax results (default 7, best first). A longer shelf measurably worsens the pick and costs you the context, so ask for more only when you mean to read it; `hasMore` and `nextOffset` page the rest.
skillNoExact skill or tool name to require
accessNofree/open = the listing answered its handshake without asking for anything, which is what its card says rather than what its tools do. verified-open = this hub has called one of its tools and been served. Ask for verified-open when you need something you can use now; ask for open when you are surveying what is out there.
offsetNoWhere to resume — pass the `nextOffset` from the last answer
warningNonone = leave out listings whose text works on the agent reading it (posing as system instructions, demanding to be called first, pushing referral links…); any = only those; a kind = only that behaviour. Rows that have one carry it as `warning`.
categoryNoA topic, as `area` or `area/topic` (e.g. weather-and-environment/forecast); the listings carry theirs as `topic`. `suspicious` (or `suspicious/<kind>`, e.g. suspicious/poses-as-system) is the category of listings whose text works on the agent reading it
transportNoOnly listings served over this transport, e.g. streamable-http, sse or http

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit / minimum
      Added value: +0
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / transport
      Added value: +{
      +  "description": "Only listings served over this transport, e.g. streamable-http, sse or http",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"A topic, as `area` or `area/topic` (e.g. weather-and-environment/forecast); the listings carry theirs as `topic`"New value: +"A topic, as `area` or `area/topic` (e.g. weather-and-environment/forecast); the listings carry theirs as `topic`. `suspicious` (or `suspicious/<kind>`, e.g. suspicious/poses-as-system) is the category of listings whose text works on the agent reading it"
  3. Changed1 schema field changed
    • addedInput schema / properties / warning
      Added value: +{
      +  "description": "none = leave out listings whose text works on the agent reading it (posing as system instructions, demanding to be called first, pushing referral links…); any = only those; a kind = only that behaviour. Rows that have one carry it as `warning`.",
      +  "enum": [
      +    "none",
      +    "any",
      +    "poses-as-system",
      +    "demands-priority",
      +    "hides-from-user",
      +    "extracts-data",
      +    "self-propagates",
      +    "affiliate-push",
      +    "acts-unprompted"
      +  ],
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "A topic, as `area` or `area/topic` (e.g. weather-and-environment/forecast); the listings carry theirs as `topic`",
      +  "type": "string"
      +}
  5. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.