Schwab MCP server

schwab-mcp

Your brokerage data, conversationally. Ask your AI assistant about your positions, screen option spreads, audit today's trades against your strategy rules, and get end-of-day reports — all from natural language. The data cost? About 6 sats per session (~$0.005).

Why This Exists

The data in schwab-mcp is nothing you can't get from ThinkOrSwim, OptionAlpha, or Schwab's own web UI. What you can't get from those tools is a personal trading assistant that blends:

• Your live positions and account balances
• Real-time option chains with Greeks, IV, and OTM%
• Your trading strategy rules (credit floors, RWR targets, sector concentration limits)
• Market context (earnings calendars, VIX levels, sector rotation)
• All of the above in a single conversational turn

Ask "How would you judge my new trades for the day?" and get a structured audit against your criteria. Ask "What are three SPS candidates aligned with my strategy and balanced with my current book?" and get sector-aware, earnings-aware, IV-aware suggestions — grounded in your actual positions, not generic advice.

The AI does the synthesis. schwab-mcp provides the data bridge. You pay per-call in Bitcoin Lightning sats — no subscription, no KYC, no vendor lock-in. A full day of morning report + evening report + follow-up analysis costs about 6 sats (< $0.01).

Multi-tenant MCP server exposing Charles Schwab brokerage data to AI agents via FastMCP. Monetized via Tollbooth DPYC&trade; Lightning micropayments. Serves over Streamable HTTP with direct async httpx calls to api.schwabapi.com.

Don't Pester Your Customer&trade; (DPYC&trade;) &mdash; API monetization for Entrepreneurial Bitcoin Advocates

Inspired by The Phantom Tollbooth by Norton Juster, illustrated by Jules Feiffer (1961).

Version: 0.12.2 &nbsp;

The DPYC&trade; Economy

DPYC&trade; stands for Don't Pester Your Customer. It is a philosophy and protocol for API monetization that eliminates mid-session payment popups, subscription nag screens, and KYC friction.

How it works

before using tools. Each tool call silently debits from their balance. No interruptions, no "please upgrade" modals. Credits expire after a tranche_lifetime window set by the operator's pricing model.

1. Pre-funded balances -- Users buy credits (api_sats) via Bitcoin Lightning

(npub), not an email or password. One keypair per role, managed by the user. No account creation forms.

1. Nostr keypair identity -- Users are identified by a Nostr public key

parameter carrying a poison phrase (e.g., bold-hawk-42) returned by requestnpubproof / receivenpubproof. The calling application remembers this token and passes it on every subsequent call. The MCP stores only sha256(poison):npub in the vault -- never the raw phrase. Proofs are generated via a human-in-the-loop Secure Courier exchange: the patron consciously approves each proof request in their Nostr client. Duration is patron-chosen (up to 7 days). Proofs survive MCP restarts.

1. Poison-keyed proof -- Every paid tool call requires a dpop_token

a deterministic UUID v5 derived from a capability name. Pricing hints come from the category field:

1. UUID-keyed tool identity -- Every tool is a ToolIdentity object with

Shortened. The full README is on GitHub.