agentswitchboard

Name: agentswitchboard
Author: assafbar2

Server Details

Search a curated directory of 300+ verified AI agents, MCP servers, and agentic tools.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 37 days
Last Tested: 2026-09-23 02:33
Transport: Streamable HTTP · MCP 2025-11-25
URL
Repository: assafbar2/agentswitchboard.dev
GitHub Stars: 0
Server Listing: agentSwitchBoard

TDQS

A4.2/5.0

Scored 2026-09-18 22:56 across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: search for discovery, get_agent for full details of a specific slug, and list_categories for browse/filter navigation. There is no meaningful overlap between the three.

Naming Consistency5/5

All tool names follow a consistent lowercase verb_noun pattern: get_agent, list_categories, search_agents. The singular/plural usage matches the tool's return semantics, so naming is predictable and clear.

Tool Count5/5

Three tools is a lean but well-scoped set for a read-only directory. Each tool maps to a distinct stage in the discovery workflow—search, browse categories, and retrieve details—with no redundant or filler tools.

Completeness4/5

The core directory workflow is covered: search agents, list categories to browse, and get full agent details. The only minor gap is the lack of an explicit list-all or paginated browsing tool, though search with category filters likely covers most discovery needs.

Available Tools

3 tools

get_agentGet Agent DetailsAInspect

Full detail for one agent by slug: skills, auth, streaming/push support, tags, provider links.

ParametersJSON Schema

Name	Required	Description	Default
`slug`	Yes	Agent slug, e.g. "playwright-mcp"

Output Schema

ParametersJSON Schema

Name	Required	Description
`url`	Yes
`name`	Yes
`slug`	Yes
`tags`	Yes
`skills`	Yes
`addedAt`	No
`agentUrl`	Yes
`authType`	Yes
`provider`	Yes
`verified`	Yes
`categories`	Yes
`description`	Yes
`providerUrl`	Yes
`accessMethods`	Yes
`supportsStreaming`	Yes
`supportsPushNotifications`	Yes

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose the scope (one agent by slug) and enumerates the response content, which is helpful for a read operation. It does not describe behaviors like error handling, exact-match requirements, or data freshness, but these are minor for a simple get tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with the primary purpose front-loaded ('Full detail for one agent by slug') followed by a compact, information-dense list of included fields. No filler, repetition, or unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with an output schema present, the description is largely complete: it states the input requirement and the response contents. The only gap is the absence of explicit routing guidance among sibling tools, which is already accounted for in usage guidelines, so the overall completeness is strong.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the schema already explaining the slug parameter and providing an example. The description adds the phrase 'by slug', which reinforces the parameter's role but does not add substantial new meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the exact action—get full detail for one agent by slug—and lists the specific fields returned (skills, auth, streaming/push support, tags, provider links). This clearly distinguishes it from the sibling tools list_categories and search_agents, which operate over collections rather than a single agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies its use case: when the full detail of a single agent is needed and a slug is available. However, it does not explicitly mention when not to use it or point to alternatives like search_agents for lookup, so the usage guidance is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_categoriesList CategoriesAInspect

All directory categories with live agent counts. Slugs are valid inputs for search_agents.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`categories`	Yes

TDQS

A4.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description carries the full burden. It discloses that counts are live and that slugs are usable, which adds value. However, it does not mention any side effects, error conditions, or whether the operation is read-only, leaving some behavioral aspects undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero filler. The primary purpose is front-loaded, and the usage hint is a single, focused addition. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters and an existing output schema, the description is sufficient for an agent to invoke the tool correctly. It states what is returned (categories with live counts) and how to use the results (slugs for search_agents), leaving no critical gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is nothing to explain beyond the schema. Baseline 4 applies per the rubric since no parameters need semantic elaboration.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: lists all directory categories, with the added detail of live agent counts. This clearly distinguishes it from siblings get_agent (single agent) and search_agents (search operation), so an agent can immediately tell it apart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage by noting that slugs are valid inputs for search_agents, which suggests a workflow: first list categories, then use slugs in searches. It does not explicitly contrast with get_agent, but the purpose is clear enough that an agent would know when to call it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_agentsSearch AgentsAInspect

Search the Agent Switchboard directory of vetted AI agents, MCP servers, and agentic tools. Returns relevance-ranked matches. Filter by category slug and/or access methods.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Max results per page (1–50)
`query`	No	Free-text search (name, description, skills, tags)
`access`	No	Require ALL of these access methods (api, mcp, cli, browser-extension)
`offset`	No	Number of results to skip, for pagination
`category`	No	Category slug, e.g. "code-devtools", "voice-messaging"

Output Schema

ParametersJSON Schema

