Skip to main content
Glama

Public Suffix List

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Public Suffix List MCP.

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.4% over 39 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-public-suffix-list
GitHub Stars
0
Server Listing
public-suffix-list

TDQS

C2.8/5.0

Scored across 35 tools

Disambiguation2/5

There are several near-duplicate entry points: ask_pipeworx, ask_pipeworx_beta (explicitly identical to ask_pipeworx right now), ask_pipeworx_grounded, deep_research, validate_claim, discover_tools, and suggest_questions all answer 'route my question somewhere' and overlap heavily. Entity tools (entity_profile, compare_entities, resolve_entity, recent_changes) also blur boundaries. The verbose descriptions mitigate some confusion, but an agent can easily misselect among the ask_* family.

Naming Consistency3/5

Most names use snake_case, but conventions are mixed: verb_noun (resolve_entity, validate_claim, list_subscriptions), bare nouns (public_suffix, registrable_domain, parse), and branded names (ask_pipeworx_beta, pipeworx_trending). Readable but not a predictable pattern.

Tool Count2/5

35 tools is heavy, and it is wildly disproportionate to the server's stated purpose ('Public Suffix List') — only 4 tools (parse, public_suffix, registrable_domain, list_version) relate to public suffixes. The remainder is an unrelated gateway/prediction-market/memory surface, so most tools do not earn their place for the named scope.

Completeness3/5

The PSL-related surface covers parsing, suffix extraction, registrable domain, and version/rules count, which handles the core workflow but offers no way to enumerate or validate arbitrary suffixes (e.g. is-public-suffix, IDN handling, list browsing). Judged against the broader gateway domain the toolset is expansive but full of redundant ask_* variants rather than clean 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
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