Measured crypto KOL data: real reach, organic token interest, chain reports, post archive.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Who among measured KOLs talks about a chain (base, solana, ethereum, bsc, near, arbitrum, hyperliquid, …), its most-discussed tokens, and the KOLs whose posts were followed by more trading volume. Window 7, 30 or 90 days.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http mihenk https://app.mihenkai.com/mcp
Who among measured KOLs talks about a chain (base, solana, ethereum, bsc, near, arbitrum, hyperliquid, …), its most-discussed tokens, and the KOLs whose posts were followed by more trading volume. Window 7, 30 or 90 days.
| Argument | Type | Description |
|---|---|---|
| days | integer | |
| chain* | string |
{
"type": "object",
"required": [
"chain"
],
"properties": {
"days": {
"enum": [
7,
30,
90
],
"type": "integer",
"default": 30
},
"chain": {
"type": "string"
}
}
}Archived posts of measured KOLs with the exact post time, including posts later deleted from X. Give a handle, words (or a $ticker), or both. Returns at most 10 records with links and record hashes.
| Argument | Type | Description |
|---|---|---|
| words | string | |
| handle | string | |
| deleted_only | boolean |
{
"type": "object",
"properties": {
"words": {
"type": "string"
},
"handle": {
"type": "string"
},
"deleted_only": {
"type": "boolean",
"default": false
}
}
}The spot coins a KOL promoted in the last 7, 30 or 90 days, with the median 24 h move after their posts. Not a recommendation; it shows what the KOL promoted and what followed.
| Argument | Type | Description |
|---|---|---|
| days | integer | |
| handle* | string |
{
"type": "object",
"required": [
"handle"
],
"properties": {
"days": {
"enum": [
7,
30,
90
],
"type": "integer",
"default": 30
},
"handle": {
"type": "string"
}
}
}Mihenk's measurement of one X account: Mihenk score (0-10), real reach (typical views per post), followers, region, 90-day call record (share of calls that went the call's way within 24 h) and the last 5 calls.
| Argument | Type | Description |
|---|---|---|
| handle* | string | X handle, e.g. cobie |
{
"type": "object",
"required": [
"handle"
],
"properties": {
"handle": {
"type": "string",
"description": "X handle, e.g. cobie"
}
}
}Which measured KOLs talked about a token, how many views those posts got and how much was organic (posts that 3+ accounts published with the same text count as coordinated). Window 7, 30 or 90 days.
| Argument | Type | Description |
|---|---|---|
| days | integer | |
| token* | string | Ticker without $ (e.g. PEPE) or a contract address |
{
"type": "object",
"required": [
"token"
],
"properties": {
"days": {
"enum": [
7,
30,
90
],
"type": "integer",
"default": 30
},
"token": {
"type": "string",
"description": "Ticker without $ (e.g. PEPE) or a contract address"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 16, 2026.
Takes a password, API key or token as an argument, so the secret passes through the model's context and chat logs.
Fix: Read credentials from the server's own configuration (environment, OAuth) instead of a tool argument.