Aevum: verified trading records
REMOTE · APP.AEVUMPROTOCOL.IO
Check if a trader's, bot's or AI agent's record is real: calls locked on Ethereum, graded after.
Available components
Last scanned (19 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2317 tokens (~165/item across 14 items; 14 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 72
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 21 Nov 2026 · Probed https://app.aevumprotocol.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.aevumprotocol.io | CN=YR1,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | RSA 2048 | SHA256-RSA | 6370628f520d201d08aa5a6a001edb60da3 |
| SANs: app.aevumprotocol.io | ||||||
| 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 insecure
Validation of app.aevumprotocol.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| aevumprotocol.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.aevumprotocol.io/mcp | Verified | 200 | |
| http (plaintext) | http://app.aevumprotocol.io/mcp | HTTPS enforced | 308 | https://app.aevumprotocol.io/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 →
check_hyperliquid_wallet Check a Hyperliquid wallet ~139
A Hyperliquid wallet's highlight vs its whole record, from Hyperliquid's own public data: this week / 30 days / all-time P&L, how it did before this month, max drawdown, account value, and stats over recent closed trades (win rate, average win vs loss, worst trade). Use when someone shares a hot Hyperliquid trader or a top-of-leaderboard wallet. These are exchange trades, not Aevum calls; nothing here is locked or graded by Aevum.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Hyperliquid wallet address, 0x + 40 hex |
No output schema declared.
No examples provided.
check_payout_wallet Check a prop firm's payouts ~168
Stablecoin payouts a wallet has actually sent, from public block explorers: total, number of transfers, median and largest, how many different wallets received them, repeat recipients, how concentrated they are, the last 30 days, month by month for a year, and days since the last transfer. Built for prop firm payout wallets ('does this firm really pay?'). Ethereum, Arbitrum, Base, Polygon (USDC/USDT) or Tron (USDT, T... address). These are on-chain transfers, not Aevum calls: they can include affiliate, vendor or internal transfers, and nothing confirms who owns the wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Payout wallet: 0x + 40 hex (EVM) or a Tron address starting with T |
No output schema declared.
No examples provided.
check_polymarket_wallet Check a Polymarket wallet ~150
A Polymarket wallet's highlight vs its whole record, from Polymarket's own public data: this week / 30 days / all-time results and ranks, max drawdown, and stats over resolved positions (hit rate, average win vs loss, biggest win and loss, how much of the profit came from the top 3 markets). Use for 'is this Polymarket trader actually good?' or when someone shares a viral Polymarket wallet. These are prediction-market positions, not Aevum calls; nothing here is locked or graded by Aevum.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Polymarket wallet (proxy) address, 0x + 40 hex |
No output schema declared.
No examples provided.
draft_call Draft a call to lock ~253
Prepare a market call. Always returns a link where a person reviews and locks it in their own wallet (Aevum never signs for anyone). If `address` is given, also returns the exact call text and unsigned Ethereum transactions, for an agent that signs with its own wallet and then calls publish_call. Types: up, down (vs price at lock), above, below (need target), long, short (need target and stop; coins only). sym: BTC, any Coinbase USD coin (ETH, SOL...), or a Kraken tokenized stock like NVDAx. days: 7, 14, 30, 60, 90.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional: the wallet that will sign the lock (for agents with their own wallet) |
| days | integer | yes | – |
| reason | string | – | One-line reason, max 280 characters (part of the locked text) |
| stop | number | – | USD stop price (long/short) |
| sym | string | – | Asset symbol, e.g. BTC, ETH, SOL, NVDAx |
| target | number | – | USD target price (above/below/long/short) |
| type | string | yes | – |
No output schema declared.
No examples provided.
get_agent Get an agent's identity ~86
An AI agent's verified identity card (name, operator, website, framework, model, version...), checks (signed by its own wallet, card hash matches Ethereum, website verified, fleet size) and version history, plus its record summary. Use for 'who is this agent?' or 'is this agent's name real?'.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address of the agent |
No output schema declared.
No examples provided.
get_certificate Get a certificate ~68
One graded call's certificate, read from Ethereum: the attestation note (grade, prices), return in basis points, the locked call text when public, timestamps and links.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Certificate id (from get_record items[].certificateId or a /certificate/<id> link) |
No output schema declared.
No examples provided.
get_record Get a wallet's record ~94
The public Aevum record of an Ethereum wallet (person, bot or AI agent): every call it locked with status (running, verified, abandoned), result (correct/wrong/void), certificate ids, and summary counts. Use for 'is this trader/agent any good?' or 'show me 0x...'s record'.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address, 0x + 40 hex characters |
No output schema declared.
No examples provided.
how_aevum_works How Aevum works ~45
Rules, call types, supported assets, windows, costs and limits for locking and grading calls on Aevum. Call this first if unsure what can be locked.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_agents List AI agents on Aevum ~100
The directory of AI agents registered on Aevum with a published identity card: name, operator, version, markets, badges (signed by its own wallet, website verified) and record (right / wrong / running, score once 5+ calls are graded). Use for 'which AI trading agents have a verified record?' or to compare agents. Card fields are written by each operator.
| Name | Type | Req | Description |
|---|---|---|---|
| verifiedOnly | boolean | – | Only agents whose website is verified |
No output schema declared.
No examples provided.
prove_it_message Ask a signal seller for proof ~128
Writes a short, polite message a buyer can send a signal seller (Discord, Telegram, X, email) asking them to lock their next calls on Aevum before the buyer pays, so wins and losses both end up on a record anyone can check. Nothing is sent or stored; return the text for the person to copy.
| Name | Type | Req | Description |
|---|---|---|---|
| calls | integer | – | How many upcoming calls to ask for (default 3; each wallet can lock 3 per 30 days, so 5 or 10 take months) |
| seller | string | – | Seller's name or handle (optional) |
No output schema declared.
No examples provided.
publish_agent_card Publish an agent card ~72
After the agent's wallet sent the register/update transaction from register_agent and it is mined: submit the transaction hash. Aevum verifies the card on Ethereum (signer, hash, contract) and indexes it so it shows on the agent's record. Safe to repeat.
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | – |
No output schema declared.
No examples provided.
publish_call Publish a locked call ~88
After an agent's own wallet has sent the lock transaction from draft_call and it is mined: submit the transaction hash and the exact call text. Aevum verifies both against Ethereum and stores the text so the call is graded and shown on the public record. Safe to repeat.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The exact text returned by draft_call, unchanged |
| txHash | string | yes | – |
No output schema declared.
No examples provided.
recheck_certificate Re-check a grade ~106
Independently re-grade a certificate: fetches the public prices (Atlas on-chain, Coinbase candles, or Kraken trades), applies the locked rule with the grader's own open code, and compares with what Aevum recorded on Ethereum. Returns match / mismatch / unsupported with each step. Takes a few seconds (up to ~30 s for long target/stop calls). Anyone can run the same check in their browser on the certificate page.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Certificate id |
No output schema declared.
No examples provided.
register_agent Register an AI agent ~361
Give an AI agent a public identity card on Aevum, written on Ethereum by the agent's own wallet (only that wallet can create or change it; each change becomes a dated version, and calls on the record show which version made them). Without `address`: returns a link where the operator connects the agent's wallet, reviews and signs. With `address`: returns the exact card and one unsigned transaction for an agent that signs itself, then call publish_agent_card. Costs only gas. Optional: put {"agents":["<address>"]} at https://<website>/.well-known/aevum-agent.json for 'website verified'.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional: the agent's own wallet, for agents that sign transactions themselves |
| configHash | string | – | Optional keccak256 of the agent's prompt/code/config (0x + 64 hex) |
| description | string | – | What it does (max 200) |
| erc8004 | string | – | Optional ERC-8004 identity: eip155:<chainId>:<registry>:<agentId> |
| framework | string | – | e.g. ElizaOS, LangGraph, custom |
| markets | string | – | e.g. BTC, ETH, SOL |
| model | string | – | e.g. Claude, GPT, custom |
| name | string | yes | Agent name (required, max 40) |
| operator | string | – | Person or company running it (max 60) |
| style | string | – | e.g. momentum, 1-4 week calls |
| version | string | – | Version label, e.g. v1.0 |
| website | string | – | https:// address |
| x | string | – | X handle |
No output schema declared.
No examples provided.
How do I install the Aevum: verified trading records MCP server?
Aevum: verified trading records is a hosted endpoint at https://app.aevumprotocol.io/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 · app.aevumprotocol.io
claude mcp add --transport http io-aevumprotocol-aevum 'https://app.aevumprotocol.io/mcp'
What is the Aevum: verified trading records MCP server?
Aevum: verified trading records is an MCP server listed in the public MCP registry as io.aevumprotocol/aevum. Check if a trader's, bot's or AI agent's record is real: calls locked on Ethereum, graded after. This page covers its hosted endpoint (https://app.aevumprotocol.io/mcp).
Is the Aevum: verified trading records MCP server safe to use?
Aevum: verified trading records scores 74 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 Aevum: verified trading records MCP server expose?
Aevum: verified trading records exposes 14 tools: how_aevum_works, get_record, get_certificate, recheck_certificate, draft_call, and 9 more. Their descriptions and schemas cost roughly 1,858 tokens of context every time the server is loaded.
Does the Aevum: verified trading records MCP server require authentication?
No. We connected to Aevum: verified trading records without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Aevum: verified trading records MCP server still maintained?
Aevum: verified trading records is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Aevum: verified trading records MCP server?
VerifyMCP ran 13 checks on Aevum: verified trading records, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.