Taiwan Companies
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
Scored across 39 tools
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'.
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.
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.
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 tool update
- Changed
release_calendar_markets2 fields changed- added
Output schema / properties / empty_reasonAdded 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" +} - added
Output schema / properties / hintAdded value: +{ + "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).", + "type": "string" +}
39 tool updates
- First observed
ai_visibility_check - First observed
ask_pipeworx - First observed
ask_pipeworx_beta - First observed
ask_pipeworx_grounded - First observed
bet_research - First observed
company_facts - First observed
compare_entities - First observed
deep_research - First observed
discover_tools - First observed
entity_profile - First observed
forget - First observed
generate_llms_txt - First observed
kalshi_weather_edge - First observed
list_subscriptions - First observed
pipeworx_feedback - First observed
pipeworx_trending - First observed
polymarket_arbitrage - First observed
polymarket_edge_tracker - First observed
polymarket_edges - First observed
polymarket_fill_risk - First observed
polymarket_kalshi_spread - First observed
recall - First observed
recent_alerts - First observed
recent_changes - First observed
release_calendar_markets - First observed
remember - First observed
resolution_audit - First observed
resolution_diff - First observed
resolve_entity - First observed
scan_competitor_ai_presence - First observed
scan_dependency - First observed
search_within - First observed
subscribe - First observed
suggest_questions - First observed
twcompany_by_ban - First observed
twcompany_search_name - First observed
twcompany_status - First observed
unsubscribe - First observed
validate_claim
Related MCP Connectors
Live data from 80+ official national company registries. Unmodified. For KYB and due diligence.
- BrregOAuthpro.publifye
Norway's company register (Enhetsregisteret) for AI: lookup, search, name resolution, key financials
OpenCorporates MCP — Global company registry data (BYO key)
Hong Kong Companies Registry (香港公司註冊處) open data via data.gov.hk (keyless): search companies by…
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceSearch 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.1MIT
- AlicenseAqualityAmaintenanceUnmodified 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.1018Apache 2.0
- AlicenseAqualityDmaintenance讓AI助理直接查詢台灣公開資料,包括公司登記、詐騙查核與實價登錄,資料即時且附來源連結。238 npmMIT
- AlicenseAqualityCmaintenanceStructured business intelligence for AI agents. 5.5M verified entities across 34 countries, 40.3M BORME mercantile acts, EU VAT validation, GLEIF, healthcare registries. 20 tools.61MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.