Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Research 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
trust score
18
downloads a day
local
runs on your machine
874
downloads in 30d
What it does
Search recorded crypto and TradFi microstructure through the EdgeDepth Research API as deterministic MCP tools.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'EDGEDEPTH_API_KEY=${EDGEDEPTH_API_KEY}' --transport stdio research-mcp '--' npx -y @edgedepth/research-mcp
# 2 — ask your agent for something these tools do
# list_features, list_instruments, resolve_scope and 25 more
It needs EDGEDEPTH_API_KEY: this reads it from your environment, so export it first.
Research costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
EDAll 1 server
@edgedepth1 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. This one runs on your machine: your client starts Research as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads EDGEDEPTH_API_KEY (Required for the stdio package. Hosted remote clients use browser OAuth instead) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx EDGEDEPTH_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'EDGEDEPTH_API_KEY=${EDGEDEPTH_API_KEY}' --transport stdio research-mcp '--' npx -y @edgedepth/research-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: EDGEDEPTH_API_KEY — Required for the stdio package. Hosted remote clients use browser OAuth instead.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
28 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.
Use this when you need the valid EdgeDepth query grammar, supported feature ids,
No parameter schema on file.
Use this when you need to verify supported symbols, recorded coverage, data availability,
No parameter schema on file.
Use this when a pointed move or symbol needs an explicit sector population. Do not use it to authorize computation or infer historical membership. Returns recorded sector choices, the exact eligible Binance crypto perpetual roster, coverage and membership limitations. Missing, ambiguous, thin or…
No parameter schema on file.
Use this when preparing a setup-first study. Interpret the user text/image in the host, then submit structured intent here. Deterministic validation, canonical definition, provenance and fresh allowance estimate; no LLM, scan or charge. Propose assumptions explicitly, preserve reached versus…
No parameter schema on file.
Use this when raw-prose clients need fallback interpretation or the host cannot construct structured intent.
No parameter schema on file.
Use this when an exact research_query.v2 document has been confirmed and the user wants
No parameter schema on file.
Use this when a prior run_scan returned an opaque page cursor and more occurrence rows are
No parameter schema on file.
Use this when you need the recorded feature values, window aggregates, and fired rulebook
No parameter schema on file.
Use this when the user asks how common one exact condition was across eligible
No parameter schema on file.
Use this when the user wants an existing versioned investigation by its SHA256 id. Compact by default; full=true restores pinned input observations. Deterministic descriptive metrics, exact event/as-of bounds, contradictions and missing analyses come from the same API as the web. No model call,…
No parameter schema on file.
Use this when the user wants the saved interpretation of a move by publication id. Returns the same explanation, supporting and challenging evidence, alternatives, next checks, exact market/window/as-of, source revisions and evidence gaps used by web pages and channel drafts. Optional edition pins…
No parameter schema on file.
Use this when the user supplied at least two exact historical moments and wants the
No parameter schema on file.
Use this when the user wants to list citable public EdgeDepth reports or retrieve one by
No parameter schema on file.
Use this when an exact where-only research_query.v2 document has been confirmed and the
No parameter schema on file.
Use this when the user asks whether an approved setup was profitable under explicit trade rules. This is separate from descriptive run_scan outcomes.
No parameter schema on file.
Use this when the user wants to test whether the outcome distribution of one confirmed
No parameter schema on file.
Use this when the user starts from an OUTCOME (a move of a stated size, in a stated
No parameter schema on file.
Use this when reading your saved hypothesis or original observation. Do not use for general market scans or other accounts. Private Radar admin pilot. With id, read the account-owned saved definition, all attempted variants, counts, failures and supporting/contradictory examples. With event, read…
No parameter schema on file.
Use this when proposing a bounded Radar hypothesis comparison. Do not use to execute or validate a strategy. Free deterministic preparation for the private Radar admin pilot. Supply the exact event and draft, plus existing id when revisiting. Returns an unrun proposal with exact four requests,…
No parameter schema on file.
Use this when the user asks to save a hypothesis or decision. Do not use to run studies, delete history or change alerts. Requires explicit user intent to save and optional research:hypotheses permission, plus Radar admin access. Save the draft or Test/Keep/Reject decision at the known revision (0…
No parameter schema on file.
Use this when executing the next request of an explicitly approved hypothesis comparison. Do not use to search combinations, open evaluation or retry unknown work. Requires research:read and research:hypotheses plus private Radar admin access. Only after human approval of the exact…
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Research 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: —
ATrust score 96 / 100
Release 0.12.0 · scanned 15 Oct 2026
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 · 1 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest0d2742fc7d8855b18ea3739a03749287d6671d28fb513b6ea73fab4234cfc03c
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (28 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| get_hypothesis | no tags | |
| prepare_hypothesis | no tags | |
| save_hypothesis | state-write | state-write: declares readOnlyHint: false |
| run_hypothesis | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| ground_screenshots | no tags | |
| investigate_move | no tags | |
| get_strategy | no tags | |
| prepare_strategy | external-sink | external-sink: handler sends an HTTP POST (request({ method: 'POST', path: '/strategies/estimate', key: ctx.getKey(), body: input }) at dist/strategies.js:31 |
| save_strategy | state-writeexternal-sink | state-write: declares readOnlyHint: false; external-sink: handler sends an HTTP POST (request({ method: 'POST', path: '/strategies/save', key: ctx.getKey(), body: input }) at dist/strategies.js:36 |
| run_strategy | state-writeexternal-sink | state-write: declares readOnlyHint: false, destructiveHint: true; external-sink: handler sends an HTTP POST (request({ method: 'POST', path: '/strategies/run', key: ctx.getKey(), body: input }) at dist/strategies.js:41 |
| cancel_strategy | state-writeexternal-sink | state-write: declares readOnlyHint: false; external-sink: handler sends an HTTP POST (request({ method: 'POST', path: '/strategies/cancel', key: ctx.getKey(), body: input }) at dist/strategies.js:46 |
| list_features | no tags | |
| list_instruments | no tags | |
| resolve_scope | no tags | |
| prepare_study | no tags | |
| interpret_prose | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| run_scan | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| next_page | no tags | |
| snapshot_at | no tags | |
| base_rate | no tags | |
| get_investigation_bundle | no tags | |
| get_investigation_assessment | no tags | |
| commonality | no tags | |
| get_report | no tags | |
| run_cohort | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| run_trade_test | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| run_stratified | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| outcome_first | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest0d2742fc7d8855b1
Scanned2026-10-15
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.12.0. Pin a release below and the command asks for exactly that one.
0.12.0
13 Oct 2026
latestNo release note was published with this version.
0.11.0
6 Oct 2026
No release note was published with this version.
0.9.0
14 Sep 2026
No release note was published with this version.
0.8.1
10 Sep 2026
No release note was published with this version.
0.8.0
9 Sep 2026
No release note was published with this version.
0.6.2
6 Sep 2026
No release note was published with this version.
0.6.1
5 Sep 2026
No release note was published with this version.
0.3.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Research 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.