ai.marketintell/marketintell
REMOTE · API.MARKETINTELL.AI · 3 COMPONENTS · SCANNED SEP 20
AI analyst desk for stocks, options & crypto with sourced trade setups and a public accuracy record.
Available components
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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 Usability84
- 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
- Tool/resource definitions use about 1861 tokens (~97/item across 19 items; 17 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 2 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_list_intents" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 19 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
How do I install the ai.marketintell/marketintell MCP server?
ai.marketintell/marketintell is a hosted endpoint at https://api.marketintell.ai/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.marketintell.ai
claude mcp add --transport http ai-marketintell-marketintell 'https://api.marketintell.ai/mcp'
{
"mcpServers": {
"ai-marketintell-marketintell": {
"url": "https://api.marketintell.ai/mcp"
}
}
} {
"servers": {
"ai-marketintell-marketintell": {
"type": "http",
"url": "https://api.marketintell.ai/mcp"
}
}
} [mcp_servers.ai-marketintell-marketintell] url = "https://api.marketintell.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-marketintell-marketintell": {
"type": "remote",
"url": "https://api.marketintell.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-marketintell-marketintell --url 'https://api.marketintell.ai/mcp' --transport streamable-http
mcp_servers:
ai-marketintell-marketintell:
url: "https://api.marketintell.ai/mcp" {
"McpServers": {
"ai-marketintell-marketintell": {
"Transport": "http",
"Url": "https://api.marketintell.ai/mcp"
}
}
} assistant mcp add ai-marketintell-marketintell -t streamable-http -u 'https://api.marketintell.ai/mcp'
{
"mcpServers": {
"ai-marketintell-marketintell": {
"type": "http",
"url": "https://api.marketintell.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 20 Sept 2026 · Probed https://api.marketintell.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=marketintell.ai | CN=YE2,O=Let's Encrypt,C=US | 28 Aug 2026 | 26 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6d3cd568e0dd96fc14bd64ad2a35a7a1816 |
| SANs: *.marketintell.ai, marketintell.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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.marketintell.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| marketintell.ai. | absent | 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 resource_metadata="https://api.marketintell.ai/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://api.marketintell.ai/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Protected resource metadata
| Document | https://api.marketintell.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.marketintell.ai |
| Authorisation server | https://api.marketintell.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.marketintell.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.marketintell.ai/mcp | HTTPS enforced | 301 | https://api.marketintell.ai/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 →
alpha_signals ~129
Fetch recent alpha signals — automated market intelligence. Crypto signals every ~10 min; equities (Beta) every ~30 min during US market hours. Filter by domain to narrow.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Filter by asset domain. Omit to return all domains mixed. |
| include_execution | boolean | – | When true, inline venue/precision metadata (venue, venue_symbol, max_leverage, sz_decimals) on each signal's setup so you can place an order without a second tokens lookup. |
| limit | integer | – | Number of signals to return (1-50, default 10) |
No output schema declared.
No examples provided.
billing_status ~38
Return the authenticated key's plan, daily quota usage, monthly LLM-cost-cents, and cap. Mirrors GET /v1/billing/status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chat ~208
Run a query through MarketIntell's brain (auto-routes to T1 fast agent or T2 CoT pipeline based on intent). Returns synthesized analysis with citations and trade setup when relevant.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Asset domain override — bypasses the auto-classifier. |
| include_facts | boolean | – | When true, attach fact_projection (neutral Fact[] + thesis) to the result. Default off. |
| include_portfolio | boolean | – | Force auto-load (true) or opt out (false) of the caller's default portfolio for this turn. |
| portfolio_id | string | – | Explicit portfolio override for portfolio-aware chat. |
| query | string | yes | Natural language query, e.g. 'Should I long BTC?', 'What caused ETH to dump?' |
| response_format | object | – | Structured-output control — mirrors REST /v1/chat response_format. |
| session_id | string | – | Optional UUID of an existing chat session to continue. Omit to start a new session. |
No output schema declared.
No examples provided.
chat_deep ~206
Run a query through MarketIntell's T3 supervisor — parallel specialists across technical/derivatives/macro/social/onchain/etc. plus synthesis. Slower (~25-40s) and costlier than `chat`. Pro tier only.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Asset domain override — bypasses the auto-classifier. |
| include_facts | boolean | – | When true, attach fact_projection (neutral Fact[] + thesis) to the result. Default off. |
| include_portfolio | boolean | – | Force auto-load (true) or opt out (false) of the caller's default portfolio for this turn. |
| portfolio_id | string | – | Explicit portfolio override for portfolio-aware chat. |
| query | string | yes | Multi-perspective query, e.g. 'Full breakdown of ETH', 'Compare BTC vs ETH vs SOL across all angles' |
| response_format | object | – | Structured-output control — mirrors REST /v1/chat response_format. |
| session_id | string | – | – |
No output schema declared.
No examples provided.
execute_approve_intent ~84
Approve a pending trade intent and place the order at the broker. Returns the executed_order audit row. Requires `trade` scope.
| Name | Type | Req | Description |
|---|---|---|---|
| intent_id | string | yes | UUID of a pending trade intent owned by the caller |
| notional_cents | integer | – | Override notional at approval time |
| qty | number | – | Override qty at approval time |
No output schema declared.
No examples provided.
execute_list_intents ~44
List the caller's recent trade intents (pending, executed, rejected). Requires `trade` scope.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
execute_propose_intent ~228
Propose a trade intent to the user's connected broker. Writes a pending row the user reviews + approves. Requires `trade` scope. Use this when an agent wants to act on a signal without placing the order itself.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_class | string | yes | Asset class — must match the broker's supportedAssetClasses |
| confidence | number | yes | Your confidence 0-1 |
| limit_price | number | – | – |
| notional_cents | integer | – | USD cents notional (preferred sizing — broker converts to qty) |
| order_type | string | – | – |
| qty | number | – | Per-share / per-token qty (alternative to notional) |
| reasoning | string | yes | Plain-English rationale, surfaced to the user when they review the intent |
| side | string | yes | Direction |
| signal_id | string | – | MarketIntell TradeSignal ID, if this is acting on one |
| stop_price | number | – | – |
| symbol | string | yes | Ticker / token, e.g. AAPL or BTC |
| take_profits | array | – | – |
No output schema declared.
No examples provided.
execute_read_portfolio ~44
Read the caller's connected broker account snapshot — equity, cash, buying power, open positions. Requires `trade` scope.
| Name | Type | Req | Description |
|---|---|---|---|
| broker_connection_id | string | – | – |
No output schema declared.
No examples provided.
health ~26
MarketIntell system health — uptime, cache stats, memory, provider circuit-breaker states.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
portfolio_analyze ~55
Compute PnL + risk assessment for a portfolio you own. Returns per-holding pnl, risk_assessment, and top_risks.
| Name | Type | Req | Description |
|---|---|---|---|
| portfolio_id | string | yes | Portfolio ID returned by portfolio_create or portfolio_list |
No output schema declared.
No examples provided.
portfolio_create ~57
Create a new portfolio for the authenticated key. Holdings are token symbol + amount (+ optional entry_price and notes).
| Name | Type | Req | Description |
|---|---|---|---|
| holdings | array | yes | – |
| name | string | yes | Display name, e.g. 'Main', 'Tax-loss harvest' |
No output schema declared.
No examples provided.
portfolio_list ~26
List all portfolios owned by the authenticated key. Returns id, name, holdings, timestamps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register ~118
Step 2 of MCP self-signup. Submit the challenge id + solved nonce to provision a fresh Free-tier API key. The key is shown ONCE — store it. Pro upgrades go through Stripe checkout; this tool only issues Free keys.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_id | string | yes | ID returned by register_challenge. |
| name | string | yes | Human-readable label for the new key, e.g. 'Claude Desktop on my laptop'. Shown in the keys admin UI. |
| nonce | string | yes | Nonce that satisfies the proof-of-work constraint. |
No output schema declared.
No examples provided.
register_challenge ~90
Step 1 of MCP self-signup. Returns a proof-of-work challenge. Solve locally (find a nonce whose sha256 has the required leading zero hex chars), then call `register` with { challenge_id, nonce, name }.
| Name | Type | Req | Description |
|---|---|---|---|
| difficulty | integer | – | Optional override (1-8). Default comes from POW_DIFFICULTY env (typically 5 ≈ 5s solve). |
No output schema declared.
No examples provided.
screener ~76
Token screening — find trending tokens, top gainers, and top losers. Use this to discover what's moving in the market right now.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | 'trending' (hot tokens), 'gainers' (top 24h gainers), 'losers' (top 24h losers), or 'all' |
No output schema declared.
No examples provided.
sessions_list ~38
List the authenticated key's recent chat sessions. Useful to resume prior conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max sessions to return (1-100) |
No output schema declared.
No examples provided.
signal_performance ~93
Realized signal accuracy — rolling 30-day win rate over CLOSED trade signals, where a win is a real take-profit / in-profit expiry (net positive after fees & leverage) and a loss is a real stop-loss / losing expiry. Win-rate is over resolved signals only; flat (break-even) and cancelled/no-fill/ambiguous signals are reported but excluded from the rate. Broken down by timeframe and direction.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the ai.marketintell/marketintell MCP server?
ai.marketintell/marketintell is an MCP server listed in the public MCP registry as ai.marketintell/marketintell. AI analyst desk for stocks, options & crypto with sourced trade setups and a public accuracy record. This page covers its hosted endpoint (https://api.marketintell.ai/mcp).
Is the ai.marketintell/marketintell MCP server safe to use?
ai.marketintell/marketintell scores 95 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 ai.marketintell/marketintell MCP server expose?
ai.marketintell/marketintell exposes 17 tools: chat, chat_deep, alpha_signals, signal_performance, screener, and 12 more. Their descriptions and schemas cost roughly 1,560 tokens of context every time the server is loaded.
Does the ai.marketintell/marketintell MCP server require authentication?
Yes. ai.marketintell/marketintell 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 ai.marketintell/marketintell MCP server still maintained?
ai.marketintell/marketintell is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.