Is io.github.nanotools-x402/nanotools up? Live MCP status
Yes, it is up. It answered an MCP server/discover with no credential and negotiated protocol 2026-07-28.
A stock client connected with no credential and negotiated 2026-07-28. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2026-07-28 |
| Server says it is | nanotools 4.0.0 |
| Answered in | 323 ms |
| Endpoint checked | https://nano.vodka-24.com/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, does not validate: an A2A 0.3 card: no `supportedInterfaces`, which 1.0 requires in place of `url` and `protocolVersion` (and 1 more). A2A 0.3 shape; 45 skills; HTTP./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://nano.vodka-24.com/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://nano.vodka-24.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 45 tools: api_base64, api_color_convert, api_cron_parse, api_csv2json, api_diff, api_dns, api_fx_rates, api_hash_multi, api_html_entities, api_ip_info, api_json, api_jwt_decode, api_lorem, api_markdown2html, api_og_image, api_password, api_pdf, api_qr, api_random, api_readability, api_regex, api_render_text, api_robots_audit, api_rss, api_scrape, api_screenshot, api_search, api_seo_meta, api_seo_report, api_serp_google, api_serp_yandex, api_sha256, api_slug, api_text_stats, api_timestamp, api_toml2json, api_trends, api_trends_region, api_trends_related, api_unit_convert, api_urlcode, api_uuid, api_weather, api_whois, api_yaml2json.
No change to its tools between 2026-09 and 2026-10.
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | io.github.nanotools-x402/nanotools |
|---|---|
| Title | NanoTools |
| Description | 44 tools for AI agents: Trends, SERP, SEO audits, screenshots, weather, FX, whois, RSS. |
| Endpoint | https://nano.vodka-24.com/mcp |
| Publisher repository | https://github.com/nanotools-x402/nanotools |
| Version | 1.0.1 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt