SearchStack
Server Details
Agent-driven search: build, import, tune, search, and score result quality — all over MCP.
- Status
- Unhealthy
- OAuth
- Works in Glama
- 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
feed_connect3 fields changed- added
Input schema / properties / request / properties / media_excludesAdded value: +{ + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] +} - added
Input schema / properties / request / properties / media_prefixAdded value: +{ + "type": [ + "string", + "null" + ] +} - added
Input schema / properties / request / properties / media_typesAdded value: +{ + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] +}
16 tool updates
- Added
api_key_create_read_only - Added
feed_connect - Added
feed_discover - Added
feed_edit_interval - Added
feed_edit_web_scope - Added
feed_get - Added
search_result_get - Added
search_result_import - Added
search_result_import_from_media - Added
search_result_list - Added
search_result_list_post - Added
webhook_create - Added
webhook_delete - Added
webhook_edit - Added
webhook_event_list - Added
webhook_test
3 tool updates
- Added
feed_list - Added
feed_sync_now - Added
search_result_delete_by_ids
3 tool updates
- Changed
bulk_insert1 field changed- added
Input schema / properties / idempotencyKeyAdded value: +{ + "default": null, + "description": "Optional idempotency key. Reuse the same value across retries of one logical bulk insert so a network blip replays the original write instead of duplicating every record. Omit to auto-generate one per call.", + "type": [ + "string", + "null" + ] +}
- Changed
bulk_insert_with_fields1 field changed- added
Input schema / properties / idempotencyKeyAdded value: +{ + "default": null, + "description": "Optional idempotency key. Reuse the same value across retries of one logical bulk insert so a network blip replays the original write instead of duplicating every record. Omit to auto-generate one per call.", + "type": [ + "string", + "null" + ] +}
- Changed
search_result_create1 field changed- added
Input schema / properties / idempotencyKeyAdded value: +{ + "default": null, + "description": "Optional idempotency key. Reuse the same value across retries of one logical create so a network blip replays the original write instead of duplicating it. Omit to auto-generate one per call.", + "type": [ + "string", + "null" + ] +}
88 tool updates
- First observed
account_get - First observed
account_get_name - First observed
analytics_get_group - First observed
analytics_get_list - First observed
bulk_insert - First observed
bulk_insert_with_fields - First observed
contributors_create - First observed
contributors_delete - First observed
coordinates_create - First observed
coordinates_delete - First observed
eval_run - First observed
eval_run_history - First observed
eval_run_status - First observed
eval_set_bootstrap - First observed
eval_set_create - First observed
eval_set_delete - First observed
eval_set_list - First observed
eval_set_view - First observed
extract_document_text - First observed
facet_create - First observed
facet_remove - First observed
facet_rename - First observed
facet_values - First observed
get_api_catalog - First observed
get_api_info - First observed
get_examples - First observed
group_add_ip_address - First observed
group_add_list - First observed
group_bump_version - First observed
group_clone - First observed
group_create - First observed
group_delete - First observed
group_edit - First observed
group_get - First observed
group_get_version_members - First observed
group_get_versions - First observed
group_remove_ip_address - First observed
group_remove_list - First observed
group_remove_model - First observed
group_remove_reranker - First observed
group_restore_version - First observed
group_search - First observed
group_search_post - First observed
group_set_model - First observed
group_set_reranker - First observed
group_suggest - First observed
group_suggest_post - First observed
group_transfer - First observed
judge_create - First observed
judge_delete - First observed
judge_list - First observed
judge_run - First observed
judge_run_status - First observed
judge_try - First observed
judge_view - First observed
list_create - First observed
list_delete - First observed
list_edit - First observed
list_get - First observed
list_restore_version - First observed
media_store_delete_media - First observed
record_group_click - First observed
record_list_click - First observed
related - First observed
related_post - First observed
resource_create - First observed
resource_remove - First observed
resource_rename - First observed
search_by_image - First observed
search_by_image_base64_post - First observed
search_by_image_post - First observed
search_group_by_image - First observed
search_group_by_image_base64 - First observed
search_group_by_image_base64_post - First observed
search_group_by_image_post - First observed
search_list - First observed
search_list_post - First observed
search_result_create - First observed
search_result_delete - First observed
search_result_delete_by_filter - First observed
search_result_edit - First observed
search_result_edit_vector - First observed
search_result_soft_delete_by_filter - First observed
searchable_create - First observed
searchable_remove - First observed
searchable_rename - First observed
suggest - First observed
suggest_post
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
Agentic search over your Dewey document collections from any MCP-compatible client.
Make your knowledge agent-ready. One MCP endpoint, 5 connectors, 3 search modes.
Multi-engine search for AI agents. Trust scoring, local corpus, MCP-native. Self-hostable, BYOK.
Search engine for AI agents to find MCP servers, A2A agents, and skills on their own.
Related MCP Servers
- AlicenseAqualityBmaintenanceConfig-driven MCP server for cross-domain full-text search across agent session logs, meeting transcripts, and notification files.71MIT
- AlicenseAqualityBmaintenanceConfig-driven MCP server for cross-domain full-text search across agent session logs, meeting transcripts, and notification files.7MIT
- AlicenseAqualityBmaintenanceProvides managed Apache Solr search as MCP tools, enabling hybrid retrieval, server-side GPU embeddings, document indexing, and grounded RAG answers without managing infrastructure.389MIT
- AlicenseAqualityCmaintenanceProvides agent-friendly web search via MCP with zero-config free engines, region-aware failover, freshness filtering, and a one-call research tool that searches, fetches, and summarizes pages.34842MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
Each tool targets a distinct resource-action pair with clear prefixes (account, analytics, api_key, etc.). Even similar tools (e.g., search_by_image vs search_by_image_base64) are distinguished by modality. No two tools appear to do the same thing.
All tool names follow a consistent snake_case noun_verb pattern (e.g., account_get, contributors_create, eval_run_status). POST variants are consistently suffixed with _post. The naming is highly systematic and predictable.
With 107 tools, this server is far beyond the typical 3-15 range. While the domain is broad, the number is excessive for an MCP server, making it hard for agents to navigate. Score 1 per calibration (50+ tools is extreme mismatch).
The server covers a comprehensive set of operations for a search platform: account, analytics, API keys, bulk operations, contributors, coordinates, evaluation, facets, feeds, groups, judges, lists, media, resources, searchable fields, search results, and webhooks. CRUD and lifecycle operations are present for most resources. No obvious gaps.