Skip to main content
Released: November 10, 2026 The Seltz MCP server now runs on new infrastructure. Its URL, https://mcp.seltz.ai/mcp, and its tool names are unchanged. The search and fetch tools now return a different format, and some argument names and limits changed.

Highlights

  • Markdown results — search and fetch return compact Markdown that an agent reads directly. They no longer return a JSON document, structuredContent, or an outputSchema.
  • Console sign-in — A client that connects without an API key now opens the Seltz Console, where you sign in, choose an organization if you belong to more than one, and approve access. Calls bill that organization. API keys in the x-api-key or Authorization: Bearer header still work.
  • snake_case arguments — search takes query, max_results, scope, include_domains, exclude_domains, from_date, and to_date, the same names as the REST Search endpoint. A call with an old camelCase name such as maxResults or fromDate gets a tool error that lists the accepted names.
  • New limits — search returns at most 50 results, and the server lowers a higher max_results to 50. Each result has up to 1,000 characters of page text, down from 20,000, plus its snippets. Call fetch for the full page. fetch takes up to 5 URLs per call, down from 20, and more is a tool error. It returns at most 100,000 characters of page text per call, split equally among the pages that return text, so each of five pages gets up to 20,000 characters. The server cuts a longer page and notes its full length.
  • Checked date filters — from_date and to_date accept a date, a datetime, or an offset such as now-7d. A value in any other form gets a tool error, and so does a date filter with the companies or people scope, which have no publication dates. When you set either filter, the server leaves out results that have no publication date.
Most clients read the tool list when they connect and pick up the new argument names on their own. If yours keeps a saved copy, such as a ChatGPT connector, refresh or reconnect the server.

Parsing results in code? Use the REST API

The MCP server writes its output for agents, and its wording can change. If your code reads fields from search or fetch results, call the Search or Fetch endpoint instead. Both return JSON described by the OpenAPI spec, take the same argument names, and accept an API key from the Console.
cURL

MCP Server

Setup instructions