@0xinsider/mcp 1.2.2 → 1.2.3

package/README.md

@@ -1,8 +1,8 @@
 # @0xinsider/mcp
 
-Official CLI and MCP server for [0xinsider](https://0xinsider.com) — prediction market intelligence for AI agents.
+Official CLI and MCP server for [0xinsider](https://0xinsider.com) — advanced tools for sports and esports markets, powered by Polymarket, for AI agents and scripts.
 
-Gives your AI agent and terminal scripts access to trader grades, whale trades, smart money signals, market intelligence, and insider-radar flags across prediction markets.
+Gives your AI agent and terminal scripts the same Polymarket data the tools run on: wallet grades on settled P&L, large trades, which side the profitable wallets hold on a market, daily picks on a public record, and insider-radar flags.
 
 ## CLI and MCP entry points
 
@@ -13,12 +13,31 @@ npm install --global @0xinsider/mcp
 0xinsider --help
 ```
 
+On macOS or Linux with Homebrew, the official tap installs the same package
+and both commands (the formula is named `oxinsider` because Homebrew formula
+names cannot start with a digit):
+
+```bash
+brew install 0xinsider/tap/oxinsider
+0xinsider --help
+```
+
 The package also exposes `0xinsider-mcp` as an explicit alias. Both commands
 run the same CLI, and `npx -y @0xinsider/mcp` remains the zero-install path.
 
+The same CLI is published under the unscoped name `0xinsider`, so `npx 0xinsider --help`
+and `npm install --global 0xinsider` work too.
+
+For Python, `pip install 0xinsider` installs the official Python SDK
+([`0xinsider-python`](https://github.com/0xinsider/0xinsider-python), import `oxinsider`).
+For Go programs, the official Go SDK
+([`github.com/0xinsider/0xinsider-go`](https://github.com/0xinsider/0xinsider-go))
+is generated from the same public OpenAPI contract the CLI and MCP tools read.
+
 ## Two ways to connect
 
-- **Remote HTTP (no install)** — `POST https://api.0xinsider.com/api/v1/mcp` with `Authorization: Bearer oxi_sk_live_...`. Implements the MCP Streamable HTTP transport (protocolVersion `2025-11-25`). Works with MCP clients that speak HTTP and can send headers. Legacy `?token=` authentication works only on exact `/api/v1/mcp`; every other protected V1 route rejects it. Prefer headers because URL secrets can leak through shell history, browser history, proxy logs, and crash reports. The retirement date is unknown until external URL-only client compatibility is checked. Remote and stdio use the same read-only public V1 tool catalog, rate limits, and billing.
+- **Remote HTTP (no install)** — `POST https://api.0xinsider.com/api/v1/mcp` with `Authorization: Bearer oxi_sk_live_...`. Implements the MCP Streamable HTTP transport (protocolVersion `2025-11-25`). Works with MCP clients that speak HTTP and can send headers. `initialize`, `ping` and `tools/list` need no key, so a client can show the catalog first; `tools/call` without a credential answers HTTP 401 with a `WWW-Authenticate` challenge naming the RFC 9728 document at `/.well-known/oauth-protected-resource/api/v1/mcp`. Clients that implement the MCP authorization spec follow it to the OAuth 2.1 authorization server (PKCE S256, dynamic client registration), sign the user in and send the resulting access token instead of an API key; see https://0xinsider.com/auth.md. Legacy `?token=` authentication works only on exact `/api/v1/mcp`; every other protected V1 route rejects it. Prefer headers because URL secrets can leak through shell history, browser history, proxy logs, and crash reports. The retirement date is unknown until external URL-only client compatibility is checked. Remote and stdio use the same read-only public V1 tool catalog, rate limits, and billing.
+- **Documentation server (no install, no key)** — `https://docs.0xinsider.com/mcp` searches and reads the developer documentation over MCP. Add it beside the product server so an agent can look up how an endpoint works before it calls a tool.
 - **Stdio (this npm package)** — run `npx -y @0xinsider/mcp` locally for Claude Code / Cursor / Codex / Gemini CLI. Best when the client can launch a child process and you prefer to keep the API key out of URLs.
 
 <!-- generated-mcp-catalog:start -->

package/dist/constants.d.ts

@@ -2,7 +2,7 @@ export declare const API_BASE_URL = "https://api.0xinsider.com";
 export declare const SITE_URL = "https://0xinsider.com";
 export declare const DEVELOPERS_URL = "https://0xinsider.com/developers";
 export declare const PRICING_URL = "https://0xinsider.com/pricing";
-export declare const VERSION = "1.2.2";
+export declare const VERSION = "1.2.3";
 export declare const PACKAGE_NAME = "@0xinsider/mcp";
 export declare const SERVER_NAME = "0xinsider";
 export declare const API_KEY_ENV_VAR = "OXINSIDER_API_KEY";

package/dist/constants.js

@@ -15,7 +15,7 @@ export const PRICING_URL = `${SITE_URL}/pricing`;
 // flow runs `cd mcp && npm ci` from a clean checkout, where `web/node_modules` need not
 // exist.
 // generated-package-version:start
-export const VERSION = "1.2.2";
+export const VERSION = "1.2.3";
 // generated-package-version:end
 export const PACKAGE_NAME = "@0xinsider/mcp";
 export const SERVER_NAME = "0xinsider";

package/package.json

@@ -1,7 +1,8 @@
 {
   "name": "@0xinsider/mcp",
-  "version": "1.2.2",
-  "description": "Official 0xinsider CLI and MCP server: Polymarket analytics for sports and esports in real-time",
+  "version": "1.2.3",
+  "mcpName": "io.github.0xinsider/mcp",
+  "description": "Official 0xinsider CLI and MCP server: advanced tools for sports and esports markets, powered by Polymarket",
   "type": "module",
   "main": "dist/index.js",
   "bin": {