Alpaca Trading API integration for Model Context Protocol (MCP)
PortfolioFit 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.
What it does
Check normalized portfolios against mandates and calculate allocation constraints.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http portfoliofit-mcp https://portfolio.fit/mcp
# 2 — ask your agent for something these tools do
# list_analysis_portfolios, list_portfolio_series, list_analyses and 7 more
PortfolioFit costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 portfoliofit-mcp https://portfolio.fit/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
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.
List owner-scoped portfolios, analytics datasets, and profile readiness.
No parameter schema on file.
Discover owner-scoped immutable series profiles and their exact dataset versions. This returns metadata and coverage only, never dataset rows.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| portfolio_id | no | — | |
| statuses | no | — | |
| cursor | no | — | |
| page_size | integer | no | — |
Read private calculation groups and independent operations. Filter by kind, portfolio, dates, ready/running/attention status or legacy open/finished status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | no | — | |
| portfolio_id | no | — | |
| status | no | — | |
| date_from | no | — | |
| date_to | no | — | |
| page | integer | no | — |
| page_size | integer | no | — |
Read retained normalized inputs, operations, results and owner-scoped dataset references. This is not an external agent transcript.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| analysis_id | string | yes | — |
Compare a clean mandate with normalized holdings. Do not send PDF, CSV, spreadsheet, or factsheet files; extract them before calling.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| holdings | array | yes | — |
| idempotency_key | string | yes | — |
| mandate | string | no | — |
| rules | no | — | |
| portfolio_name | string | no | — |
| base_currency | string | no | — |
| composition_scope | string | no | — |
| source_warnings | no | — | |
| analysis_name | no | Optional private grouping name. The same case-sensitive name, after trimming outer whitespace, reuses one group for this user. Omit it for an independent operation. Keep the name on retries; each calc |
Calculate explicit portfolio constraints deterministically from normalized holdings. Use this for arithmetic checks, not for interpreting natural-language mandates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| holdings | array | yes | — |
| constraints | array | yes | — |
| idempotency_key | string | yes | — |
| base_currency | string | no | — |
| composition_scope | string | no | — |
| source_warnings | no | — | |
| analysis_name | no | Optional private grouping name. The same case-sensitive name, after trimming outer whitespace, reuses one group for this user. Omit it for an independent operation. Keep the name on retries; each calc |
Upload normalized series_key/date/value/distribution rows and commit a dataset version. For up to 5,000 rows, omit chunk_index and total_chunks to complete in one call. For larger inputs, declare total_chunks on every call, send chunks in order, and reuse upload_id and idempotency_key. The final chunk automatically verifies and commits all data and returns immutable series profiles. Parse files lo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| idempotency_key | string | yes | — |
| rows | array | yes | — |
| chunk_index | integer | no | Zero-based chunk position; upload chunks in order. |
| total_chunks | integer | no | Total number of chunks in this upload. The last accepted chunk commits the dataset automatically. |
| upload_id | no | — | |
| portfolio_id | no | — | |
| new_portfolio_name | string | no | — |
| dataset_id | no | — | |
| dataset_name | string | no | — |
| source | no | — | |
| series_profiles | no | Source-backed semantics for each series_key. Supply on the first or final chunk; the final chunk can complete the proposals before commit. Ambiguous or incomplete profiles require review before calcul | |
| content_hash | string | no | — |
| analysis_name | no | Optional private grouping name. The same case-sensitive name, after trimming outer whitespace, reuses one group for this user. Omit it for an independent operation. Keep the name on retries; each calc |
Cancel a pending upload and permanently remove its staging chunks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| upload_id | string | yes | — |
| analysis_name | no | Optional private grouping name. The same case-sensitive name, after trimming outer whitespace, reuses one group for this user. Omit it for an independent operation. Keep the name on retries; each calc |
Create an immutable profile revision using revise, or explicitly confirm a warning-free proposal with confirmation=true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profile_id | string | yes | — |
| action | string | yes | — |
| confirmation | boolean | no | — |
| revisions | no | — | |
| analysis_name | no | Optional private grouping name. The same case-sensitive name, after trimming outer whitespace, reuses one group for this user. Omit it for an independent operation. Keep the name on retries; each calc |
Calculate historical return, volatility, drawdown, risk-adjusted and benchmark-relative statistics from a confirmed portfolio series profile. The metrics parameter describes all available calculations and their required inputs. Use daily, weekly or monthly complete periods; results include coverage, warnings and exact dataset/profile pins. Reuse an idempotency_key only for an identical calculation
| Parameter | Type | Required | Notes |
|---|---|---|---|
| series_profile_id | string | yes | Confirmed portfolio series profile returned by upload or list_portfolio_series; pins one immutable dataset version. |
| metrics | array | yes | Select one or more unique metric names. periodic_returns: Return for each complete period at target_frequency. cumulative_return: Compounded return across the selected complete periods. observation_co |
| target_frequency | string | yes | Calculate complete daily, weekly or monthly return periods. Annualization uses 252, 52 or 12 periods per year respectively; finer-frequency data must be available. |
| idempotency_key | string | yes | — |
| start_date | no | — | |
| end_date | no | — | |
| benchmark_profile_id | no | Confirmed benchmark series profile in the same currency and return basis as the portfolio. Required for beta, alpha, correlation, tracking_error and information_ratio. Returns are matched by exact per | |
| risk_free_rate | no | Required for sharpe and alpha. Use a confirmed risk-free rate profile or a source-backed dated annualized scalar with currency, tenor, compounding and provenance. Do not substitute an assumed rate. | |
| minimum_acceptable_return | no | Required for downside_deviation and sortino. Use a confirmed minimum acceptable return profile or a source-backed dated annualized scalar with currency, tenor, compounding and provenance. | |
| analysis_name | no | Optional private grouping name. The same case-sensitive name, after trimming outer whitespace, reuses one group for this user. Omit it for an independent operation. Keep the name on retries; each calc |
- 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 PortfolioFit or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_analysis_portfolios | no tags | |
| list_portfolio_series | no tags | |
| list_analyses | sensitive-source | sensitive-source: keyword "read_private" |
| get_analysis | no tags | |
| evaluate_portfolio_alignment | state-write | state-write: declares readOnlyHint: false |
| calculate_portfolio_constraints | state-write | state-write: declares readOnlyHint: false |
| upload_portfolio_series_rows | state-write | state-write: declares readOnlyHint: false |
| cancel_portfolio_series_upload | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| review_portfolio_series_profile | state-write | state-write: declares readOnlyHint: false |
| calculate_portfolio_statistics | state-write | state-write: declares readOnlyHint: false |
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
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 0.1.3.
No release note was published with this version.
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.
Any signed-in account that does not publish PortfolioFit can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.