Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Portfolio Terminal is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
10
tools declared
remote
at its publisher
—
calls last 7d
What it does
Dated ETF, stock and calendar data, plus tax-loss, withholding and fee math on your holdings.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http portfolio-terminal-mcp https://portfolio-terminal.com/api/mcp
# 2 — ask your agent for something these tools do
# analyze_ticker, who_holds, etf_holdings and 7 more
Portfolio Terminal costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PTAll 1 server
portfolio-terminal1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http portfolio-terminal-mcp https://portfolio-terminal.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Dated key facts and a plain-English chart read for one ticker Portfolio Terminal covers (390 US stocks, 30 ETFs, 17 cryptocurrencies and 4 commodity futures): price and one-year change, 52-week range, distance from the 200-day average, 30-day volatility with a risk rating, P/E and dividend yield, all-time high and "lowest since", ten years against the S&P 500 (SPY), support and resistance levels,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | The ticker as listed in the US ("NVDA", "VOO", "BRK.B"), a coin ("BTC" or "BTC-USD") or a future ("GC=F" for gold). |
Which of the 54 tracked US ETFs hold a US-listed stock (weight and rank, from each issuer's full holdings file, matched on ISIN), and which famous investors hold it in their latest SEC Form 13F (share of their reported portfolio, rank, quarter). Offline data: fast, no market call. Use it for "which ETFs hold PLTR", "does Buffett own Apple".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | A US stock ticker, e.g. "NVDA", "BRK.B". |
An ETF's or index fund's holdings from the issuer's full file (or its latest SEC N-PORT report for funds outside the catalog): the largest lines with their weights, the sector mix, and how concentrated it is (weight of the top 10, how many names make up half the fund, effective number of holdings). Share classes of one fund (VFIAX → VOO) resolve to its file.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | The fund ticker, e.g. "VOO", "QQQ", "SCHD", "AVUV". |
| limit | integer | no | How many holdings, largest first to return (1–100, default 25). |
How much of two ETFs is the same money: overlap by weight (the sum, over companies both hold, of the smaller of the two weights), how many companies they share, what share of each fund sits in names the other also holds, and the largest shared holdings. Full issuer files, matched on ISIN. Use it for "VOO vs QQQ overlap", "is IVV the same as VOO".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fund_a | string | yes | First fund ticker, e.g. "VOO". |
| fund_b | string | yes | Second fund ticker, e.g. "QQQ". |
| limit | integer | no | How many shared holdings to return (1–50, default 10). |
Five-year head-to-head of two covered stocks or ETFs from weekly closes adjusted for dividends and splits: total and annualized return, 1-, 3- and 5-year returns, volatility, worst drawdown and worst week, correlation, what $10,000 became, plus each one's dividend yield, beta and (for funds) fee. Use it for "SCHD vs VIG", "NVDA vs AMD".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| a | string | yes | First ticker, e.g. "SCHD". |
| b | string | yes | Second ticker, e.g. "VIG". |
US stocks and ETFs (of the 420 Portfolio Terminal covers) going ex-dividend in a month or a date range: ex-dividend date, pay date, dividend per share, yield, frequency, and whether the date is confirmed by the company or estimated from its payment rhythm. Buy before the ex-date to receive the dividend. Filter by one ticker with symbol.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| month | string | no | A calendar month as YYYY-MM, from three months back to three months ahead. Defaults to the current month. Ignored when from is given. |
| from | string | no | First day of a date range, YYYY-MM-DD (instead of month). Use it for "this week" or "the next 10 days". |
| days | integer | no | Length of the range that starts at from, in calendar days (1–31, default 10). |
| symbol | string | no | Only this ticker, e.g. "KO". |
| limit | integer | no | How many entries, earliest first to return (1–200, default 50). |
US companies (of the 390 Portfolio Terminal covers) reporting earnings in a month or a date range: the day, before the open or after the close, EPS and revenue estimates, whether the date is confirmed or estimated, and once out, the result against the consensus and how many recent quarters beat it. Filter by one ticker with symbol.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| month | string | no | A calendar month as YYYY-MM, from three months back to three months ahead. Defaults to the current month. Ignored when from is given. |
| from | string | no | First day of a date range, YYYY-MM-DD (instead of month). Use it for "this week" or "the next 10 days". |
| days | integer | no | Length of the range that starts at from, in calendar days (1–31, default 10). |
| symbol | string | no | Only this ticker, e.g. "NVDA". |
| limit | integer | no | How many reports, earliest first, larger companies first on the same day to return (1–200, default 50). |
Computes, on the lots the user gives (ticker, shares, price, date, account and its type), the losses a sale before December 31 would realize and what they offset, with the engine of Portfolio Terminal's "Before December 31" panel. US resident: FIFO lots per account, short vs long term, this year's realized gains, the year netted as Schedule D nets it (the $3,000 off ordinary income, the carryforwa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| residence | string | yes | Where the user pays tax: US or FR (France). |
| lots | array | yes | Every purchase of the shares held, one per lot; add this year's sales (side "sell") with the purchases they came from, so realized gains and wash sales count. At most 300. |
| prices | array | no | Current price per share by ticker, in the lots' currency, when the user gave it. Tickers left out are priced from Yahoo Finance. At most 150. |
| filing_status | string | no | US only: Form 1040 filing status (default single). Married filing separately caps the deduction at $1,500. |
| carryover | object | no | US only: capital losses carried into this year from last year's return, in dollars, by term. |
Computes, on the dividends the user gives (a year of dividends, gross, by payer: a ticker such as "NESN.SW" or a country code), the tax each payer's country keeps at source, the treaty rate, and what was withheld above it over 12 months, which only that country refunds on a claim; for a French resident, also the treaty part France credits on form 2047. Same engine as Portfolio Terminal's Income an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| residence | string | yes | Where the user pays tax: FR (France), US, or other (the usual 15% treaty rate is used). |
| currency | string | no | Currency of every amount (default EUR for FR, USD otherwise). |
| dividends | array | yes | One line per payer: a year of dividends, gross (before any tax). At most 100. |
Computes, on the funds and amounts the user gives, what each fund's expense ratio takes a year (amount × expense ratio), the total and the weighted ratio, with the expense ratios of Portfolio Terminal's fees view (the fund's latest annual report as Yahoo Finance lists it). A fact, not a verdict: no other fund is suggested. A line that is not a fund, or whose ratio is not published, is named. Nothi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| currency | string | no | Currency of every amount (default USD). |
| funds | array | yes | One line per fund: its ticker and what is invested in it now. At most 50. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Portfolio Terminal or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.1.0 · scanned 2 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestc58c1d7e4d4d95082defb1d9a1eb80833630b83b18bc8262fa8d3ef3168fbf07
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| analyze_ticker | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| who_holds | no tags | |
| etf_holdings | no tags | |
| etf_overlap | no tags | |
| compare | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| dividend_calendar | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| earnings_calendar | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| tax_loss_harvest | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| withholding_check | no tags | |
| fund_fees | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc58c1d7e4d4d9508
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Portfolio Terminal can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.