publicdotcom-mcp-server
Provides an MCP (Model Context Protocol) server exposing Public.com brokerage/trading API operations as MCP tools (read-only and write/destructive actions) over stdio for AI assistants.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Secrets are supplied via environment variables (good baseline), but the README does not describe least-privilege scopes, token lifetimes, or explicit protections against logging secrets. Destructive trading tools increase the blast radius if an agent is misconfigured.
⚡ Reliability
Best When
You need an AI assistant to retrieve brokerage data and optionally perform order actions through a standardized MCP tool interface, with explicit tool-level readOnly/destructive hints.
Avoid When
You require a web/API gateway interface, strong operational guarantees (e.g., documented idempotency/retry semantics), or you cannot protect secrets and authorize destructive trading operations safely.
Use Cases
- • Get real-time quotes for stocks/options/crypto
- • Read portfolio holdings, buying power, and open orders
- • View transaction/order history and specific order status
- • Preflight/estimate order impact and costs
- • Place and manage trading orders (single-leg and multi-leg), including cancel/replace
Not For
- • Making financial decisions without human oversight
- • Unattended trading without additional safeguards/approvals
- • Use in environments that cannot safely handle brokerage API credentials
Interface
Authentication
Authentication is configured via a required secret (PUBLIC_COM_SECRET). No OAuth and no fine-grained scope model is described in the README.
Pricing
README does not describe hosting costs or API usage pricing; Public.com account/API pricing would apply separately.
Agent Metadata
Known Gotchas
- ⚠ Write/destructive tools can place/cancel/replace real orders; require strong guardrails/confirmation flows before calling them.
- ⚠ Stdio MCP integrations can hide HTTP-level status/headers from the agent unless the server maps errors clearly.
- ⚠ Order operations typically are not naturally idempotent; repeated calls can have financial impact unless the implementation explicitly prevents duplicates.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for publicdotcom-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.