How do I install the AIXBT MCP server?

AIXBT is a hosted endpoint at https://api.aixbt.tech/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.

AIXBT

REMOTE · API.AIXBT.TECH · SCANNED SEP 27

Crypto market intelligence for Projects, Topics, Intel, Reports, and Clusters.

Available components

remote · api.aixbt.tech 94

−1 this week 94 94 Trust /100

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 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability75

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 1382 tokens (~115/item across 12 items; 12 tools + 0 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 Management100

No destabilizing schema changes in the last 30 days.Pass

Tool Coverage99

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
98% of tool parameters carry a description.Partial
Structured output schemas are declared (100% 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
We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass

Capabilities100

Implements a current MCP spec version (2026-07-28).Pass

Changelog Show cosmetic changes

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 Sept 26 0
- Tool “me” rewrote its description, which is the text the model reads security
- Tool “me” changed its title: Check AIXBT access → Check AIXBT account cosmetic
25 Sept 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
24 Sept 26 −1
- Schema quality: excellent → good functional
- “list_intel” added an optional parameter “marketCap” cosmetic
18 Sept 26 +2
- Stability: fail → pass ▲ security
17 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
14 Sept 26 0
- Schema quality: good → excellent functional
- “get_intel” reworded the description of “id” cosmetic
9 Sept 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 85 to 91.
7 Sept 26 +1

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

Show 5 earlier entries Hide earlier entries

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 27 Sept 2026 · Probed https://api.aixbt.tech/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=api.aixbt.tech	CN=YR1,O=Let's Encrypt,C=US	22 Sept 2026	21 Dec 2026	RSA 2048	SHA256-RSA	5b0a4e149597e4863c8c95fa3475e3503b3
SANs: api.aixbt.tech
CN=YR1,O=Let's Encrypt,C=US (CA)	CN=Root YR,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	RSA 2048	SHA256-RSA	a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	RSA 4096	SHA256-RSA	f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.aixbt.tech. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
tech.	present	2185	13	Verified
aixbt.tech.	present	808	13	Verified
api.aixbt.tech.				Verified address RRset verified with the apex keys

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="https://api.aixbt.tech", resource_metadata="https://api.aixbt.tech/.well-known/oauth-protected-resource", scope="mcp"

Bearer realm="https://api.aixbt.tech", resource_metadata="https://api.aixbt.tech/.well-known/oauth-protected-resource", scope="mcp"

Header	Value
strict-transport-security	max-age=31536000; includeSubDomains
content-security-policy	default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
x-content-type-options	nosniff
x-frame-options	SAMEORIGIN
referrer-policy	no-referrer

Protected resource metadata

Document	https://api.aixbt.tech/.well-known/oauth-protected-resource
Retrieved	Yes
Resource	https://api.aixbt.tech/mcp
Authorisation server	https://api.aixbt.tech

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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://api.aixbt.tech/mcp	Verified	200
http (plaintext)	http://api.aixbt.tech/mcp	HTTPS enforced	301	https://api.aixbt.tech/mcp

MCP tools · 12 exposed · ~1,119 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

get_intel Get intel details ~61

Get one development with its sources and context.

Input Output Examples

Name	Type	Req	Description
activity	string	–	Activity rows to include: all (default), source observations only, or none
id	string	yes	Exact Intel item id returned by list_intel, not its project.id

Name	Type	Req	Description
data	object	yes	–

No examples provided.

get_project Get project details ~35

Get a Project with recent Intel and related Projects.

Input Output Examples

Name	Type	Req	Description
idOrSlug	string	yes	Project ID or slug; slug aliases resolve

Name	Type	Req	Description
data	object	yes	–
meta	object	yes	–

No examples provided.

get_project_series Get project history ~85

Get recent attention history for a Project.

Input Output Examples

Name	Type	Req	Description
from	string	–	Start of time window (ISO 8601)
idOrSlug	string	yes	Project ID or slug; slug aliases resolve
measure	string	yes	trend for hourly scores; rank for recorded Trend-rank changes
to	string	–	End of time window (ISO 8601)

Name	Type	Req	Description
data	object	yes	–
meta	object	yes	–

No examples provided.

get_report Get topic report ~28

Get a published AIXBT report with its sources.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Report ID

Name	Type	Req	Description
data	object	yes	–

No examples provided.

get_topic Get topic details ~30

Get one current Topic with its recent context.

Input Output Examples

Name	Type	Req	Description
topicId	string	yes	Topic ID from list_topics

Name	Type	Req	Description
data	object	yes	–
meta	object	yes	–

No examples provided.

get_topic_series Get topic history ~78

Get recent attention history for a Topic.

Input Output Examples

Name	Type	Req	Description
from	string	–	Start of time window (ISO 8601)
measure	string	yes	trend for hourly scores; rank for recorded Trend-rank changes
to	string	–	End of time window (ISO 8601)
topicId	string	yes	Topic ID

Name	Type	Req	Description
data	object	yes	–
meta	object	yes	–

No examples provided.

get_vocabulary Get filter vocabulary ~15

Get current supported filter values.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
data	object	yes	–
meta	object	yes	–

No examples provided.

list_clusters List audience clusters ~29

List audience communities contributing to crypto attention.

Input Output Examples

Name	Type	Req	Description
universe	string	–	Market universe (default: crypto)

Name	Type	Req	Description
data	array	yes	–

No examples provided.

list_intel Search crypto intel ~457

Search recent crypto developments using text and filters.

Input Output Examples

Name	Type	Req	Description
activity	string	–	Activity rows to include: all (default), source observations only, or none
address	string	–	Token contract address
assetTypes	string	–	Comma-separated asset types; use get_vocabulary to list them
categories	string	–	Comma-separated Intel category names; use get_vocabulary and choose intelCategories[].name
clusterIds	string	–	Comma-separated cluster IDs
cursor	string	–	Cursor returned in meta.nextCursor from the previous page
detectedAfter	string	–	Detected at or after this time (ISO 8601)
detectedBefore	string	–	Detected at or before this time (ISO 8601)
grades	string	–	–
hasOfficialSource	boolean	–	Set true to return only Intel with an official Project source
limit	integer	–	Results per page (default and maximum: 50)
marketCap	string	–	Only return Intel for Projects whose current market cap is in this band: low (under $80M), mid ($80M to $500M), or large ($500M and above). Projects without a current market cap are excluded
minClusters	integer	–	Minimum number of community clusters represented
names	string	–	Comma-separated Project names
projectIds	string	–	Comma-separated Project IDs
projectRanking	string	–	Only return Intel for Projects in the current trend ranking
projectSlugs	string	–	Comma-separated Project slugs
reinforcedAfter	string	–	Reinforced at or after this time (ISO 8601)
reinforcedBefore	string	–	Reinforced at or before this time (ISO 8601)
search	string	–	Any text to match across Project identity and Intel content; combines with all filters
sentiments	string	–	Comma-separated sentiments: positive, neutral, negative
sort	string	–	Order by first detection (default) or latest reinforcement
tickers	string	–	Comma-separated tickers
xHandles	string	–	Comma-separated X handles

Name	Type	Req	Description
data	array	yes	–
meta	object	yes	–

No examples provided.

list_projects Find crypto projects ~235

Find tracked crypto Projects using supported filters.

Input Output Examples

Name	Type	Req	Description
address	string	–	Token contract address
assetTypes	string	–	Comma-separated asset types (token, stablecoin, nft-collection)
categories	string	–	Comma-separated Project category slugs; use get_vocabulary to list them
chain	string	–	Chain to filter by (e.g. "ethereum", "solana")
cursor	string	–	Cursor returned in meta.nextCursor from the previous page
ids	string	–	Comma-separated Project IDs
limit	integer	–	Number of results to return (default and maximum: 50)
minTrend	number	–	Minimum current trend measurement
names	string	–	Comma-separated Project names
slugs	string	–	Comma-separated Project slugs
sort	string	–	Order by trend (default), creation time, or latest reinforcement
tickers	string	–	Comma-separated tickers
universe	string	–	Market universe (default: crypto)
xHandles	string	–	Comma-separated X handles

Name	Type	Req	Description
data	array	yes	–
meta	object	yes	–

No examples provided.

list_topics List trending topics ~42

List the current crypto Topic landscape.

Input Output Examples

Name	Type	Req	Description
projectId	string	–	Only Topics currently associated with this Project ID
ranking	string	–	trend for sustained attention

Name	Type	Req	Description
data	array	yes	–
meta	object	yes	–

No examples provided.

me Check AIXBT account ~24

Check the signed-in AIXBT account, plan, wallet, and usage limits.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
data	object	yes	–

No examples provided.

Common questions

What is the AIXBT MCP server?

AIXBT is an MCP server listed in the public MCP registry as io.github.aixbt/aixbt. Crypto market intelligence for Projects, Topics, Intel, Reports, and Clusters. This page covers its hosted endpoint (https://api.aixbt.tech/mcp).

Is the AIXBT MCP server safe to use?

AIXBT scores 94 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 AIXBT MCP server expose?

AIXBT exposes 12 tools: list_projects, get_project, get_project_series, list_intel, get_intel, and 7 more. Their descriptions and schemas cost roughly 1,119 tokens of context every time the server is loaded.

Does the AIXBT MCP server require authentication?

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

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

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Badge

Put this score in your README. The image is served from a stable URL, updates when the score does, and links back to the evidence on this page. It shows nothing that is not already published here.

Score Verified Plain

The two-cell badge: our name, and this channel's current score out of 100.

Markdown

 [![VerifyMCP trust score for AIXBT](https://verifymcp.io/badge/aixbt-aixbt/api.svg)](https://verifymcp.io/servers/aixbt-aixbt/api)

HTML

 <a href="https://verifymcp.io/servers/aixbt-aixbt/api"><img src="https://verifymcp.io/badge/aixbt-aixbt/api.svg" alt="VerifyMCP trust score for AIXBT" height="20"></a>

A single cell stating that the server is listed here. Carries no number.

Markdown

 [![VerifyMCP trust score for AIXBT](https://verifymcp.io/badge/aixbt-aixbt/api.svg?variant=verified)](https://verifymcp.io/servers/aixbt-aixbt/api)

HTML

 <a href="https://verifymcp.io/servers/aixbt-aixbt/api"><img src="https://verifymcp.io/badge/aixbt-aixbt/api.svg?variant=verified" alt="VerifyMCP trust score for AIXBT" height="20"></a>

The score alone, tier-coloured, for a badge row that is already crowded.

Markdown

 [![VerifyMCP trust score for AIXBT](https://verifymcp.io/badge/aixbt-aixbt/api.svg?variant=plain)](https://verifymcp.io/servers/aixbt-aixbt/api)

HTML

 <a href="https://verifymcp.io/servers/aixbt-aixbt/api"><img src="https://verifymcp.io/badge/aixbt-aixbt/api.svg?variant=plain" alt="VerifyMCP trust score for AIXBT" height="20"></a>

Score history · last 30 days

29 Aug 27 Sept

Trust score by day, last 30 days
Day	Score
29 Aug	86
30 Aug	87
31 Aug	87
1 Sept	88
2 Sept	88
3 Sept	89
4 Sept	89
5 Sept	91
6 Sept	91
7 Sept	92
8 Sept	92
9 Sept	93
10 Sept	93
11 Sept	93
12 Sept	93
13 Sept	93
14 Sept	93
15 Sept	93
16 Sept	93
17 Sept	93
18 Sept	95
19 Sept	95
20 Sept	95
21 Sept	95
22 Sept	95
23 Sept	95
24 Sept	94
25 Sept	94
26 Sept	94
27 Sept	94