Skip to main content
Glama

Ipqualityscore

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

IPQualityScore MCP — wraps the IPQualityScore fraud-prevention API

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
29.6% over 40 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-ipqualityscore
GitHub Stars
0
Server Listing
mcp-ipqualityscore

TDQS

A3.8/5.0

Scored across 35 tools

Disambiguation3/5

Several clusters overlap: ask_pipeworx / ask_pipeworx_beta (explicitly stated to be currently identical) / ask_pipeworx_grounded / deep_research all answer questions over the same catalog, and polymarket_edges / polymarket_arbitrage / polymarket_fill_risk / polymarket_edge_tracker all chase trading edges. The very long, self-referential descriptions do a lot of work disambiguating them, but the boundaries still require careful reading rather than being self-evident.

Naming Consistency4/5

Names are uniformly snake_case and mostly follow a verb_noun or resource-qualified pattern (check_ip, resolve_entity, subscribe, recent_alerts, polymarket_kalshi_spread). A few are noun-only labels (entity_profile, recent_changes, polymarket_edges) rather than action verbs, a minor deviation but the casing convention is never broken.

Tool Count2/5

35 tools is heavy and spans unrelated domains — IP/email/phone/URL fraud scoring, prediction-market arbitrage, entity resolution, memory key-value storage, subscriptions, and AI-visibility marketing — which is far beyond what the server's name (Ipqualityscore) implies. The count itself is at the 'too many' threshold and the breadth reads as a kitchen-sink aggregator rather than a coherent scoped set.

Completeness3/5

The apparent IPQS fraud domain is actually covered thinly (only four check_* tools, with no explicit domain-reputation or bulk/batch operation), while the surrounding Pipeworx aggregation surface is broad. Coverage feels lopsided: no delete/update for subscriptions beyond unsubscribe, and the mismatch between the server name and its actual contents leaves the stated purpose only partially served.

Tool Schema Changelog

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

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
  2. 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."
  3. 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."
  4. 4 tool updates
    • Changedcheck_email3 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "email": "user@example.com"
-  },
-  {
-    "_apiKey": "your-ipqualityscore-api-key",
-    "email": "test@gmail.com"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-ipqualityscore-api-key",
+    "email": "user@example.com"
+  },
+  {
+    "_apiKey": "your-ipqualityscore-api-key",
+    "email": "test@gmail.com"
+  }
+]
      • changedInput schema / properties / _apiKey / description
        Previous value: -"Optional — your own IPQualityScore API key for higher limits; omit to use the shared Pipeworx key."New value: +"Your own IPQualityScore API key (BYO — Pipeworx does not supply one). Free tier at ipqualityscore.com; the key is on the account dashboard."
      • changedInput schema / required
        Previous value: -[
-  "email"
-]New value: +[
+  "email",
+  "_apiKey"
+]
    • Changedcheck_ip3 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "ip": "8.8.8.8",
-    "strictness": 1
-  },
-  {
-    "_apiKey": "your-ipqualityscore-api-key",
-    "ip": "192.168.1.1",
-    "strictness": 0
-  }
-]New value: +[
+  {
+    "_apiKey": "your-ipqualityscore-api-key",
+    "ip": "8.8.8.8",
+    "strictness": 1
+  },
+  {
+    "_apiKey": "your-ipqualityscore-api-key",
+    "ip": "192.168.1.1",
+    "strictness": 0
+  }
+]
      • changedInput schema / properties / _apiKey / description
        Previous value: -"Optional — your own IPQualityScore API key for higher limits; omit to use the shared Pipeworx key."New value: +"Your own IPQualityScore API key (BYO — Pipeworx does not supply one). Free tier at ipqualityscore.com; the key is on the account dashboard."
      • changedInput schema / required
        Previous value: -[
-  "ip"
-]New value: +[
+  "ip",
+  "_apiKey"
+]
    • Changedcheck_phone3 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "phone": "18007267864"
-  },
-  {
-    "country": "US",
-    "phone": "+1 800 726 7864"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-ipqualityscore-api-key",
+    "phone": "18007267864"
+  },
+  {
+    "_apiKey": "your-ipqualityscore-api-key",
+    "country": "US",
+    "phone": "+1 800 726 7864"
+  }
+]
      • changedInput schema / properties / _apiKey / description
        Previous value: -"Optional — your own IPQualityScore API key for higher limits; omit to use the shared Pipeworx key."New value: +"Your own IPQualityScore API key (BYO — Pipeworx does not supply one). Free tier at ipqualityscore.com; the key is on the account dashboard."
      • changedInput schema / required
        Previous value: -[
-  "phone"
-]New value: +[
+  "phone",
+  "_apiKey"
+]
    • Changedcheck_url3 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "url": "https://example.com"
-  },
-  {
-    "_apiKey": "your-ipqualityscore-api-key",
-    "url": "https://suspicious-domain.net"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-ipqualityscore-api-key",
+    "url": "https://example.com"
+  },
+  {
+    "_apiKey": "your-ipqualityscore-api-key",
+    "url": "https://suspicious-domain.net"
+  }
+]
      • changedInput schema / properties / _apiKey / description
        Previous value: -"Optional — your own IPQualityScore API key for higher limits; omit to use the shared Pipeworx key."New value: +"Your own IPQualityScore API key (BYO — Pipeworx does not supply one). Free tier at ipqualityscore.com; the key is on the account dashboard."
      • changedInput schema / required
        Previous value: -[
-  "url"
-]New value: +[
+  "url",
+  "_apiKey"
+]

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