Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Near Hydra 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
3
downloads a day
local
runs on your machine
68
downloads in 30d
What it does
MCP server exposing the NEAR stack (accounts, Chain Signatures, NEAR Intents) as agent tools.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user near-hydra-mcp '--' npx -y near-hydra-mcp
# 2 — ask your agent for something these tools do
# hydra_config_show, hydra_account_view, hydra_contract_view and 18 more
Near Hydra costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NIAll 2 servers
nikshepsvn2 servers
2 categories
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 Near Hydra 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. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user near-hydra-mcp '--' npx -y near-hydra-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 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
21 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.
Show the active near-hydra configuration: network, account, MPC contract, RPC endpoints. Read-only.
No parameter schema on file.
View a NEAR account
No parameter schema on file.
Call a read-only view method on a NEAR smart contract. Returns parsed JSON when possible. Example: hydra_contract_view({contractId:
No parameter schema on file.
Derive a foreign-chain address (Bitcoin, EVM, Solana) from a NEAR account using Chain Signatures (MPC). Same NEAR account + path → same address every time.
No parameter schema on file.
Get the native-asset balance of an address on a foreign chain.
No parameter schema on file.
For a NEAR account, derive its addresses on every supported foreign chain and return all native-asset balances in one call. Errors on individual chains are reported per-chain — partial success is normal.
No parameter schema on file.
List all tokens supported by NEAR Intents 1Click for cross-chain swaps. Each entry includes assetId, blockchain, contractAddress, symbol, decimals, USD price.
No parameter schema on file.
Get a NEAR Intents 1Click cross-chain swap quote. Set dry=true to simulate (no deposit address); dry=false returns a deposit address you must send the input asset to. Asset IDs come from hydra_swap_tokens. Example:
No parameter schema on file.
Check the execution status of a 1Click swap by its deposit address.
No parameter schema on file.
Notify 1Click that the deposit transaction has been broadcast. depositAddress comes from a non-dry quote; txHash is the transaction hash on the chain you sent funds on.
No parameter schema on file.
Send native NEAR from the configured account. SAFE BY DEFAULT: dry=true returns the plan without broadcasting. Set dry=false to actually send. Requires policy.readOnly=false. amountYocto is in yocto (1 NEAR = 10^24 yocto).
No parameter schema on file.
Send a NEP-141 fungible token from the configured account. Calls ft_transfer with 1 yoctoNEAR deposit. SAFE: dry=true by default. Example: send wNEAR via tokenContract=
No parameter schema on file.
Call a state-changing method on a NEAR smart contract from the configured account. SAFE: dry=true by default. depositYocto is attached NEAR; gas is in TGas units (default 30 TGas).
No parameter schema on file.
No parameter schema on file.
Send BTC from a Chain-Signature-derived Bitcoin address. UTXO selection via Mempool API. SAFE: dry=true returns the plan; dry=false signs via MPC and broadcasts. Amount in satoshis (1 BTC = 100,000,000 satoshi). Requires the derived address to have spendable UTXOs.
No parameter schema on file.
Send native SOL from a Chain-Signature-derived Solana address. SAFE: dry=true returns the plan. Amount in lamports (1 SOL = 1,000,000,000 lamports). Requires the derived address to have SOL.
No parameter schema on file.
Send a Solana SPL token from a Chain-Signature-derived Solana address. Auto-derives source + destination ATAs and creates the destination ATA on-the-fly if it doesn
No parameter schema on file.
Mint NEAR function-call access keys scoped to specific contracts (with a NEAR allowance cap) for autonomous agent use. Generates one fresh ed25519 keypair per receiverContract (NEAR
No parameter schema on file.
Sign an arbitrary message (EIP-191
No parameter schema on file.
Top up the derived foreign-chain address with native gas, via a small NEAR Intents 1Click swap. Checks current balance; if below minBalance, swaps a NEAR-side asset (default wNEAR) to the chain
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 Apache-2.0
- 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 Near Hydra 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.5.0 · scanned 14 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 digestb74db497c7a53fa6967aee90f5c377593fba035786b0a5feb2f62cd765c92ad2
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 (21 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 |
|---|---|---|
| hydra_config_show | no tags | |
| hydra_account_view | no tags | |
| hydra_contract_view | no tags | |
| hydra_address_derive | no tags | |
| hydra_address_balance | no tags | |
| hydra_account_balance_all_chains | no tags | |
| hydra_swap_tokens | no tags | |
| hydra_swap_quote | external-sink | external-sink: parameter "recipient" |
| hydra_swap_status | no tags | |
| hydra_swap_submit_deposit | no tags | |
| hydra_send_near | no tags | |
| hydra_send_ft | no tags | |
| hydra_contract_call | no tags | |
| hydra_send_evm | external-sink | external-sink: parameter "recipient" |
| hydra_send_btc | no tags | |
| hydra_send_solana | no tags | |
| hydra_send_spl | no tags | |
| hydra_create_agent_key | no tags | |
| hydra_sign_message | no tags | |
| hydra_ensure_gas | no tags | |
| hydra_swap_execute | untrusted-inputexternal-sink | untrusted-input: keyword "fetch"; external-sink: parameter "recipient" |
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 digestb74db497c7a53fa6
Scanned2026-10-14
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.5.0. Pin a release below and the command asks for exactly that one.
0.5.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 Near Hydra 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.