Skip to main content
Glama

Server Details

TLE MCP — satellite tracking via Two-Line Element sets (tle.ivanstanojevic.me, free, no auth)

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
30.8% over 39 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-tle
GitHub Stars
0
Server Listing
mcp-tle

TDQS

A3.8/5.0

Scored across 34 tools

Disambiguation3/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded are nearly identical routers with subtle differences; polymarket_arbitrage and polymarket_edges both scan for opportunities; entity_profile and compare_entities overlap for multi-entity views. Descriptions do help distinguish them, but boundaries are fuzzy.

Naming Consistency3/5

Most tools use snake_case and follow a verb_noun or noun pattern, but there are deviations: get_tle vs fetch_tle, list_recent vs list_subscriptions, and some tools like ask_pipeworx, bet_research, and entity_profile use noun phrases without clear verbs. Mixed conventions reduce predictability.

Tool Count2/5

With 34 tools, the count is high for a single MCP server. While many serve distinct domains (satellites, memory, AI visibility, dependency scanning), the number feels bloated, especially with three near-identical pipeworx ask variants and multiple monitoring/subscription tools that could be consolidated.

Completeness3/5

The surface covers a wide range of data sources and functions, but there are notable gaps: no explicit tool for listing available data sources or packs despite the router's claim of 1552 sources; no clear delete/update for subscriptions beyond unsubscribe; memory has remember/recall/forget but no update. The domain is too broad to achieve full CRUD lifecycle coverage.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
        -  "company"
        -]New value: +[
        +  "company",
        +  "ticker"
        +]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.