F
licenseNot graded
qualityD
maintenanceFinds 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.
4
-
H-Index
Server Details
Capability registry for the agentic economy. Semantic search over verified MCP server listings.
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
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
search_registry1 field changed- changed
Input schema / properties / category / enumPrevious value: -[ - "developer-tools", - "data", - "ai-models", - "infra", - "productivity", - "other" -]New value: +[ + "developer-tools", + "data", + "ai-models", + "infra", + "web", + "security", + "automation", + "productivity", + "communication", + "commerce", + "payments", + "finance", + "marketing", + "other" +]
1 tool update
- Changed
search_registry4 fields changed- added
Input schema / properties / excludeFlagsAdded value: +{ + "description": "Comma-separated flags to exclude across all tiers (drift, vuln).", + "type": "string" +} - added
Input schema / properties / paidAdded value: +{ + "description": "Filter by paid status (comma-list): paid (x402 pay-per-call), gated (account/key), open (free), unknown. Only observed listings carry this; attested read 'unknown'.", + "type": "string" +} - added
Input schema / properties / tagsAdded value: +{ + "description": "Filter by derived domain tags (comma-list, matches any), e.g. crypto,ads,ai.", + "type": "string" +} - added
Input schema / properties / trustAdded value: +{ + "default": "observed_clean", + "description": "Trust tier filter: attested_only (owner-registered only), observed_clean (default: attested plus unflagged observed listings), or observed_any (everything, flags inline). Every result carries a trust label.", + "enum": [ + "attested_only", + "observed_clean", + "observed_any" + ], + "type": "string" +}
3 tool updates
- First observed
get_listing - First observed
list_categories - First observed
search_registry
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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!
Related MCP Connectors
Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
Find, compare, and audit software for AI agents. Scored registry of tools and MCP servers.
- UnifAPIOAuthcom.unifapi
Hosted MCP server for live public-data APIs and Skills for AI agents.
Search and install 4,000+ security-scanned MCP servers from inside any MCP-aware AI client.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceTool search engine for AI agents. One API call to discover the best MCP server for any task. 900+ services indexed with 4-dimensional value ranking.MIT
- AlicenseAqualityAmaintenanceMCP 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.361MIT
mcp-server-mcpindexofficial
AlicenseAqualityBmaintenanceEnables agents to discover, compare, and install other MCP servers using natural language tasks, backed by a searchable index of thousands of servers.6115MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool serves a distinct purpose: get_listing retrieves a specific registry item, list_categories provides taxonomy for filtering, and search_registry performs semantic queries. There is no overlap in their functions, making tool selection straightforward.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case: get_listing, list_categories, search_registry. The naming is predictable and clearly communicates the action and target resource.
Tool Count5/5
With only three tools, the server is tightly scoped for a read-only registry search service. Every tool is necessary and no redundant functionality is present.
Completeness5/5
The tools cover the core operations for a registry index: browsing categories, searching, and retrieving details by ID. There are no obvious dead ends or missing critical features for the stated purpose.