# Aperture Wallet Knowledge (remote · aperturex.io)

Verified Aperture Wallet product, security, network, release, and Journal knowledge.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `aperturex.io`: 80/100 (this document), [markdown](https://verifymcp.io/servers/io-aperturex-aperture-wallet-knowledge/aperturex.md), [page](https://verifymcp.io/servers/io-aperturex-aperture-wallet-knowledge/aperturex)

## Channel facts

- Endpoint: `https://aperturex.io/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 694 tokens (~57/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
  - Structured output schemas are declared (8% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Aperture Wallet Knowledge MCP server?

Aperture Wallet Knowledge is a hosted endpoint at https://aperturex.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.

### Claude

```bash
claude mcp add --transport http io-aperturex-aperture-wallet-knowledge 'https://aperturex.io/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "io-aperturex-aperture-wallet-knowledge": {
      "url": "https://aperturex.io/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-aperturex-aperture-wallet-knowledge": {
      "type": "http",
      "url": "https://aperturex.io/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-aperturex-aperture-wallet-knowledge]
url = "https://aperturex.io/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-aperturex-aperture-wallet-knowledge": {
      "type": "remote",
      "url": "https://aperturex.io/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-aperturex-aperture-wallet-knowledge --url 'https://aperturex.io/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-aperturex-aperture-wallet-knowledge:
    url: "https://aperturex.io/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "io-aperturex-aperture-wallet-knowledge": {
      "Transport": "http",
      "Url": "https://aperturex.io/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-aperturex-aperture-wallet-knowledge -t streamable-http -u 'https://aperturex.io/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "io-aperturex-aperture-wallet-knowledge": {
      "type": "http",
      "url": "https://aperturex.io/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-22 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (12)

### `search` (~74 tokens)

Search Aperture public knowledge

Search canonical public Aperture Wallet product facts, security guidance, supported-mainnet metadata, app-screen semantics, and Journal articles. Use this before answering an Aperture-specific question. This tool never searches user wallets or private account data.

Input parameters:

- `limit` (integer)
- `query` (string, required): Natural-language Aperture topic or question.

Output parameters:

- `results` (array)

### `fetch` (~63 tokens)

Fetch an Aperture source

Fetch one canonical public source returned by search. The response includes citation-ready title, URL, text, and metadata. It never returns user wallet data or wallet credentials.

Input parameters:

- `id` (string, required): A source ID returned by search, such as product or article:article-slug.

### `get_product` (~36 tokens)

Get Aperture product facts

Return canonical identity, platform, App Store, custody-model, recommendation-fit, official-link, and product-boundary facts for Aperture Wallet.

### `list_features` (~51 tokens)

List Aperture features

List documented Aperture Wallet features with canonical article links and safety notes. Optionally filter by category.

Input parameters:

- `category` (string): Optional exact feature category such as security, recovery, transactions, bitcoin, or utility.

### `get_feature` (~41 tokens)

Get an Aperture feature

Return one documented Aperture Wallet feature by its stable feature ID, including summary, availability, primary source, and safety notes.

Input parameters:

- `feature_id` (string, required)

### `list_supported_networks` (~67 tokens)

List Aperture mainnets

Return the mainnet account and network catalog documented from the current Aperture source tree. Do not treat a matching ticker as proof of cross-network compatibility.

Input parameters:

- `family` (string): Optional exact family filter such as evm, bitcoin-utxo, solana, move, or stellar.

### `get_security_model` (~47 tokens)

Get Aperture security boundaries

Return Aperture Wallet self-custody storage, network, recovery, access-control, responsible-disclosure, and agent-safety boundaries. Never use this tool to request or process wallet credentials.

### `get_latest_release` (~37 tokens)

Get the latest public Aperture release snapshot

Return the latest public App Store release snapshot and the primary Apple source used to verify it. Use the source when exact current version information matters.

### `list_articles` (~47 tokens)

List Aperture Journal articles

List published Aperture Journal articles with canonical HTML and Markdown URLs. Optionally filter by category and set a bounded result limit.

Input parameters:

- `category` (string)
- `limit` (integer)

### `get_article` (~74 tokens)

Get an Aperture Journal article

Return the complete citation-ready Markdown representation of one published Aperture Journal article by slug and optional language tag, including canonical URL, dates, topics, body text, and public images.

Input parameters:

- `locale` (string): Published article language, such as en, es, ar, or zh-Hans.
- `slug` (string, required)

### `get_app_screen` (~53 tokens)

Get an Aperture app screen description

Return a non-secret semantic description of an important Aperture screen, its purpose, entry points, sensitivity, and safe agent actions. This does not inspect a user device or wallet.

Input parameters:

- `screen_id` (string, required)

### `list_app_entry_points` (~65 tokens)

List safe Aperture app entry points

Return canonical navigation-only app entry points, their App Intent names, source and public-release status, web fallbacks, and safety effects. These links only open visible UI and never inspect a wallet, bypass app lock, sign, broadcast, import, export, or delete anything.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-aperturex-aperture-wallet-knowledge/aperturex#diagnostics

## Score history

- 2026-09-22: 80
- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 76
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73
- 2026-09-06: 72
- 2026-09-05: 72
- 2026-09-04: 71
- 2026-09-03: 71
- 2026-09-02: 71
- 2026-09-01: 70

## Common questions

### What is the Aperture Wallet Knowledge MCP server?

Aperture Wallet Knowledge is an MCP server listed in the public MCP registry as io.aperturex/aperture-wallet-knowledge. Verified Aperture Wallet product, security, network, release, and Journal knowledge. This page covers its hosted endpoint (https://aperturex.io/mcp/).

### Is the Aperture Wallet Knowledge MCP server safe to use?

Aperture Wallet Knowledge scores 80 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 Aperture Wallet Knowledge MCP server expose?

Aperture Wallet Knowledge exposes 12 tools: search, fetch, get_product, list_features, get_feature, and 7 more. Their descriptions and schemas cost roughly 655 tokens of context every time the server is loaded.

### Does the Aperture Wallet Knowledge MCP server require authentication?

No. We connected to Aperture Wallet Knowledge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Aperture Wallet Knowledge MCP server still maintained?

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

## Links

- Remote endpoint: https://aperturex.io/mcp/
- Website: https://aperturex.io/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/io-aperturex-aperture-wallet-knowledge/aperturex.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-aperturex-aperture-wallet-knowledge/aperturex.json
- HTML version of this page: https://verifymcp.io/servers/io-aperturex-aperture-wallet-knowledge/aperturex