Skip to main content
Glama

Transport Nsw

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Transport for NSW MCP — journey planning, live departures, service alerts

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.1% over 21 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-transport-nsw
GitHub Stars
0
Server Listing
transport-nsw

TDQS

A3.9/5.0

Scored across 40 tools

Disambiguation2/5

Several tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all route natural-language questions; bet_research, polymarket_edges, polymarket_arbitrage, and polymarket_fill_risk all analyze prediction markets. Descriptions differentiate them, but the boundaries between 'ask', 'research', 'validate', and 'scan' remain unclear.

Naming Consistency4/5

All names use snake_case consistently, with predictable prefixes such as tfnsw_, polymarket_, and pipeworx_. There is minor deviation from a strict verb_noun pattern (e.g., entity_profile, company_facts, tfnsw_departures), but the overall convention is readable and predictable.

Tool Count2/5

40 tools is far too many for a server named Transport Nsw, whose core tools are only the four tfnsw_* ones. The remaining 36 tools cover unrelated Pipeworx gateway, prediction-market, AI-marketing, and memory functions, making the set grossly oversized for its apparent transport scope.

Completeness3/5

The four NSW transport tools cover realtime alerts, carparks, departures, and trip planning, which handles many common queries but leaves gaps like fares, accessibility details, and static timetables. Because most of the surface is unrelated to NSW transport, the set is neither focused nor complete for the stated domain.

Tool Schema Changelog

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

  1. 40 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 observedtfnsw_alerts
    • First observedtfnsw_carparks
    • First observedtfnsw_departures
    • First observedtfnsw_trip_plan
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources