Skip to main content
Glama

Greynoise

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

GreyNoise Community MCP — internet scanner classification (free tier with key)

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
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-greynoise
GitHub Stars
0
Server Listing
mcp-greynoise

TDQS

A4.1/5.0

Scored across 32 tools

Disambiguation3/5

The description text works hard to steer callers, but the tool set has real overlap: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded are three variants on the same router (with beta explicitly identical right now), and six polymarket tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) share a domain an agent could easily misselect within. Memory (remember/recall/forget) and subscription (subscribe/list_subscriptions/unsubscribe/recent_alerts) clusters are clean by contrast.

Naming Consistency4/5

Nearly all names are snake_case and follow a verb_noun or noun_noun convention, so the set reads consistently. Minor deviations exist (ai_visibility_check, entity_profile, ip_context, recent_changes are noun-led rather than verb-led), but nothing is chaotic or mixed-case.

Tool Count3/5

32 tools is on the heavy side and includes genuine redundancy (the identical ask_pipeworx_beta, six overlapping polymarket tools). It is defensible for a broad multi-domain data gateway, but the surface would benefit from consolidation.

Completeness4/5

Coverage across research, entity resolution, comparison, memory, subscription lifecycle, and domain specialists is broad and mostly closed-loop. Minor gaps remain (e.g. discovery/onboarding exists but no obvious way to browse the full catalog structure), yet core workflows have an end-to-end tool.

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."

Related MCP Connectors

Related MCP Servers

  • greynoise-mcp-server by GreyNoise-Intelligence

    greynoise-mcp-serverofficial

    GreyNoise-Intelligence
    A
    license
    A
    quality
    A
    maintenance
    MCP server for GreyNoise threat intelligence, enabling IP analysis, GNQL queries, tag and vulnerability lookups, and session/pcap retrieval via natural language.
    48
    56 npm
    5
    MIT
  • honeylabs-mcp by honeylabshq

    honeylabs-mcpofficial

    honeylabshq
    A
    license
    A
    quality
    B
    maintenance
    Honeypot threat intelligence for AI agents. Query 90 days of probe data from our sensor network: IP reputation, scanner classification, CVE probing trends, TLS/SSH/JA4 fingerprints. Free tier 500 credits/day, OAuth + bearer auth, streamable HTTP at https://mcp.honeylabs.net/mcp.
    7
    2
    MIT
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