MCP Marketplace
Server Details
Search and install 4,000+ security-scanned MCP servers from inside any MCP-aware AI client.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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 4.3/5 across 3 of 3 tools scored.
Each tool has a clearly distinct purpose: get_server retrieves detailed information for a single server, list_categories provides category metadata, and search_servers performs catalog searches. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern (get_server, list_categories, search_servers) with clear, descriptive verbs and nouns. The naming is uniform and predictable across the set.
Three tools are appropriate for a marketplace server, covering core operations like browsing, searching, and inspecting. It is slightly lean but reasonable, as it handles essential workflows without unnecessary complexity.
The tools provide a complete surface for marketplace interactions: browsing categories, searching servers, and fetching detailed server information. Minor gaps might include actions like user reviews or installation management, but core functionality is well-covered.
Available Tools
7 toolscompareInspect
Compare 2-5 MCP servers side by side on the fields users actually decide on: security score, critical findings, pricing, transport mode, tool count, and install command availability. Use when a user is choosing between candidates from a search. Returns a structured comparison table plus a short per-field summary, so the agent can surface the important contrasts without a second pass over each server.
| Name | Required | Description | Default |
|---|---|---|---|
| slugs | Yes | Array of 2-5 server slugs to compare. |
creator_profileInspect
List all MCP servers by a single creator, plus aggregate trust signals. Use to evaluate a publisher holistically: 'do they ship consistently?', 'what's their security track record?', 'are there other servers by the same author?'. Match is case-insensitive on display name. Returns aggregate stats (total servers, avg security score, grade distribution, critical-finding count) plus the per-server list.
| Name | Required | Description | Default |
|---|---|---|---|
| creator | Yes | Creator display name (case-insensitive) OR GitHub username. From a search_servers result, use the `creator` field. |
get_serverInspect
Fetch full details for a single MCP server by its slug. Returns description, install commands, security score/risk/findings, ratings, creator info, setup requirements (API keys/credentials the user will need), and the list of MCP tools the server exposes. The security.critical_findings array lists every severity=critical|high issue — you MUST show these to the user before recommending they install. Use this as the last step before any install recommendation.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Server slug (from search_servers results or the URL: mcp-marketplace.io/server/{slug}). |
list_categoriesInspect
List all MCP Marketplace categories with slug, name, description, and approved server count. Use the returned slug as the category filter in search_servers.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
recently_addedInspect
List the most recently added MCP servers. Use for discovery: 'what's new', 'latest servers', 'servers from this week'. Optionally constrain to the last N days. Ordered by creation date descending. Each result carries the same security/risk/pricing fields as search_servers.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Only include servers created within the last N days (1-365). Omit for no date bound. | |
| limit | No | Max servers to return (1-25). Default 10. | |
| free_only | No | If true, exclude paid servers. |
search_serversInspect
Search the MCP Marketplace catalog. With a free-text query and default sort, results are ranked by semantic similarity (gte-small embeddings + cosine similarity), so natural-language queries like 'manage my calendar', 'something to read PDFs', or 'database for my agent' work as well as keyword searches. Each result includes security_score (0-10), risk_level (low/moderate/high/critical), critical_findings (count of severity=critical|high findings), pricing, rating, install count, and a URL. ranking_mode in the response indicates whether semantic or keyword matching was used. Before recommending an install, call get_server for full details including every flagged finding — critical_findings > 0 means the server has known security issues you must surface to the user.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-indexed page number. Combine with `limit` to paginate past the first window. Defaults to 1. | |
| sort | No | Ranking order. Defaults to 'relevance' when query is set, else 'installs'. | |
| limit | No | Max results per page (1-25). Default 10. | |
| query | No | Free-text search across name, tagline, description, tags, and MCP tool names. | |
| category | No | Category slug filter. Call list_categories to see valid slugs. | |
| free_only | No | If true, exclude paid servers. | |
| transport | No | Filter by transport. 'stdio' = local (npm/pip); 'streamable-http' = hosted remote. SSE is not exposed because the catalog doesn't distinguish SSE from streamable-HTTP and filtering on it would always return zero. |
similar_toInspect
Find MCP servers that are semantically similar to a reference server. Use when a user picked a candidate but wants alternatives — e.g. 'like this but safer', 'like this but free', 'what else does this'. Reuses the catalog's gte-small embeddings: the reference server's embedding is the query vector. Returns servers sorted by cosine similarity (highest first), excluding the reference itself. Each result carries the same security/risk/pricing fields as search_servers so callers can immediately compare on security_score, has_critical_findings, and pricing.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Reference server slug (the one you want similar alternatives to). | |
| limit | No | Max similar servers to return (1-10). Default 5. | |
| free_only | No | If true, exclude paid servers from the comparison set. |
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!