EErgoKit

Documentation

How to use ErgoKit

Use ErgoKit to check public websites, inspect search and AI-readiness signals, and run everyday developer utilities.

Website checksTest public URLs

Check GEO, SEO, metadata, schema, headers, robots.txt, sitemaps, DNS, redirects, HTTP status, and CORS.

Local utilitiesWork in your browser

Format JSON, decode JWTs, convert Base64, generate hashes, UUIDs, QR codes, UTM URLs, and more.

MCPConnect AI clients

Compatible MCP clients can call selected read-only ErgoKit diagnostics for public URLs and domains.

Web Tools

Most users should start from the web app. Search for a tool on the homepage, open the tool page, enter a public URL or local input, and review the result summary, details, issues, and recommendations.

GEO Score CheckerScore AI/search discoverability signals.HTTP Status CheckerInspect status, redirects, headers, and timing.Meta Tag / OG PreviewReview title, description, canonical, and social previews.JSON FormatterFormat and validate JSON locally.

Browse all toolsGEOSEODeveloper

Choose A Tool

AI visibility
Use GEO Score Checker, Meta Tag / OG Preview, Schema Validator, Robots.txt Tester, and Sitemap Checker.
Technical SEO
Use HTTP Status Checker, Redirect Chain Checker, Sitemap Checker, Meta Tag / OG Preview, and Schema Validator.
Security
Use Security Headers Checker, CORS Tester, JWT Decoder, and Hash Generator.
Developer work
Use JSON Formatter, Base64 Tool, UUID Generator, Timestamp Converter, URL Encoder/Decoder, and Cron Generator.
Marketing
Use UTM Builder, QR Code Generator, URL Encoder/Decoder, and Meta Tag / OG Preview.

MCP For AI Clients

MCP is optional. Use it when an AI client, agent, or automation needs to call ErgoKit tools directly. For normal use, the website is the easiest interface.

Endpoint
https://ergokit.co/mcp
Transport
Streamable HTTP
Access
Public, unauthenticated, rate-limited
Use case
Read-only diagnostics for public URLs and public domains

Available MCP tools

Use ask_ergokit when you want ErgoKit to choose the right diagnostic from a plain request such as check NS records for example.com or check HTTP status for ergokit.co.

Example prompts

  • check deployment health for https://ergokit.co/
  • check HTTP status for https://ergokit.co/
  • trace redirects for https://ergokit.co/
  • check NS records for ergokit.co
  • test robots.txt for https://ergokit.co/tools/geo-score-checker/
  • validate schema for https://ergokit.co/

These examples use ask_ergokit. MCP clients can also call exact tools directly when the workflow already knows which check it needs.

Tool names

  • ask_ergokit
  • check_geo_score
  • check_http_status
  • check_security_headers
  • lookup_dns_records
  • preview_meta_tags
  • trace_redirect_chain
  • test_robots_txt
  • check_sitemap
  • validate_schema
  • test_cors_policy
  • check_deployment_health

Connect with MCP Inspector

npx @modelcontextprotocol/inspector

Choose Streamable HTTP, use https://ergokit.co/mcp, then list tools and run a small check such as lookup_dns_records for example.com.

Privacy And Safety

  • Local utilities run in your browser. Do not paste secrets unless you are comfortable handling them locally.
  • Public URL checks fetch public pages transiently and show metadata, headers, timing, issues, and recommendations.
  • ErgoKit does not show full response bodies in server-side diagnostic results.
  • Private, local, internal, and reserved network targets are blocked.
  • MCP tools are read-only and rate-limited.
  • For feedback, bug reports, or MCP questions, email hello@ergokit.co.

Public Index Files

These are mainly for search engines, AI crawlers, and integrations. Most users do not need them directly.

sitemap.xmlCanonical public pages for search engines.llms.txtConcise AI-readable summary of ErgoKit pages and tools.tools.jsonStructured catalog of live tools and categories.