inetGeek MCP server

A Model Context Protocol server over inetGeek's infrastructure data: every provider and comparison on the site, and every figure carrying the URL it was read from, the sentence it was read from, and the date it was last checked against that page.

No account, no API key, and nothing you ask it is stored. Every tool is read-only except send_feedback, which records a report for the maintainer and can change nothing.

https://inetgeek-mcp.palashbagchi.workers.dev/mcp

Why point a model at this

A model asked "what does Neon's free tier include" answers from training data that may predate this week's repricing, and cannot tell you where the number came from. Every value here is read from the provider's own documentation and ships with four things: the value, the verbatim sentence it was read from, the source URL, and the date. If a figure is wrong, the excerpt makes it easy to demonstrate.

What the server will not do is more of the point than what it will. It never infers a value from silence, never fills a gap with a plausible number, and never returns a ranking without the interval around it. Where two providers cannot be told apart, it says so.

Connect it

Claude Code

claude mcp add --transport http inetgeek https://inetgeek-mcp.palashbagchi.workers.dev/mcp

Claude Desktop / any MCP client — add to your client's config:

{
  "mcpServers": {
    "inetgeek": {
      "type": "http",
      "url": "https://inetgeek-mcp.palashbagchi.workers.dev/mcp"
    }
  }
}

A machine-readable server card lives at /.well-known/mcp.json, and every underlying feed is indexed at /.well-known/api-catalog.

Tools

Tool	What it returns
list_categories	The categories this site tracks, each with its current provider count.
list_providers	Every provider in one category with its free tier, entry price and the editorial "best for" line — the orientation call before a per-provider lookup.
filter_providers	Providers that document every fact key you name (e.g. SOC 2 and HIPAA), each with the value, source and verification date.
search_infrastructure	Full-text search over every published page — providers, comparisons, DNS records, tools and stacks — including the fact labels each provider documents.
get_provider	The full sourced fact sheet for one provider — pricing, limits, regions and startup-credit programs, each with a source and a verification date.
list_startup_credit_providers	Every provider documented as offering a startup credit program, with the amount and eligibility — a filter, not a per-provider lookup.
get_provider_score	One provider's iScore with its interval and rank, every pillar and criterion with the fact behind it, and the criteria its peers document that it does not — what a provider would publish to move the number.
list_alternatives	Every peer in a provider's category ranked by iScore, with score, interval, entry price and where each differs from the provider named.
compare_providers	The sourced side-by-side comparison for a curated pair, where one exists.
list_comparisons	Every published comparison, optionally only those involving one provider — so an agent knows a pair exists before asking for it.
get_stack_recommendation	Every host that documents real support for a framework or runtime, ordered by strength of documentation.
plan_infrastructure	The /plan/ planner: one suggested provider per layer for a stage or a hand-picked set of layers, a floor-price total, and the layers left out of it for having no clean starting price. Takes the project’s context — what it already uses, the platform it runs on, what it excludes — so a tie is broken by the project and a covered layer is left alone; ties are reported as ties.
estimate_monthly_cost	What each provider that publishes a per-volume price would charge a month at a stated volume (web analytics, email and auth): plan fee plus overage, cheapest first, with the vendor page and read date. inetGeek’s arithmetic on published rates, not a quote.

Twenty tools. Every one except send_feedback is read-only, and the tool list is mirrored on https://inetgeek.com/mcp/.

Give it your project's context

The server cannot see your project; the assistant connected to it can. The tools that benefit take what it finds as arguments, and the server's own instructions tell the client what to read first (its deploy config, dependencies, env var names, real traffic figures):

This is the beginning of the README. Read the rest at the original. Read the full README ↗