Sentry MCP vs Nslookup
A side-by-side look at the Sentry MCP and Nslookup MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Sentry MCP for monitoring work as a local process; choose Nslookup for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Sentry MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SENTRY_ACCESS_TOKEN, EMBEDDED_AGENT_PROVIDER, OPENAI_API_KEY, ANTHROPIC_API_KEY, OPENROUTER_API_KEY, OPENROUTER_MODEL, OPENROUTER_REASONING_EFFORT, SENTRY_HOST.
Choose Nslookup when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You want tools like
dns_lookup, dns_record, dns_propagation.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 55/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | SENTRY_ACCESS_TOKENEMBEDDED_AGENT_PROVIDEROPENAI_API_KEYANTHROPIC_API_KEYOPENROUTER_API_KEYOPENROUTER_MODELOPENROUTER_REASONING_EFFORTSENTRY_HOST | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 934 | 23 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 23 |
| Full listing | View Sentry MCP | View Nslookup |
Tools & capabilities
Sentry MCP tools
No tool names declared yet. Check the project README from the listing page.
Nslookup tools 23
dns_lookupLook up all common DNS records (A, AAAA, NS, MX, TXT, CNAME, SOA) for a domaindns_recordLook up a specific DNS record type — supports all 53 types (HTTPS, DNSKEY, TLSA, SPF, etc.)dns_propagationCheck DNS propagation across 18+ global servers (Cloudflare, Google, Quad9, regional, authoritative)webserversGet IPv4 and IPv6 addresses for a domaindns_change_reviewReview proposed DNS changes before applying them: diff vs current DNS, rule-based findings with fixes, and a 0–100 risk scorerdap_lookupRegistration data (RDAP) for an IP, AS number, or domain — owner org, network range, RIR, contacts, dateshosting_reportWho hosts a website: hosting provider, CDN/proxy, DNS provider, mail servers, server location, SSL issuerstatus_pageRead a public status page (by slug or custom domain): overall status, components, active incidentsdns_healthRun a DNS health audit (39 checks across DNSSEC, MX, hygiene, TTL, nameservers, CAA, operational maturity) with severity-weighted scoringssl_certificateCheck SSL/TLS certificate — issuer, expiry, chain validity, cipher strength, SAN domains, TLS versionbimi_vmcCheck BIMI record and VMC (Verified Mark Certificate) — logo URL, trademark info, certificate expirybimi_checkCheck only the BIMI DNS record (faster — skips the VMC certificate fetch)- +11 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Sentry MCP
{
"mcpServers": {
"getsentry-sentry-mcp": {
"command": "npx",
"args": [
"-y",
"@sentry/mcp-server@latest"
],
"env": {
"SENTRY_ACCESS_TOKEN": "YOUR_SENTRY_ACCESS_TOKEN_HERE",
"EMBEDDED_AGENT_PROVIDER": "YOUR_EMBEDDED_AGENT_PROVIDER_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE",
"OPENROUTER_MODEL": "YOUR_OPENROUTER_MODEL_HERE",
"OPENROUTER_REASONING_EFFORT": "YOUR_OPENROUTER_REASONING_EFFORT_HERE",
"SENTRY_HOST": "YOUR_SENTRY_HOST_HERE"
}
}
}
}
Nslookup
{
"mcpServers": {
"nslookup": {
"command": "npx",
"args": [
"-y",
"@nslookup-io/mcp-server"
]
}
}
}
Frequently asked questions
Sentry MCP is categorized under Monitoring and uses a local stdio subprocess. Nslookup belongs to Monitoring and uses a local stdio subprocess. Pick Sentry MCP for monitoring work and Nslookup for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Sentry MCP is listed as free. Auth: api key required. Nslookup has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add getsentry-sentry-mcp and nslookup as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sentry MCP has a quality signal of 55/100 (Good) with 6 views, 0 installs and 934 GitHub stars. Nslookup has 55/100 (Good) with 1 views, 0 installs and 23 GitHub stars.
