Greynoise runs on your own machine — the client starts it, so there is no endpoint to ping. 28 installs a week from npm. Last commit 26 Feb 2026.
MCP server for GreyNoise API - Check if IPs are internet background noise or targeted attacks
Nothing serious here today
Today is the operative word: we check Greynoise every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add greynoise -- npx -y mcp-greynoise{
"mcpServers": {
"greynoise": {
"args": [
"-y",
"mcp-greynoise"
],
"command": "npx"
}
}
}[mcp_servers.greynoise]
command = "npx"
args = ["-y", "mcp-greynoise"]{
"mcpServers": {
"greynoise": {
"args": [
"-y",
"mcp-greynoise"
],
"command": "npx"
}
}
}{
"mcpServers": {
"greynoise": {
"args": [
"-y",
"mcp-greynoise"
],
"command": "npx"
}
}
}This one needs environment variables set before it will start:
GREYNOISE_API_KEY (GreyNoise API key (free Community tier: 50 req/day)).
The author declared them in the registry entry; get the values from the project itself.
Alternatives to Greynoise
same job, measured the same wayMCP server for Rundeck API integration
MCP server for Healthchecks.io API
MCP server for SMS.RU API — send SMS, check status, balance. 3 tools.
MCP server for Chanty API integration
Background Check Quotes: the site's own MCP server — dataset, enquiry (enquiry = a human...
MCP server for Tableau API integration
Check if an MCP server tool changed or hides injection patterns before you trust it.
MCP server for Azure API integration
Greynoise — questions
Answers built from our own checks of this server.