io.github.mrfentmen/greynoise-mcp
greynoise-mcp
Is the io.github.mrfentmen/greynoise-mcp MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.
MCP server for GreyNoise: IP noise classification, tags. Free key.
alive probed 2026-11-14 · unchanged since 2026-10-30
- Run it
- npx -y greynoise-mcp@1.0.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- greynoise-mcp 1.0.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 317 tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 343. The o200k_base estimate is 170. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/mrfentmen/awesome-mcps
- Registry
- active, updated 2026-09-22 · registry entry
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.86×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| query_tags | 188 | 101 | 59 % |
| check_ip | 129 | 69 | 41 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.mrfentmen/graph-algorithms-mcp · alive
- io.github.mrfentmen/graph-modeling-language-mcp · alive
- io.github.mrfentmen/graphql-mcp · alive
- io.github.mrfentmen/greenhouse-mcp · alive
- io.github.mrfentmen/grid-carbon-mcp · alive
- io.github.mrfentmen/groovy-mcp · alive
- io.github.mrfentmen/groovy-server-pages-mcp · alive
- io.github.mrfentmen/groq-mcp · alive
Servers that mention greynoise.
- Greynoise io.github.pipeworx-io/greynoise · alive
- io.github.aplaceforallmystuff/mcp-threatintel · alive
- io.github.nickjlucker/greynoise · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.