MCPExplorer
Server Details
Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- mcpexplorer/mcp
- GitHub Stars
- 1
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.9/5 across 14 of 14 tools scored. Lowest: 2.9/5.
Each tool targets a distinct aspect of MCP server exploration and management: trust evaluation, comparison, configuration generation, search, loadout planning, etc. There is no overlap in purpose; even similar tools like 'get_capability' and 'search_servers' have clear boundaries (capability-specific vs. free-text search).
All tool names follow a consistent 'verb_noun' pattern using lowercase and underscores. The verbs ('check', 'compare', 'generate', 'get', 'list', 'plan', 'report', 'search') are appropriately descriptive and logically distinguish actions. No mixing of camelCase or other conventions.
With 14 tools, the server covers a comprehensive range of operations for an MCP server registry without being overwhelming. Each tool serves a clear and necessary function, and the count feels well-scoped for the domain.
The toolset covers all major use cases: retrieving server details, comparing servers, checking trust, generating configurations, searching by text or capability, exploring loadouts and ecosystem stats, and reporting issues. There are no obvious gaps for the server's stated purpose.
Available Tools
14 toolscheck_trustCheck trustInspect
Return the explainable trust score, label, scoring reasons, and verification history for an MCP server.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Server slug |
compare_serversCompare two MCP serversInspect
Compare two MCP servers side by side: trust, transport, tools, install, and links.
| Name | Required | Description | Default |
|---|---|---|---|
| a | Yes | First server slug | |
| b | Yes | Second server slug |
generate_runtime_configGenerate MCP setup configInspect
Generate the install + client config for an MCP server in a given runtime (claude-desktop, cursor, vscode, windsurf, cline, continue, goose, openai-agents, langgraph, crewai).
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Server slug | |
| runtime | Yes | Runtime slug, e.g. 'claude-desktop' |
get_alternativesGet alternativesInspect
Find verified MCP servers with the same capabilities as a given server, ranked by trust.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Server slug |
get_capabilityGet a capabilityInspect
List the best MCP servers that provide a capability (e.g. 'send-email', 'web-search'), ranked by trust.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Capability slug, e.g. 'send-email' |
get_ecosystem_statsGet ecosystem statsInspect
Live snapshot of the indexed MCP ecosystem: totals (servers, tools, handshake-verified), provenance and transport breakdowns, and the current top-trust / most-adopted / newest / biggest-trust-riser servers.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_loadoutGet a loadoutInspect
Fetch one curated loadout: its servers (each with role + LIVE trust/transport/tool-risk from the index), an aggregated governance posture for the whole kit, and the plays (see→decide→act sequences) it's designed to run.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Loadout slug, e.g. 'gtm', 'coding', 'research' |
get_serverGet an MCP serverInspect
Fetch the full record for one MCP server by slug: install methods, tools, trust, verification, and provenance.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Server slug, e.g. 'github' |
list_capabilitiesList capabilitiesInspect
List the capability slugs an agent can filter or look up by (e.g. 'send-email', 'query-database'), most-populated first. Use these with get_capability or search_servers' capability filter — the taxonomy isn't guessable.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max capabilities (default 30) |
list_loadoutsList loadoutsInspect
List curated loadouts — deliberately-assembled kits of MCP servers + governance + plays for a specific job (GTM, coding, research, support, infra). The agent-facing version of the /loadouts product. Use get_loadout for the full kit with live trust.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_runtimesList runtimesInspect
List the runtimes generate_runtime_config supports (Claude Desktop, Cursor, VS Code, agent frameworks, …), with each one's config path. Enumerate these instead of guessing runtime slugs.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
plan_toolsetPlan a governed toolsetInspect
Turn a plain-language goal into a recommended, governed toolset: the best-fit curated loadout (matched transparently by goal terms) plus an assembled set of the most relevant indexed servers, each with LIVE trust and tool-risk, and an aggregate governance posture for the kit. The decision layer over search/capability/trust/loadouts.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | Yes | What the agent should do, in plain language, e.g. 'triage support tickets and file bugs'. | |
| limit | No | Max assembled servers (default 6). | |
| risk_tolerance | No | 'read-only' restricts the assembled set to servers with no write/destructive tools — the safe set for an unsupervised agent. Default 'any'. |
report_broken_serverReport a broken serverInspect
Report that an MCP server's install, docs, or endpoint is broken. Creates a submission for editorial review.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Server slug | |
| detail | Yes | What's broken (install fails, endpoint down, docs wrong, …) |
search_serversSearch MCP serversInspect
Search the MCPExplorer index of MCP servers by free text and filters. Omit query to browse the whole index ranked by trust score. Every filter either applies or is echoed back in ignored_filters with a reason — filters never silently do nothing.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 10) | |
| query | No | Free-text query, e.g. 'send email' or 'postgres'. Omit to browse the full index ranked by trust. | |
| transport | No | Filter by transport. Many servers are still 'unknown' (transport not yet probed by the crawler). | |
| capability | No | Filter to servers providing a capability slug, e.g. 'send-email'. An unknown slug is reported in ignored_filters, not silently dropped. | |
| risk_level | No | Filter by tool risk. 'read-only' = has tools and none are write/destructive — the safe set to hand an autonomous agent. | |
| official_status | No | Filter by provenance |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!