AI Rook Hosted MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track changes to AI Rook's hosted MCP tools and x402/payment disclosures independently of the unresolved npm package.

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Hosted AI Rook MCP endpoint for paid trading intelligence and other agent commerce services; verify the live tool catalog before granting payment authority.

What we know

Operator advertises a hosted MCP tools surface associated with the AI Rook x402 commerce platform. Its catalog includes trading signals, market data, model analysis and other paid endpoints. The direct MCP tool-to-API mapping, transport authentication and whether MCP itself can initiate settlement were not established sufficiently to claim wallet custody or trading execution.

Maintenance / activity evidence

The owner-reviewed current first-party product exposes the hosted MCP endpoint and its documented MCP tool surface with x402/payment behavior.

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Hosted tools potentially access market analysis and pay-per-call APIs; exact tool authority unconfirmed. Complete write authority is not verified.
Authentication not yet verified.
Sensitive access: Trading strategies and wallet addresses if submitted, Potential x402 payment proofs

Paid financial intelligence surface; exact hosted MCP payment and mutation authority unresolved.
Do not equate API escrow endpoints with MCP tool availability.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Has the hosted tool surface or x402/payment behavior changed enough to update the tracking disclosure?

The explicit owner-reviewed correction approves accurately scoped public tracking of AI Rook hosted MCP; this is neither installation safety nor security certification.

Paid financial intelligence surface; exact hosted MCP payment and mutation authority unresolved.
Do not equate API escrow endpoints with MCP tool availability.
Hosted tools potentially access market analysis and pay-per-call APIs; exact tool authority unconfirmed.
Market/analysis prompts and payment metadata may reach the hosted provider; specific MCP retention unknown.
Sensitive access: Trading strategies and wallet addresses if submitted, Potential x402 payment proofs
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime, dependency vulnerabilities, installation readiness and complete tool permissions were not independently audited in Phase E.
The hosted MCP's documented x402/payment behavior remains an operational risk; npm package equivalence is not established.
No higher-tier recommendation, production-readiness claim, installation certification or complete client/tool audit is supplied.
direct hosted MCP tools/list and auth
MCP payment handshake and wallet custody
hosted MCP write/transaction authority
retention policy
The hosted endpoint is a distinct admitted identity: do not bind excluded npm/ai-rook-trading-mcp as equivalent.
MCP tools list and endpoint-specific authentication still need live first-party verification.
x402 platform API payment flows do not prove the hosted MCP holds private keys or can execute trades.
Trading signals are not guaranteed investment outcomes; downstream calls can incur costs.
Owner-corrected hosted endpoint identity; unrelated excluded npm package must not be rebound.

Original activity observations

The owner-reviewed current first-party product exposes the hosted MCP endpoint and its documented MCP tool surface with x402/payment behavior.

Technical identity

endpoint:https://agents.ai-rook.com/mcp

Exact implementation source: https://agents.ai-rook.com/mcp ↗
Reviewed resource type: Gateway
Service endpoint: https://agents.ai-rook.com/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Evidence source ↗
agents.ai-rook.com/mcp
Source material retained for this review.
Evidence source ↗
agents.ai-rook.com/mcp/tools
Source material retained for this review.
Evidence source ↗
agents.ai-rook.com/
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
agents.ai-rook.com/llms.txt
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
ai-rook.com/llms.txt
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Self-hosted gateway service setup

Publisher instructions.

Source evidence observed Oct 13, 2026.

Documentation entry — installation instructions still need review.

Documentation / current availability
Publisher instructions
Publisher website currently documents x402 APIs, not a verified MCP client registration. Do not copy a guessed endpoint configuration.
Configure / authenticate
Publisher instructions
AI Rook site documents x402 pay-per-call APIs and Base USDC; no verified MCP client installation or credential/header specification for /mcp was found. Do not conflate the REST/x402 quickstart with an MCP handshake.
Check connection
Suggested check
Review the vendor service documentation for current MCP integration before attempting a connection.
Remove / uninstall / revoke
MCP100 setup guide
No verified MCP client registration was documented for the Radar /mcp URL. There is nothing to uninstall from these instructions; if the user previously configured this endpoint, remove THAT entry in their own client without triggering x402 payments.
Unknown for the supplied /mcp identity. Treat any x402 payment authorization separately; do not assume bearer keys exist or trigger payments.

Official Documentation & Sources

What it does

Operator advertises a hosted MCP tools surface associated with the AI Rook x402 commerce platform. Its catalog includes trading signals, market data, model analysis and other paid endpoints. The direct MCP tool-to-API mapping, transport authentication and whether MCP itself can initiate settlement were not established sufficiently to claim wallet custody or trading execution.

Capability: Finance & Payments
Resource type: Gateway
Industry: Financial Services & Investing
Best fit: Hosted AI Rook MCP endpoint for paid trading intelligence and other agent commerce services; verify the live tool catalog before granting payment authority.

Representative uses

Explore live hosted tools for market pulse, trade idea and order flow
Request trading analysis or market research where exposed by live MCP
Inspect advertised paid endpoint capabilities and per-call costs

Limitations

The hosted endpoint is a distinct admitted identity: do not bind excluded npm/ai-rook-trading-mcp as equivalent.
MCP tools list and endpoint-specific authentication still need live first-party verification.
x402 platform API payment flows do not prove the hosted MCP holds private keys or can execute trades.
Trading signals are not guaranteed investment outcomes; downstream calls can incur costs.
Owner-corrected hosted endpoint identity; unrelated excluded npm package must not be rebound.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Hosted tools potentially access market analysis and pay-per-call APIs; exact tool authority unconfirmed.
Data handling: Market/analysis prompts and payment metadata may reach the hosted provider; specific MCP retention unknown.
Cost: pay_per_call_x402
Risk and cautions: Paid financial intelligence surface; exact hosted MCP payment and mutation authority unresolved.

Access scope and cautions

Write actions: Not verified
Sensitive access: Trading strategies and wallet addresses if submitted Potential x402 payment proofs
Risk level: high
Security notes: Do not equate API escrow endpoints with MCP tool availability.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which implementation does this page cover?

This page covers the recorded endpoint https://agents.ai-rook.com/mcp. The hosted endpoint is a distinct implementation identity, separate from npm/ai-rook-trading-mcp.

What connection information is established, and what remains unverified?

A complete connection procedure is not verified. Recorded endpoint: https://agents.ai-rook.com/mcp. Recorded transport: streamable_http. Client notes: Do not add a wallet key or payment configuration without endpoint-specific documentation. These facts do not supply missing installation commands, credentials or a verified authentication procedure.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Hosted tools potentially access market analysis and pay-per-call APIs; exact tool authority unconfirmed.

What data-handling boundary should I consider?

Market/analysis prompts and payment metadata may reach the hosted provider; specific MCP retention unknown. Recorded sensitive-access context: Trading strategies and wallet addresses if submitted; Potential x402 payment proofs.

What limitations and risks should I check before use?

Paid financial intelligence surface; exact hosted MCP payment and mutation authority unresolved. The hosted endpoint is a distinct implementation identity, separate from npm/ai-rook-trading-mcp. MCP tools list and endpoint-specific authentication still need live first-party verification. x402 platform API payment flows do not prove the hosted MCP holds private keys or can execute trades. Trading signals are not guaranteed investment outcomes; downstream calls can incur costs. Do not equate API escrow endpoints with MCP tool availability. Runtime, dependency vulnerabilities, installation readiness and complete tool permissions were not independently audited. The hosted MCP's documented x402/payment behavior remains an operational risk; npm package equivalence is not established.