CDS SIMBAD — astronomical object database (~14M objects) via TAP/script
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
bet_research1 field changedInput schema / properties / include_rawAdded value: +{
+ "description": "Default false. When false (recommended), FRED/FDA/GDELT/Federal-Register evidence is summarized to the few fields agents actually use — keeps responses under ~20KB. Pass true to get full upstream payloads (50KB-500KB) when you need to recompute deltas, cite specific observations, or post-process.",
+ "type": "boolean"
+}ai_visibility_check4 fields changedInput schema / properties / _apiKeyAdded value: +{
+ "description": "Optional Anthropic API key (sk-ant-...) — only needed if \"anthropic\" is in models. Passed straight through to api.anthropic.com.",
+ "type": "string"
+}Input schema / properties / context / descriptionPrevious value: -"Optional: a phrase locating the entity (e.g. \"Boston restaurant\", \"B2B SaaS\", \"Polish painter\"). Helps disambiguate common names."New value: +"Optional: a phrase locating the entity (e.g. \"Boston restaurant\", \"B2B SaaS\"). Helps disambiguate common names."Input schema / properties / entity / descriptionPrevious value: -"The thing to ask about. Brand/business name, product name, person, or topic. E.g. \"Pipeworx\", \"OpenInvoice\", \"Acme Corp pricing\", \"the company behind ChatGPT\"."New value: +"The thing to ask about. Brand/business name, product name, person, or topic. E.g. \"Pipeworx\", \"OpenInvoice\", \"Acme Corp pricing\"."Input schema / properties / modelsAdded value: +{
+ "description": "Which models to probe. Supported: \"workers-ai\" (free default), \"anthropic\" (requires _apiKey). Omit for just workers-ai.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}scan_competitor_ai_presenceai_visibility_checkgenerate_llms_txtpipeworx_trendingpolymarket_kalshi_spreadask_pipeworxbet_researchcompare_entitiescone_searchdiscover_toolsentity_profileforgetobjectpipeworx_feedbackpolymarket_arbitragepolymarket_edgesrecallrecent_changesrememberresolve_entityscripttapvalidate_claimClaiming 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 as io.github.acme/server also 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.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!
CDS VizieR — astronomical catalogue server (tens of thousands of catalogues)
MAST (Mikulski Archive for Space Telescopes) — Hubble/JWST/Kepler/TESS
NASA JPL Horizons — solar-system body ephemerides
Add one secure layer between your agents and this server.
Most tools have distinct purposes, with detailed descriptions. Minor overlap exists between ai_visibility_check and scan_competitor_ai_presence, and among company-related tools like entity_profile, compare_entities, and recent_changes, but descriptions clarify usage.
Tool names use mixed conventions: snake_case (ai_visibility_check, ask_pipeworx), compound words (cone_search, discover_tools), and inconsistent patterns (pipeworx_feedback vs. generate_llms_txt). No consistent verb_noun pattern.
23 tools is high but not extreme. The server aggregates multiple domains (SIMBAD, Pipeworx, Polymarket, memory), making the count borderline. It could benefit from splitting into separate servers for clarity.
The tool set covers astronomy, data queries, betting, memory, and AI visibility. However, it lacks update/delete for entities and direct pack-level tools (though discover_tools helps). Completeness varies by subdomain.