MCP server health, State of MCP census

Nslookup

io.github.venomseven/nslookup

DNS lookups, health reports, SSL certs, security scans, GEO scoring, uptime checks

healthy checked 2026-07-02 · 10/10 checks passed · keyless

Checks

The exact rows akashi check io.github.venomseven/nslookup prints, from the 2026-07-02 census.

Check	Status	Detail
registry status	pass	active
server.json valid	pass	validates against its declared JSON Schema
repo reachable	pass	exists
repo freshness	pass	pushed 90d ago
package npm	pass	published (1.3.0)
remote reachable	pass	HTTP 200 via initialize
MCP conformance	pass	initialize handshake ok
tools/list	pass	11 tools: dns_lookup, dns_record, dns_propagation, webservers, ssl_certificate, bimi_vmc, security_scan, uptime_check, ...
at least one live entrypoint	pass	3 alive
license present	pass	Apache-2.0

Evidence

Repository

github · alive

https://github.com/NsLookup-io/nslookup-mcp

Packages

npm @nslookup-io/mcp-server · published(1.3.0)

Remote endpoints

https://mcp.nslookup.io/mcp
streamable-http · reachable· HTTP 200· initialize_ok

11 tools: dns_lookup, dns_record, dns_propagation, webservers, ssl_certificate, bimi_vmc, security_scan, uptime_check, ...

server.json

validagainst its declared schema

One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).

Verify it yourself

This page is a static read of one dated probe. Run the same check locally, any time, with no key:

$ akashi check io.github.venomseven/nslookup

Install Akashi - single Go binary, zero keys, MIT licensed.

Is this your server?

Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check io.github.venomseven/nslookup --badge.

Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.