Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
PolySignals.net 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
Live crypto Buy/Sell/Hold readings from prediction markets and options, plus daily trend calls.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http polysignals-net-mcp https://polysignals.net/api/mcp
# 2 — ask your agent for something these tools do
# get_overview, get_coin_signal, get_regime and 7 more
PolySignals.net costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
POAll 1 server
polysignals1 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 polysignals-net-mcp https://polysignals.net/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.
Every tracked coin in one table: spot price, the overall Buy/Sell/Hold call with score and confidence, the 1 hour window, and the daily regime call (long or flat).
No parameter schema on file.
One coin in full: the overall call, each window running now (5m, 15m, 1h, 4h, 1d) blended across venues with score, up probability, confidence and the move since the window opened, the next windows, each venue's own reading, the daily regime call, the Cryptohopper markets that get its signals and its latest delivery, the live backtest, and the newest headlines that name it. Pass timeframe to narro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | yes | Coin ticker or name as on the site, for example BTC, ETH or SOL |
| timeframe | string | no | Only this window |
The daily regime (trend) rule relayed to Cryptohopper: long while the Coinbase daily close is more than one 20-day sigma above its 50-day average, flat once more than one below. Without a coin: the board for every coin; with a coin: its call, distance, days in state and the close that would change it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | no | Coin ticker or name as on the site, for example BTC, ETH or SOL |
The coins whose daily trend (regime) call changed, newest decision first: turned long (sent to Cryptohopper as a buy signal) or turned flat (a sell), decided at 00:05 UTC on the daily close, plus the next decision time, the coins whose live price is closest to the level that would change their call, how many Cryptohopper markets accepted each recent signal, and how many coins were long after each
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Decisions to list |
| coin | string | no | Only this coin, for example SOL: its current trend call and when it last changed |
Which exchange markets on Cryptohopper receive the daily trend signals (buy when a coin turns long, sell when it turns flat), in each exchange's own market format such as BTCUSDT, XBT/EUR or BTC-USD. Without arguments: every exchange with its coin and market counts; with exchange: its markets per coin; with coin: that coin's markets on every exchange; with both: that one list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | no | Only this coin, for example SOL |
| exchange | string | no | Cryptohopper exchange by name or key, for example Binance, Kraken, OKX, Coinbase or kraken2 |
What following the calls would have returned, trading the coin against USD on Coinbase with fees, next to buy and hold: net and gross return, round trips, win rate, drawdown and the current position. Without a coin: one strategy (default: the daily regime) for every coin; with a coin: all eight strategies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | no | Coin ticker or name as on the site, for example BTC, ETH or SOL |
| strategy | string | no | Default regime; ignored when a coin is given |
The blended reading of one coin's window over the last hours (up to 48), thinned to about 36 rows: time, up probability, score and confidence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | yes | Coin ticker or name as on the site, for example BTC, ETH or SOL |
| timeframe | string | no | — |
| hours | integer | no | — |
Which coins have venue readings, the windows, and each venue with its type and how many coins it covers.
No parameter schema on file.
The methodology document: what the score is, confidence, window matching, options readings, the backtest and the daily regime rule. Without a section: the list of sections and the introduction; with one: that section.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section | string | no | A section title or part of one, for example 'confidence' or 'regime' |
The latest crypto headlines from CoinArticle, newest first, each with the live overall Buy/Sell/Hold call of every tracked coin it names. Pass coin to keep only headlines that name it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | no | Only headlines naming this coin |
| limit | integer | no | — |
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 PolySignals.net 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.0.0 · scanned 30 Oct 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 digest2044ecfbb6ff731e246d8316e0a7db5ec79505d429b5eedad309731b11f1cfec
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 |
|---|---|---|
| get_overview | no tags | |
| get_coin_signal | no tags | |
| get_regime | no tags | |
| get_trend_changes | no tags | |
| get_signal_markets | no tags | |
| get_results | no tags | |
| get_history | no tags | |
| list_coins_and_venues | no tags | |
| get_methodology | no tags | |
| get_news | 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 digest2044ecfbb6ff731e
Scanned2026-10-30
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.0.0.
1.0.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 PolySignals.net 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.