Skip to main content
Glama

Server Details

Taiwan's statutory company register: every incorporated company, its 統一編號, capital, registered…

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
0.3% over 16 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-taiwan-companies
GitHub Stars
0
Server Listing
taiwan-companies

TDQS

A3.7/5.0

Scored across 39 tools

Disambiguation2/5

The server is named 'Taiwan Companies' yet only three tools (twcompany_by_ban, twcompany_search_name, twcompany_status) relate to that domain — the other ~36 are a general Pipeworx data gateway, so the set's purpose is unclear. Within the gateway there is heavy overlap: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions, validate_claim, entity_profile and compare_entities all answer 'look something up' with fuzzy boundaries. The Polymarket family (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread, bet_research, release_calendar_markets, kalshi_weather_edge) is described at length but still overlaps on 'find me an edge'.

Naming Consistency3/5

Nearly all names are snake_case, which is good, but the conventions inside them are mixed: some are verb_noun (resolve_entity, validate_claim, generate_llms_txt, scan_dependency), others are bare nouns (entity_profile, company_facts, bet_research, resolution_audit, recall, remember, subscribe). Namespacing is inconsistent — twcompany_*, polymarket_*, pipeworx_*, ask_pipeworx* prefixes coexist with unprefixed general verbs, and polymarket_edges / polymarket_edge_tracker / polymarket_arbitrage are near-synonyms that are hard to distinguish by name alone.

Tool Count2/5

39 tools is heavy for what the server advertises (Taiwan company registry lookup, which would need ~3). The extra tools look like an entire unrelated data-gateway platform bolted on, so the count is far beyond the apparent scope, though each individual tool is plausibly functional.

Completeness2/5

For the stated Taiwan-companies domain the surface is thin: it resolves a company by number or name and returns status, but gives no filings, financial statements, shareholder/director detail beyond the responsible person, or industry/change history. Conversely it ships dozens of unrelated tools (US SEC, Polymarket, npm deps, memory, subscriptions), so the set does not coherently cover the domain it is named for.

Tool Schema Changelog

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

  1. 1 tool update
    • Changedrelease_calendar_markets2 fields changed
      • addedOutput schema / properties / empty_reason
        Added value: +{
        +  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
        +  "type": "string"
        +}
      • addedOutput schema / properties / hint
        Added value: +{
        +  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
        +  "type": "string"
        +}
  2. 39 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcompany_facts
    • First observedcompare_entities
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedtwcompany_by_ban
    • First observedtwcompany_search_name
    • First observedtwcompany_status
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Search and analyze 14M+ Taiwan government tenders (since 1999, updated daily): full-text search, award records, vendor win-rate and rivalry reports, agency spending patterns with next-tender predictions, and bid price analysis. Free, no API key required.
    1
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Unmodified government company data from 27 registries, live. Cross-border UBO chain walker for AI agents. 60+ tools covering GB, IE, NO, FR, DE, NL, PL, BE, CH, LI, MC, IM, IS, CY, AU, NZ, CA, TW, HK, MY, FI, CZ, ES, IT, KR, US — raw upstream fields preserved, no LLM extraction.
    10
    18
    Apache 2.0
  • A
    license
    A
    quality
    D
    maintenance
    讓AI助理直接查詢台灣公開資料,包括公司登記、詐騙查核與實價登錄,資料即時且附來源連結。
    23
    8 npm
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.