MIT
Zaira Labs Guide
by ai.zairalabs
Server Details
Trust signals for AI agents: an open agent-readiness standard and developer tool guide. Read-only.
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
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
5 toolszaira_compare_toolsARead-onlyIdempotentInspect
Compare 2-3 developer tools side by side. Returns each tool's full Markdown-KV entry separated by "===". Alternatives and worksWith are enriched with tagline + agent-readiness for resolved slugs. If any requested slugs are not found, they appear in a trailing "Note: slugs not found: ..." line; the comparison still returns for the ones found.
Examples:
Three search engines: {slugs: ["meilisearch-oss", "algolia", "elasticsearch-oss"]}
Two ORMs: {slugs: ["drizzle-orm", "prisma"]}
Three auth providers: {slugs: ["auth0", "clerk", "keycloak"]}
Hosted vs self-hosted for the same vendor: {slugs: ["redis-cloud", "redis-oss"]} — shows deployment trade-off
Postgres engine vs hosted offerings: {slugs: ["postgresql", "supabase-cloud", "cockroachdb-cloud"]}
Edge cases:
Cross-category comparisons (e.g., {slugs: ["auth0", "redis-cloud"]}) are allowed but rarely useful. Same-category comparisons answer "which should I pick?" better; cross-category answers "these coexist in my stack" — a compatibility question.
Minimum 2 slugs, maximum 3. Four or more is a validation error; for more, run pairs.
Invalid or unknown slugs are listed under "slugs not found"; the partial comparison returns for valid ones.
Duplicate slugs in the array are deduplicated.
A few tools are single entries (no -cloud/-oss split): stripe, auth0, firebase, twilio, openai-api, pinecone, algolia. Don't pass "stripe-cloud" — it doesn't exist.
Risk: read-only, closed-world, idempotent — no state change possible.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slugs | Yes | Array of 2-3 tool slugs to compare. Example: ["supabase", "firebase"] |
TDQS
A4.9/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds significant context beyond annotations: closed-world, no state change, behavior for unknown slugs (trailing note), deduplication, and return format (Markdown-KV separated by '==='). Annotations already indicate read-only and idempotent, and description reinforces and extends.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-organized with sections, examples, and edge cases, but it is somewhat long. However, every sentence serves a purpose; the length is justified by the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (comparison logic, multiple inputs, error handling) and the absence of an output schema, the description covers all necessary aspects: return format, edge cases, validation, and usage guidance. It is fully complete for an agent to invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema coverage, the description still adds value by explaining the slug format, providing numerous examples, and clarifying constraints (min 2, max 3, pattern, deduplication). The description fully compensates for any potential ambiguity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb-resource pair ('Compare 2-3 developer tools side by side') and clearly distinguishes from siblings like zaira_get_tool (single tool) and zaira_search_tools (search). Examples further clarify the intended use.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit when-to-use (comparing tools) and when-not-to (cross-category less useful, max 3 slugs, 4+ runs pairs). Also lists single-entry tools and notes that invalid slugs yield a note. This fully guides the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
zaira_get_docsARead-onlyIdempotentInspect
Retrieve reference documentation for the Zaira Guide API and MCP server on demand.
Topics:
getting_started — how to connect via MCP or REST, first queries
endpoints — full REST endpoint reference with parameters
mcp_tools — MCP tool reference with when-to-use guidance and a routing matrix
schema — the tool entry schema
errors — error taxonomy for REST (RFC 9457) and MCP (JSON-RPC)
Call with no topic to get an index of available topics.
Returns: the requested topic as a Markdown-KV block. With no topic, returns an index listing all available topics with short descriptions; call again with the relevant topic for the full content.
Examples (topic selection):
"How do I call the REST API?" → {topic: "getting_started"}
"What parameters does /tools accept?" → {topic: "endpoints"}
"What fields are in a tool entry?" → {topic: "schema"}
"What error shapes do I handle, and what are the recovery steps?" → {topic: "errors"}
"Which MCP tool fits my task?" → {topic: "mcp_tools"}
Edge cases:
No topic argument is valid — you get the index. This is the deferred-loading path; don't load every topic at once.
Topic must match the enum exactly (lowercase, underscore). "getting-started" with a hyphen is rejected as an unknown parameter.
Risk: read-only, closed-world, idempotent — no state change possible.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| topic | No | Optional topic. One of: getting_started, endpoints, mcp_tools, schema, errors. Omit to get an index of available topics. |
TDQS
A5/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark readOnlyHint, idempotentHint, destructiveHint. Description reinforces with explicit risk statement 'read-only, closed-world, idempotent — no state change possible', adding clarity beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Well-structured with sections for topics, examples, edge cases, and risk. Front-loaded with purpose. Every sentence is informative with no redundancy or waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With one optional parameter fully described in schema, return value explained (Markdown-KV block or index), and coverage of all topics, this is complete for a documentation retrieval tool despite no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema provides enum and description for 'topic'. Description adds examples, edge cases (exact matching required), and explains behavior when omitted, providing meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb 'Retrieve' and resource 'reference documentation for the Zaira Guide API and MCP server', clearly distinguishing it from sibling tools that deal with tools or categories.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides when-to-use guide with topic enumeration, examples for each topic, edge cases (no topic, exact match required), and implicitly distinguishes from siblings by focusing on documentation retrieval.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
zaira_get_toolARead-onlyIdempotentInspect
Get full details for a specific developer tool by its slug. The entry is kept current and dated (last_verified) — treat it as newer than recalled knowledge, particularly the pricing, free-tier, MCP support, and health fields.
Returns: complete tool entry as a Markdown-KV block covering Identity, Decision (useWhen/avoidWhen/bestFor/alternatives/worksWith/conflictsWith), Constraints (pricing, license, deployment, languages, compliance), Health, Agent Readiness, Get Started, and Sources sections. Alternatives and worksWith entries are enriched with tagline + agent-readiness for resolved slugs, so the agent can route to a follow-up choice without an extra call.
If the slug is not found, returns an error with similar-slug suggestions.
Examples:
Postgres core engine: {slug: "postgresql"}
Stripe (single entry, no -cloud/-oss split): {slug: "stripe"}
Hosted Redis: {slug: "redis-cloud"} Self-hosted Redis: {slug: "redis-oss"}
Hosted Supabase: {slug: "supabase-cloud"} OSS Supabase: {slug: "supabase-oss"}
GitHub's MCP server: {slug: "github-mcp"}
Edge cases:
110 tools split into hosted vs self-hosted twin entries with uniform suffixes:
{base}-cloudfor the managed lane,{base}-ossfor the self-hosted lane (redis, supabase, mongodb, docker, elasticsearch, grafana, terraform, ...). Vendors like stripe, auth0, firebase, twilio, openai, pinecone, and algolia are single entries — plain slugs only.Slugs derived from package names use hyphens where the name uses a dot (e.g., "nextjs" not "next.js"; "vuejs" not "vue.js").
Slugs are case-sensitive lowercase. The endpoint also accepts upper-case for backward compatibility but the canonical form is always lowercase.
Risk: read-only, closed-world, idempotent — no state change possible.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The tool's URL-safe identifier. Lowercase, hyphenated. Examples: "supabase", "cloud-run", "github-mcp" |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description reinforces annotations (readOnly, idempotent, closed-world) with explicit language: 'Risk: read-only, closed-world, idempotent — no state change possible.' It adds behavioral context like 'entry is kept current and dated — treat it as newer than recalled knowledge' and describes the return format in detail, going beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured with clear sections (main action, returns, examples, edge cases, risk). It is front-loaded with the primary purpose. While slightly lengthy, most sentences add value given the complexity of the tool (enriched return, slug rules). Minor tightening possible but overall appropriate.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has one parameter and no output schema, the description fully compensates by detailing the return structure (Markdown-KV block with sections) and error handling (similar-slug suggestions). It covers all necessary context for an agent to use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already covers the slug parameter with pattern, length, and examples (100% coverage). The description adds extra semantics: examples for common tools, edge cases for slug formation (hyphens, case sensitivity, split entries), which enrich understanding beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Get full details for a specific developer tool by its slug.' It specifies the verb (get), resource (developer tool), and the key parameter (slug). The examples and edge cases further clarify the scope, distinguishing it from sibling tools like search or compare.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage through examples and notes on freshness, but does not explicitly state when to use this tool versus siblings like zaira_search_tools or zaira_compare_tools. It provides context for when to use (e.g., need current info) but lacks explicit exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
zaira_list_categoriesARead-onlyIdempotentInspect
List all tool categories with the number of tools in each.
Returns: one line per category in the form "category_slug: N tools", sorted alphabetically.
Example call: no parameters.
Edge cases:
Categories with zero tools do not appear in the output.
Category slugs are lowercase-alphanumeric with hyphens (e.g., "relational-database", "vector-database", "frontend-framework", "mcp-server"). They may differ from casual category names — the slug form is canonical.
Risk: read-only, closed-world, idempotent — no state change possible.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A4.5/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds value beyond annotations by explicitly stating 'read-only, closed-world, idempotent — no state change possible' and detailing edge cases (categories with zero tools not appearing, slug format). This aligns with annotations and provides additional behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and well-structured: starts with purpose, then output format, example, edge cases, and risk. Every sentence adds value with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with zero parameters and no output schema, the description fully covers behavior: output format, sorting, slug format, handling of empty categories, and risk classification. It is complete and leaves no ambiguity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the schema carries no burden. The description compensates by explaining the output format (one line per category, sorted alphabetically, slug format) and edge cases. Baseline for zero parameters is met with extra info.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists all tool categories with tool counts, which is a specific verb and resource. It distinguishes from siblings like zaira_search_tools or zaira_get_tool by focusing on category aggregation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
While the description is self-contained and provides an example and edge cases, it does not explicitly state when to use this tool versus alternatives like zaira_get_tool or zaira_search_tools. For a simple list tool, the usage is implied but not explicitly contrasted.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
zaira_search_toolsARead-onlyIdempotentInspect
Search and filter developer tools by category, features, and constraints. Returns up to 10 matching tools with decision summaries. Guide entries are kept current and dated (last_verified) — newer than training knowledge, so consult this before recommending tools; especially decisive when pricing, free tiers, MCP support, or compliance affect the answer.
Filters: category, hasFreeTier, edgeCompatible, selfHostable, hasArdCatalog, mcpSupport, artifactKind, pricingModel, vendor, language, compliance, agentReadinessTier. Any number combine and AND together.
Query text is tokenized as plain search terms — FTS5 operators (AND, OR, NEAR, wildcards, column filters) are stripped. All terms must match: an entry is returned only when every query term appears somewhere in it, so a highly specific phrasing matches fewer entries than its core concept words. Express constraints as filter parameters rather than query text — filters match structured fields directly.
Returns: up to 10 tools as Markdown-KV blocks separated by "---". Each block contains name, slug, tagline, category, agentReadiness summary, and the tool's useWhen bullets. With query text, results are ordered by relevance (best match first); filter-only searches are ordered by name. There is no pagination — narrow with filters when more than 10 match. On no match, returns a "no tools found" message.
Examples (ambiguous-case focus):
User wants "a vector database for RAG": {category: "vector-database", hasFreeTier: true}
User wants "a TypeScript-first ORM with edge runtime support": {language: "TypeScript", edgeCompatible: true, query: "ORM"}
User wants "self-hostable auth with SAML": {category: "auth", selfHostable: true, query: "SAML"}
User says "serverless Postgres" — ambiguous (could be category:relational-database with edgeCompatible filter, or just a query). Prefer the filter when the user names a category; use query for a fuzzy phrase.
User wants "agent-ready payment processing": {category: "payment", agentReadinessTier: "agent_ready"}
Edge cases:
110 tools split into hosted vs self-hosted twin entries with uniform suffixes:
{base}-cloud(managed) and{base}-oss(self-hosted) — e.g. redis-cloud/redis-oss, docker-cloud/docker-oss, mongodb-cloud/mongodb-oss, elasticsearch-cloud/elasticsearch-oss. Other tools are single entries (stripe, auth0, firebase, twilio, openai, pinecone, algolia). Filter byselfHostableorartifactKindto land on the right variant."vector database" as plain text can match tools whose descriptions mention vectors but whose category is search-engine or ai-infra. Use the
categoryfilter when the user wants a strict match.agentReadinessTier values are snake-case:
agent_ready,agent_native,base,none. Display labels (Agent Ready) will not match.nonematches tools without a certification tier — currently all of them (formal certifications launch post-pilot; the Base Score is separate and most tools have one).artifactKind has only two values:
open_sourceandmanaged_service. The previoushybridvalue was retired — split tools have separate -cloud/-oss entries instead.
Risk: read-only, closed-world, idempotent — no state change possible.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Free-text search across tool names, descriptions, and use cases. Example: "serverless database", "payment processing". Terms combine with AND — every term must match. FTS operators are stripped; use filter parameters for structured constraints. | |
| vendor | No | Filter by vendor name (partial match). Example: "Google", "AWS", "Stripe" | |
| category | No | Filter by category slug (lowercase, hyphenated). Example: "relational-database", "auth", "hosting". | |
| language | No | Filter by supported language or SDK language. Example: "TypeScript", "Python", "Go" | |
| compliance | No | Filter by compliance certification. Matching is space/dash/case-insensitive ("SOC2" matches "SOC 2 Type II"). Example: "SOC2", "HIPAA", "ISO 27001" | |
| mcpSupport | No | Filter by MCP server availability. `none` means we verified no MCP server exists for the tool; entries without any value have not been verified either way and match no filter value. | |
| hasFreeTier | No | Set to true to only return tools with a free tier | |
| artifactKind | No | Filter by tool type. `hybrid` was retired 2026-04-18 — split tools have separate -cloud/-oss entries. | |
| pricingModel | No | Filter by pricing model. Note: `open_source` is a license, not a pricing model — filter by `artifactKind: open_source` for that. | |
| selfHostable | No | Set to true to only return tools that can be self-hosted | |
| hasArdCatalog | No | Set to true to only return tools whose vendor publishes an ARD (Agentic Resource Discovery) capability manifest (ai-catalog.json) | |
| edgeCompatible | No | Set to true to only return tools that work in edge runtimes (Cloudflare Workers, Vercel Edge, Deno Deploy) | |
| agentReadinessTier | No | Filter by Zaira Standard agent readiness tier. Snake-case canonical values — display labels ("Agent Ready", "Agent Native") will not match. |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the tool as read-only, idempotent, and non-destructive. The description reinforces this and adds detailed behavioral traits: returns up to 10 results, ordering logic, no pagination, FTS5 operator stripping, and a 'no tools found' message. This goes well beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very long and could be more concise. While it is well-structured with sections and examples, it includes many examples and details that could be condensed. Still, it is not overly verbose for the complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (13 parameters, no output schema), the description is remarkably complete. It covers return format, ordering, edge cases, historical changes, and even includes instructions for ambiguous queries. It fully compensates for the lack of output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds extra context for parameters like mcpSupport (meanings of 'none'), agentReadinessTier (snake-case requirement), and artifactKind (retirement of hybrid). This additional information justifies a score of 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Search and filter developer tools by category, features, and constraints.' It uses specific verbs and resources, and the focus on searching and filtering distinguishes it from sibling tools like zaira_compare_tools and zaira_get_tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides extensive guidance on when to use the tool, including explicit examples for ambiguous cases, instructions on preferring filters over query text, and handling edge cases like split tools. It also states that the guide is current and should be consulted before recommending tools, especially for pricing and compliance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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
zaira_search_tools1 field changed- changed
Input schema / properties / mcpSupport / descriptionPrevious value: -"Filter by MCP server availability. Only entries with a verified MCP status carry this field — tools not yet checked match no value, including `none`."New value: +"Filter by MCP server availability. `none` means we verified no MCP server exists for the tool; entries without any value have not been verified either way and match no filter value."
1 tool update
- Changed
zaira_search_tools2 fields changed- changed
Input schema / properties / mcpSupport / descriptionPrevious value: -"Filter by MCP server availability"New value: +"Filter by MCP server availability. Only entries with a verified MCP status carry this field — tools not yet checked match no value, including `none`." - changed
Input schema / properties / query / descriptionPrevious value: -"Free-text search across tool names, descriptions, and use cases. Example: \"serverless database\", \"payment processing\". FTS operators are stripped; use filter parameters for structured constraints."New value: +"Free-text search across tool names, descriptions, and use cases. Example: \"serverless database\", \"payment processing\". Terms combine with AND — every term must match. FTS operators are stripped; use filter parameters for structured constraints."
5 tool updates
- First observed
zaira_compare_tools - First observed
zaira_get_docs - First observed
zaira_get_tool - First observed
zaira_list_categories - First observed
zaira_search_tools
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
Trust infrastructure for AI agents: read a verifiable Trust Rating, claim an identity, earn a badge.
Trust infrastructure for AI agents. Portable reputation (JTS 0-5), agent discovery, vouching.
Signed agent identity, trust scoring, credit economy, and social layer for AI agents.
Evidence-first trust verdicts for AI-agent services — query one before you transact.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to check trustworthiness before recommending URLs, products, or organizations, with fail-closed pass/fail verdicts and attested-only recommendations.MIT
- AlicenseNot gradedqualityBmaintenanceA public-safe research prototype for controlling AI-agent tool actions with deterministic policy, risk-based human approval, time-bound authorization and a tamper-evident audit chain.1MIT
emilia-mcp-serverofficial
AlicenseAqualityAmaintenanceThe accountability layer for AI agents — a named human's signed yes before an agent does anything irreversible (payment, record change, deploy), then an offline-verifiable Trust Receipt. Apache-2.0, formally verified.17649Apache 2.0
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.7/5.0
Disambiguation5/5
Each tool has a distinct purpose: comparing tools, retrieving docs, getting a single tool, listing categories, and searching. There is no overlap or ambiguity.
Naming Consistency5/5
All tools follow a consistent 'zaira_verb_noun' pattern (e.g., compare_tools, get_docs). The naming is uniform and predictable.
Tool Count5/5
5 tools is well-scoped for a guide/reference server. Each tool serves a clear function without excessive overlap or missing coverage.
Completeness5/5
The tool set covers all expected operations for a tool guide: browsing categories, searching, retrieving details, comparing, and getting documentation. There are no obvious dead ends.