Skip to main content
Glama

Server Details

Free search across ~35,000 agent tools (x402 bazaar + MCP registry) by plain-language need.

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.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 27 tools

Disambiguation4/5

Most tools have clear resource+action identity (token_verdict vs token_whales vs wallet_pnl vs wallet_verdict), and the descriptions explicitly differentiate near-neighbours like x_search vs x_digest vs x_ticker_pulse. A few clusters still blur: x_person vs x_leads_deep (deep lead finder already returns person enrichment), x_profile vs x_person, and token_verdict vs token_verdict_batch vs token_new_launches (which also emits a safety verdict) require reading the descriptions carefully to pick right.

Naming Consistency4/5

All names are snake_case and consistently namespaced by prefix (x_, token_, wallet_), which makes the surface easy to scan. However verb-first names (find_agent_tools, request_agent_tool, send_feedback, translate_text) coexist with noun-first names (token_holders, wallet_pnl, x_digest, credits_balance), so there is no single verb_noun pattern.

Tool Count3/5

27 tools is at the heavy end, and the set mixes the core discovery mission (find_agent_tools, request_agent_tool, agent_market_stats) with ~20 unrelated paid utility endpoints, so the count feels driven by catalog breadth rather than a tightly scoped purpose. Each endpoint is individually justified as a paid x402 offering, but a discovery server carrying this many tangential tools is borderline.

Completeness3/5

Discovery, market stats, build-requests, credits check, and feedback are all covered, but there are notable gaps: no tool to fetch full details/call schema for a specific tool found via search, no way to check the status of a previously requested build, and no credit top-up or call-history/receipts tool. Agents can partly work around these via the returned status URL and external calls, but the lifecycle is not closed.

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources