AI product expert answering from live source code, with sources and a verification status.
Score is being calculated. Check back soon.
ask_product_expertAsk the product expertInspectAsk a question about "deployit" and get an answer verified against its live source code and git history. Use it for anything about product behavior, features, settings, limits, error messages, or recent changes.
HOW IT WORKS AND HOW LONG IT TAKES: the expert genuinely investigates — it searches and reads the product's real source code before answering. A fresh investigation takes 20-60 SECONDS. Do not give up early, and if a human is waiting, tell them the verified answer may take up to a minute. Repeated questions asked without context are served from cache in under a second; the cache resets whenever the product's code changes.
IF IT TIMES OUT: you get an error saying the expert could not finish in time. The investigation KEEPS RUNNING in the background — re-ask the IDENTICAL question (same wording, no context) about a minute later and the finished answer is served instantly from cache. Retry with the same words; rephrasing restarts the investigation.
READING THE ANSWER: it ends with a Sources block (the files and commits actually consulted) and a Verification status carrying both confidence and polarity:
verified: confirmed in the code — safe to relay.
backend_only: the capability exists server-side but has no visible UI path.
not_found: searched, and it does NOT exist — a factual "no", relayable as such.
unknown: the expert could not conclude — do NOT relay as fact; consider retrying with depth "thorough".
LIMITS: strictly read-only — it can never change anything. Some topics may be refused by the project's policy. A monthly question quota may apply (the error message says so when reached; cached answers never count). At most 60 requests per minute per access key.
| Name | Required | Description | Default |
|---|---|---|---|
| depth | No | quick (default): up to ~1 minute of investigation, right for support questions. thorough: digs much deeper for hard questions — expect the timeout-then-retry-from-cache flow. | |
| context | No | Optional context from your own conversation with the end user (symptoms, plan, what they tried…). Makes the answer more targeted, but context-carrying questions are never cached — omit it for generic questions. | |
| question | Yes | The question about the product, as specific as possible. Identical wording hits the cache — when retrying after a timeout, repeat the question verbatim. |
get_recent_changesRecent product changesInspectInstant list of recent changes to "deployit" — the semantic changelog derived from its commits. No AI processing: responds in under a second, costs nothing, and never counts against any quota. Use this FIRST for "what changed", "what's new", "since when" questions; escalate to ask_product_expert only when you need an investigated answer.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | How many days back (default 14, max 90). |
server_infoServer infoInspectDescribe this MCP server: which product it answers for, which repositories back it, and how fresh the underlying code index is. Instant (no AI). Call it once at the start of a session to confirm you are talking to the right product — if the index is stale or still building, say so instead of trusting deep answers.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
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 or an account that owns the GitHub organization, then choose Claim with GitHub.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on 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.
No comments yet. Be the first to start the discussion!
Independent fact-checking for AI answers: a verdict and sources for every claim.
Ask a business's official customer support and get their verified answer, with sources.
Verify live product price, currency, stock, variants and published shipping evidence for AI agents.
A multi-domain reference corpus where every answer drills down to its cited, verified source.
