Connect the MCP server
One URL, no account, no API key
The inetGeek MCP server gives an AI assistant the same sourced data the site publishes, so it answers from a vendor's own page and a date rather than from training data that may predate this week's price change.
https://inetgeek-mcp.palashbagchi.workers.dev/mcpIt speaks MCP over streamable HTTP, is stateless and needs no authentication: everything it returns is already public.
Pick your client
Claude Code
One command.
Claude.ai
A custom connector.
ChatGPT
A custom connector, where your plan allows it.
Cursor and other clients
A line in the MCP config file.
Client menus change often. Each page is date-stamped with the day its steps were last checked; if a label differs in your version, the vendor's own MCP documentation is the authority and the URL above is all this server needs.
What you get
Twenty tools: find and read providers, filter by documented capability, compare curated pairs, rank alternatives with an interval, plan a stack, estimate a monthly cost at your volume, read the evidence ledger and changelog, and run live DNS checks. All but send_feedback are read-only. See the tool reference.
Give it your project
The server cannot see your repository; your assistant can. Two tools take the project's context as arguments, and the server's own instructions tell the client what to read first. See project context.
What the server keeps
Nothing you ask it. It counts handshakes, calls per tool name and the client's User-Agent, never an IP address or an argument value. See privacy and telemetry.