MCP server

Planned — waitlist open

Solana signal intelligence for your own AI agents.

A read-oriented MCP server that gives external AI agents the intelligence ARCHR computes internally: signal performance history, wallet scores, token lifecycle state, and meta narratives. Not shipped yet.

Status

Not yet available

Shape

Read-oriented intelligence tools

Auth

API key, rate limited

Execution tools

Confirmation-gated if added

Configuration

Why another Solana MCP would be pointless

Swap-execution MCPs for Solana already exist, several of them. Building one more would add nothing, so this is not that.

Signal performance

Historical, per source

Wallet scoring

Behavioural scores

Token lifecycle

Stage classification

Meta narratives

Theme clustering

Technical indicators

Computed series

Market temperature

Regime summary

Explainer

What is a Solana intelligence MCP server?

Updated 2026-07-27

The Model Context Protocol is an open standard that lets AI clients — Claude, Cursor, and a growing list of others — call external tools. An MCP server publishes a set of tools with typed schemas, and any compatible client can discover and use them without a custom integration.

Most Solana MCP servers built so far are execution wrappers: check a balance, send SOL, swap through Jupiter, snipe a launch. Several of those already exist and work fine. Adding another would be redundant, and we are not going to claim a category-first position that is plainly not available.

The gap is intelligence. What no existing Solana MCP exposes is derived, historical context — which signal families actually performed and over what sample, how a wallet has behaved across many tokens, where a token sits in its lifecycle, which narrative cluster a launch belongs to. ARCHR already computes all of that internally to run the bot. That is the part worth publishing.

The design constraint is the boundary between research and execution. Agent frameworks chain tools aggressively, and without a hard confirmation step a research workflow quietly becomes an execution workflow. So the first release will be read-only, and any execution tool added later will require explicit confirmation with the size, token, and wallet spelled out — not an inferred yes.

The gap

Execution is solved; context is not

An agent that can swap tokens but cannot tell you whether a signal source has ever worked is a fast way to lose money. The scarce input is not transaction capability — it is judgment-grade context.

ARCHR's intelligence jobs produce exactly that as a by-product of running the bot: signal performance summaries, wallet scores, lifecycle stages, technical indicators, and meta-narrative clusters.

The design

Read-only first, confirmation-gated later

Version one exposes intelligence, with versioned schemas, documented freshness, API-key auth, and rate limits. Nothing in it can move funds, which makes it safe to hand to an autonomous agent.

If execution tools arrive, they will be a separate, clearly-marked surface with a mandatory confirmation step. That is the whole argument of our MCP-safe confirmation guide, and it would be strange to publish it and then ignore it.

  • Versioned tool schemas
  • Documented data freshness and limitations
  • API-key auth with rate limits
  • Read tools and execution tools never merged

Honestly

What exists today

Today ARCHR's Telegram agent uses internal MCP integrations for on-chain and market data when configured. That is an internal implementation detail, not a public endpoint, and calling it a public MCP would be a lie of the sort this site tries not to tell.

There is no way to connect Claude or Cursor to ARCHR right now. The waitlist is the honest version of a launch date.

Common questions

Questions ARCHR answers

Direct answers, including the ones where the honest answer is “no”.

Can I connect Claude or Cursor to ARCHR today?

Not yet. The public MCP server is planned and not shipped. You can use the Telegram bot and its optional BYOK agent today, and join the waitlist for MCP updates.

How will the ARCHR MCP differ from other Solana MCP servers?

Existing Solana MCP servers focus on execution — balances, transfers, swaps, sniping. ARCHR's will expose derived intelligence instead: signal performance history, wallet scoring, token lifecycle stage, and meta narratives.

Will the MCP server be able to execute trades?

The first release is read-only. If execution tools are added later they will be a separate surface requiring explicit confirmation with token, size, and wallet stated.

Is ARCHR the first Solana trading MCP?

No, and we will not claim that. Several Solana MCP servers already exist. ARCHR's differentiator is the intelligence data, not being first.

What is the Model Context Protocol?

MCP is an open standard that lets AI clients discover and call external tools through a common interface, so one server can serve many different AI applications without bespoke integrations.

What it does

  • Expose ARCHR's computed intelligence to MCP-compatible clients.
  • Let an agent ask which signal families have actually performed, and over what window.
  • Keep research tools and any execution tools strictly separate.

How traders use it

  • Ask Claude to summarize which call channels performed this month.
  • Give an internal research agent structured wallet scores instead of scraped pages.
  • Build a daily Solana meta brief from lifecycle and narrative data.

At a glance

Protocol
Model Context Protocol
Availability
Planned — not shipped
First tools
Read-only intelligence
Distribution
MCP registries and GitHub at launch

Solana signal intelligence for your own AI agents.

ARCHR runs in Telegram. @archr_signal_bot — free to start, 1% platform fee on trades.

Memecoin trading is highly volatile and can result in total loss of capital. ARCHR provides software tools, not financial advice. Read the full risk disclosure and terms of use.