inetGeek docs

Overview

Connect inetGeek's sourced infrastructure data to your AI assistant, or read it over plain HTTP

inetGeek publishes sourced, dated infrastructure facts: provider pricing and limits, comparisons, iScore, stack recommendations, per-volume prices and live DNS checks. Every figure carries the vendor page it was read from, the sentence it was read from and the date it was last checked against that page.

These docs cover the two ways to use it from code or an assistant. Neither needs an account or an API key.

Three jobs it is good at

  1. Compare providers on facts you can verify. Ask for two providers, or for every provider that documents a capability, and get the value, the vendor sentence behind it and the date.
  2. Plan a stack from your project's context. Give it the platform you deploy on and the providers you already use; it reports ties as ties instead of presenting the alphabetically first provider as a recommendation.
  3. Check DNS, SPF and propagation live from the assistant you already use, with nothing stored.

Start with connecting a client, then try the example prompts.

Source and licence

The MCP server's code is MIT and lives at github.com/nqzai/inetgeek-mcp. The data it serves is not part of that licence: it is published at inetgeek.com for reading, each figure attributed to its vendor page. These docs are built with Fumadocs, which inetGeek also profiles as a provider — see the disclosure.

On this page