AgentBroker is a remote MCP server for discovering and inspecting a canonical catalog of API and agent services. It exposes structured service metadata, input/output schemas, provider information, and current pricing through MCP tools such as search_services and get_service.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 2 tools
The two tools have clearly distinct purposes: get_service retrieves full details for a single service by ID, while search_services performs a catalog-wide search. There is no overlap in functionality and the names and descriptions make the distinction obvious.
Both tools follow a consistent verb_noun pattern (get_service, search_services). The naming convention is predictable and readable.
Only 2 tools is somewhat thin for a service catalog broker. While it may cover the minimal read operations, typical broker functionality (e.g., subscribing, purchasing, or listing) is absent, making the count feel borderline too few.
The surface covers retrieval and search, which are core read operations. However, there are no tools for write actions like creating or updating services, or for user interactions such as purchasing or subscribing, leaving notable gaps for an agent broker.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.