Name	Required	Description
`limit`	Yes
`total`	Yes	Total matches before paging
`agents`	Yes
`offset`	Yes

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of behavioral context. It discloses meaningful behavior beyond the schema: results are relevance-ranked, the directory is curated ('vetted'), and filters can be combined. It does not explicitly state that the operation is read-only or describe pagination behavior, but 'search' strongly implies a safe read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences front-load the action, resource, and result, then add the filtering capability. There is no redundant restatement of the tool name or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is adequate for a search tool with five optional, fully documented parameters and an output schema. It covers what is searched, what is returned, and the key filtering dimensions, although it does not explicitly mention pagination or route the agent to sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the schema already documents limit, offset, query, access, and category. The description adds a small clarification by saying filters can be applied by category and/or access methods, but it does not add deeper meaning to the remaining parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with the verb 'Search' and names a concrete resource: 'the Agent Switchboard directory of vetted AI agents, MCP servers, and agentic tools.' It also states the result type ('relevance-ranked matches'), which separates it from the sibling tools get_agent and list_categories.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly frames the tool as a directory search rather than a category listing or single-agent fetch, so the broad usage context is evident. It does not explicitly name get_agent or list_categories or state when not to use those alternatives, though the 'search' framing makes the distinction largely inferable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateSep 18, 2026

Changedsearch_agents6 fields changed

addedInput schema / properties / limit / description
```
Added value: +"Max results per page (1–50)"
```

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Number of results to skip, for pagination",
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / limit
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / offset
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / total / description
```
Added value: +"Total matches before paging"
```

changedOutput schema / required

Previous value: -[
-  "total",
-  "agents"
-]New value: +[
+  "total",
+  "offset",
+  "limit",
+  "agents"
+]

3 tool updatesSep 18, 2026

Changedget_agent1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "accessMethods": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "addedAt": {
+      "type": "string"
+    },
+    "agentUrl": {
+      "type": "string"
+    },
+    "authType": {
+      "type": "string"
+    },
+    "categories": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "description": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "providerUrl": {
+      "type": "string"
+    },
+    "skills": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "supportsPushNotifications": {
+      "type": "boolean"
+    },
+    "supportsStreaming": {
+      "type": "boolean"
+    },
+    "tags": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "url": {
+      "type": "string"
+    },
+    "verified": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "name",
+    "slug",
+    "description",
+    "provider",
+    "categories",
+    "accessMethods",
+    "authType",
+    "verified",
+    "url",
+    "agentUrl",
+    "providerUrl",
+    "skills",
+    "tags",
+    "supportsStreaming",
+    "supportsPushNotifications"
+  ],
+  "type": "object"
+}

Changedlist_categories1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "categories": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "agentCount": {
+            "type": "number"
+          },
+          "description": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "categories"
+  ],
+  "type": "object"
+}

Changedsearch_agents1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "agents": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "accessMethods": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "authType": {
+            "type": "string"
+          },
+          "categories": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "description": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "provider": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "verified": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "name",
+          "slug",
+          "description",
+          "provider",
+          "categories",
+          "accessMethods",
+          "authType",
+          "verified",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "agents"
+  ],
+  "type": "object"
+}

3 tool updatesJul 24, 2026
- First observedget_agent
- First observedlist_categories
- First observedsearch_agents

Related MCP Connectors

AgentIndex — Agentic Web Index A
io.github.cengit1
Search 150k+ AI agents and MCP servers. Live liveness probes, behavioral benchmarks, x402 commerce.
Search Agent Orchestration AI & Machine Learning
81
StackResolve C
dev.stackresolve
Find, compare, and audit software for AI agents. Scored registry of tools and MCP servers.
Developer Tools
151
wellknown A
network.wellknown
Live index of AI agents, MCP servers and tools with observed liveness and capability search.
AI & Machine Learning Developer Tools Search
91
Aibooma - AI Agent Registry
com.aibooma
AI agent registry — search, discover, register, and connect agents via MCP.
Agent Orchestration Search Developer Tools
2

Related MCP Servers

beacon-mcp
AI & Machine Learning Developer Tools Search
enrichgateagent-png
A
license
A
quality
A
maintenance
MCP server that searches 3,800+ open-source AI agents by capability, ranked by real traction (stars, activity). Query it from Claude Desktop, Cursor, Cline, or Windsurf.
Updated 2 months ago (2026-07-13 17:16 UTC)
3
30 npm
MIT
MCP Hub Server
Developer Tools Search
AiAgentKarl
A
license
Not graded
quality
D
maintenance
An app store for AI agents. Discover, search, and install 49+ MCP servers from a curated catalog.
Updated 6 months ago (2026-04-03 16:05 UTC)
4 npm
MIT
remoteopenclaw-mcp
Developer Tools Search
aidevelopers2
A
license
A
quality
D
maintenance
Enables AI agents to search a directory of 13,870+ MCP servers, 4,384+ agent skills, and plugins from Remote OpenClaw, returning install commands directly.
Updated 3 months ago (2026-07-02 11:15 UTC)
3
36 npm
6
MIT
Meyhem
Search Agent Orchestration
c5huracan
F
license
Not graded
quality
D
maintenance
Finds the right MCP server for a task from over 1,400 indexed servers ranked by community trust. Also provides outcome-ranked web search for AI agents with no API key or rate limits.
Updated 6 months ago (2026-03-14 17:36 UTC)
4
-

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Server Details

Available Tools

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources