Is io.github.XogZ3/botoi-mcp up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.
A stock client connected with no credential and negotiated 2025-11-25. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server says it is | botoi 1.0.0 |
| Answered in | 818 ms |
| Endpoint checked | https://api.botoi.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 | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://api.botoi.com/mcp/server-card |
| MCP server card (SEP-1649 location) | Published, does not validate: transport.endpoint is required for an HTTP transport. SEP-1649 shape; Botoi 1.0.0; MCP 2025-06-18; streamable-http./.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://api.botoi.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 49 tools: dev_cron_describe, dev_diff, dev_hash, dev_jwt_sign, dev_jwt_verify, dev_password_generate, dev_regex_test, dev_semver_parse, dev_timestamp_convert, dev_url_decode, dev_url_encode, dev_uuid, lookup_accessibility, lookup_address_validate, lookup_breach_check, lookup_company, lookup_dns, lookup_dns_monitor, lookup_domain_availability, lookup_email, lookup_headers, lookup_ip, lookup_phone, lookup_ssl, lookup_ssl_cert_expiry, lookup_tech_detect, lookup_url_metadata, lookup_vpn_detect, lookup_whois, security_decrypt, security_encrypt, security_pii_detect, security_totp_generate, security_validate_credit_card, text_base64_decode, text_base64_encode, text_csv_to_json, text_html_to_markdown, text_json_format, text_json_to_yaml, text_json_validate, text_markdown_to_html, text_xml_to_json, text_yaml_to_json, transform_code_format, transform_json_to_typescript, transform_minify_css, transform_minify_js, transform_sql_format.
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.XogZ3/botoi-mcp |
|---|---|
| Description | 49 developer tools via MCP: DNS, WHOIS, IP lookup, JWT, hashing, QR, and more. |
| Endpoint | https://api.botoi.com/mcp |
| Publisher repository | https://github.com/XogZ3/botoi |
| Version | 1.0.0 |
| 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