Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Manawa Terminal

REMOTE · MCP.MANAWA.APP

Live market data, financial analysis, and portfolio research tools across 10,000+ tickers.

Available components

+1 this week 89 Trust /100

Last scanned (13 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security91
Transport & Reachability100
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 12884 tokens (~243/item across 53 items; 52 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability check failed: schema churn in the 30 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 12 additions. See how to fix → Fail
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 23% of tool parameters carry a description.Partial
  • Structured output schemas are declared (98% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 54 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 92 to 93.

  • 17 Nov 26 0
    • Schema quality: 11482 → 12884 ▼ functional
    • New tool “get_portfolio_covered_call_yield” functional
    • New tool “get_portfolio_crowding” functional
    • New tool “get_portfolio_fund_overlap” functional
    • New tool “get_portfolio_hedge_cost” functional
    • New tool “get_portfolio_rate_sensitivity” functional
    • New tool “get_portfolio_signal_alerts” functional
  • 6 Nov 26 −2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 31 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “finance_search” rewrote its description, which is the text the model reads security
    • Schema quality: 202 → 236 ▼ functional
    • Tool coverage: 2% → 24% ▲ functional
    • “cancel_order” added an optional parameter “strategy_id” cosmetic
    • “create_alert” added an optional parameter “strategy_id” cosmetic
    • “create_library_folder” added an optional parameter “strategy_id” cosmetic
    • “create_library_item” added an optional parameter “strategy_id” cosmetic
    • “create_portfolio” added an optional parameter “strategy_id” cosmetic
    • “create_screener” added an optional parameter “strategy_id” cosmetic
    • “create_watchlist” added an optional parameter “strategy_id” cosmetic
    • “delete_alert” added an optional parameter “strategy_id” cosmetic
    • “delete_library_folder” added an optional parameter “strategy_id” cosmetic
    • “delete_library_item” added an optional parameter “strategy_id” cosmetic
    • “delete_screener” added an optional parameter “strategy_id” cosmetic
    • “earnings_rag” added an optional parameter “strategy_id” cosmetic
    • “edit_order” added an optional parameter “strategy_id” cosmetic
    • “get_journal_entry” added an optional parameter “strategy_id” cosmetic
    • “get_library_item” added an optional parameter “strategy_id” cosmetic
    • “get_notifications” added an optional parameter “strategy_id” cosmetic
    • “get_portfolio_rules” added an optional parameter “strategy_id” cosmetic
    • “get_portfolio_statistics” added an optional parameter “strategy_id” cosmetic
    • “get_positions” added an optional parameter “strategy_id” cosmetic
    • “list_alerts” added an optional parameter “strategy_id” cosmetic
    • “list_journal” added an optional parameter “strategy_id” cosmetic
    • “list_library_folders” added an optional parameter “strategy_id” cosmetic
    • “list_library_item_versions” added an optional parameter “strategy_id” cosmetic
    • “list_library_items” added an optional parameter “strategy_id” cosmetic
    • “list_portfolios” added an optional parameter “strategy_id” cosmetic
    • “list_screeners” added an optional parameter “strategy_id” cosmetic
    • “list_strategies” added an optional parameter “strategy_id” cosmetic
    • “list_watchlists” added an optional parameter “strategy_id” cosmetic
    • “marketing_graphics” added an optional parameter “strategy_id” cosmetic
    • “marketing_inbox” added an optional parameter “strategy_id” cosmetic
    • “marketing_render” added an optional parameter “strategy_id” cosmetic
    • “move_library_folder” added an optional parameter “strategy_id” cosmetic
    • “move_library_item” added an optional parameter “strategy_id” cosmetic
    • “rename_library_folder” added an optional parameter “strategy_id” cosmetic
    • “report_bug” added an optional parameter “strategy_id” cosmetic
    • “run_deepdive” added an optional parameter “strategy_id” cosmetic
    • “run_screener” added an optional parameter “strategy_id” cosmetic
    • “search_library” added an optional parameter “strategy_id” cosmetic
    • “submit_journal_draft” added an optional parameter “strategy_id” cosmetic
    • “update_library_item” added an optional parameter “strategy_id” cosmetic
    • “update_screener” added an optional parameter “strategy_id” cosmetic
    • “update_watchlist” added an optional parameter “strategy_id” cosmetic
  • 28 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “add_transaction” rewrote its description, which is the text the model reads security
    • Tool “finance_search” rewrote its description, which is the text the model reads security
    • Tool “get_strategy” rewrote its description, which is the text the model reads security
    • New tool “tag_activity” functional
    • “add_transaction” added an optional parameter “strategy_id” cosmetic
    • “finance_search” added an optional parameter “strategy_id” cosmetic
  • 25 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “finance_search” rewrote its description, which is the text the model reads security
Diagnostics

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 21 Nov 2026 · Probed https://mcp.manawa.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.manawa.app CN=WR3,O=Google Trust Services,C=US 7 Nov 2026 5 Feb 2027 RSA 2048 SHA256-RSA 1ec90c131e5f00210a95bac8e3033ef7
SANs: mcp.manawa.app
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.manawa.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
manawa.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="Manawa MCP", resource_metadata="https://mcp.manawa.app/.well-known/oauth-protected-resource"

Bearer realm="Manawa MCP", resource_metadata="https://mcp.manawa.app/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://mcp.manawa.app/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.manawa.app/mcp
Authorisation server https://mcp.manawa.app

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.manawa.app/mcp Verified 200
http (plaintext) http://mcp.manawa.app/mcp HTTPS enforced 302 https://mcp.manawa.app/mcp
MCP tools · 52 exposed · ~9,987 tokens

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 →

Tool Tokens
update_screener ~187

Update a saved screener's name, query, schedule, or baseline symbols. Args: screener_id: The screener UUID from list_screeners name: New name (optional) query: Updated filter blob (optional) schedule: "off", "daily", or "weekly" (optional; weekly requires Pro) notify_on_change: Toggle enter/exit notifies (optional) last_symbols: Refresh enter/exit baseline from the live table (optional)

NameTypeReqDescription
last_symbols–––
name–––
notify_on_change–––
query–––
schedule–––
screener_idstringyes–
strategy_id––Strategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.
NameTypeReqDescription
resultstringyes–

No examples provided.

update_watchlist ~109

Update a watchlist's name and/or symbols. Args: watchlist_id: The watchlist UUID name: New name (optional) symbols: Updated list of symbols (optional)

NameTypeReqDescription
name–––
strategy_id––Strategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.
symbols–––
watchlist_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the Manawa Terminal MCP server?

Manawa Terminal is a hosted endpoint at https://mcp.manawa.app/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 · mcp.manawa.app

# add to Claude Code
claude mcp add --transport http app-manawa-manawa-terminal 'https://mcp.manawa.app/mcp'
Common questions

What is the Manawa Terminal MCP server?

Manawa Terminal is an MCP server listed in the public MCP registry as app.manawa/manawa-terminal. Live market data, financial analysis, and portfolio research tools across 10,000+ tickers. This page covers its hosted endpoint (https://mcp.manawa.app/mcp).

Is the Manawa Terminal MCP server safe to use?

Manawa Terminal scores 89 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 Manawa Terminal MCP server expose?

Manawa Terminal exposes 52 tools: finance_search, earnings_rag, list_watchlists, create_watchlist, update_watchlist, and 47 more. Their descriptions and schemas cost roughly 9,987 tokens of context every time the server is loaded.

Does the Manawa Terminal MCP server require authentication?

Yes. Manawa Terminal 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 Manawa Terminal MCP server still maintained?

Manawa Terminal is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Manawa Terminal MCP server?

VerifyMCP ran 14 checks on Manawa Terminal, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.