Nyria
REMOTE · API.NYRIA.IO
Send trade alerts from Claude, Cursor or any MCP client to Nyria Paper or your broker.
Available components
Last scanned (23 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 759 tokens (~108/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- Tool “nyria_preview_alert” rewrote its description, which is the text the model reads security
- Tool “nyria_send_alert” rewrote its description, which is the text the model reads security
- Schema quality: 63 → 108 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: excellent → good functional
- “nyria_preview_alert” reworded the description of “message” cosmetic
- “nyria_send_alert” reworded the description of “message” cosmetic
- 3 Nov 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 30 Oct 26 36
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.nyria.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nyria.io | CN=YE1,O=Let's Encrypt,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 544d6d356fc6769b4935afddd1b8c39e4e8 |
| SANs: *.nyria.io, nyria.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.nyria.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| nyria.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.nyria.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.nyria.io/mcp | HTTPS enforced | 301 | https://api.nyria.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
nyria_list_bots List bots ~37
List bots deployed on your strategy. Shows each bot's broker, account type (live or paper), status, and position size.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nyria_order_status Order status ~71
Look up an order by the order_id from nyria_send_alert or nyria_recent_orders. Shows each bot's order: status, quantity, filled quantity, fill price, broker and account type.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order_id from nyria_send_alert or nyria_recent_orders |
No output schema declared.
No examples provided.
nyria_positions Open positions ~56
Show open positions on each broker account that has a bot on this strategy: account (last 4 digits), instrument, side, filled quantity and average price. Covers positions Nyria opened; trades placed outside Nyria are not listed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nyria_preview_alert Preview trade alert ~134
Parse a trade alert without placing any orders. Use this to verify your alert message will be interpreted correctly before sending it live. JSON alerts with order keys (order_type, stop_price, limit_price, trail_percent, trail_amount, stop_loss, stop_loss_limit, take_profit, percent, bots) and the FLATTEN action are read the same way. Stop loss and take profit are for stocks, ETFs and options only. Percent closes are for stocks, ETFs and crypto only.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The alert message to preview. A JSON alert may carry the same order keys as nyria_send_alert. |
No output schema declared.
No examples provided.
nyria_recent_orders Recent orders ~60
View recent orders placed through your strategy. Shows order_id, instrument, action, status, quantity, price, and timestamp. Pass an order_id to nyria_order_status for its fill.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of orders to return |
No output schema declared.
No examples provided.
nyria_send_alert Send trade alert ~372
Send a trade alert to your Nyria strategy. The alert is parsed and forwarded to every bot on the strategy. If the strategy has live bots, this places real orders in your broker account, exactly like the webhook; the alert also reaches accounts that copy the strategy. Preview first when unsure. Alerts cannot set position size on entries (the bot controls sizing); an exit may close a share of the position with "percent", above 0 to 100. Stop orders are attached only when a JSON alert carries them (see the message field). The reply lists an order_id per order leg; pass it to nyria_order_status to see each bot's fill.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The alert message, e.g. 'BUY AAPL' or 'SELL TO CLOSE SPY 450C 12/20'. A JSON alert may add order keys: order_type (market, limit, stop, stop_limit, trailing_stop), stop_price, limit_price, trail_perc… |
No output schema declared.
No examples provided.
nyria_strategy_info Strategy info ~29
Show the strategy this connection sends to: name, status, equity type and active bot count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Nyria MCP server?
Nyria is a hosted endpoint at https://api.nyria.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.nyria.io
claude mcp add --transport http nyria-llc-nyria 'https://api.nyria.io/mcp'
What is the Nyria MCP server?
Nyria is an MCP server listed in the public MCP registry as io.github.Nyria-LLC/nyria. Send trade alerts from Claude, Cursor or any MCP client to Nyria Paper or your broker. This page covers its hosted endpoint (https://api.nyria.io/mcp).
Is the Nyria MCP server safe to use?
Nyria scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Nyria MCP server expose?
Nyria exposes 7 tools: nyria_send_alert, nyria_preview_alert, nyria_strategy_info, nyria_recent_orders, nyria_list_bots, and 2 more. Their descriptions and schemas cost roughly 759 tokens of context every time the server is loaded.
Does the Nyria MCP server require authentication?
Yes. Nyria asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Nyria MCP server still maintained?
Nyria is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.