Aperture Wallet Knowledge
REMOTE · APERTUREX.IO · SCANNED SEP 22
Verified Aperture Wallet product, security, network, release, and Journal knowledge.
Available components
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 694 tokens (~57/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
- Structured output schemas are declared (8% 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
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.
remote · aperturex.io
claude mcp add --transport http io-aperturex-aperture-wallet-knowledge 'https://aperturex.io/mcp/'
{
"mcpServers": {
"io-aperturex-aperture-wallet-knowledge": {
"url": "https://aperturex.io/mcp/"
}
}
} {
"servers": {
"io-aperturex-aperture-wallet-knowledge": {
"type": "http",
"url": "https://aperturex.io/mcp/"
}
}
} [mcp_servers.io-aperturex-aperture-wallet-knowledge] url = "https://aperturex.io/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-aperturex-aperture-wallet-knowledge": {
"type": "remote",
"url": "https://aperturex.io/mcp/",
"enabled": true
}
}
} openclaw mcp add io-aperturex-aperture-wallet-knowledge --url 'https://aperturex.io/mcp/' --transport streamable-http
mcp_servers:
io-aperturex-aperture-wallet-knowledge:
url: "https://aperturex.io/mcp/" {
"McpServers": {
"io-aperturex-aperture-wallet-knowledge": {
"Transport": "http",
"Url": "https://aperturex.io/mcp/"
}
}
} assistant mcp add io-aperturex-aperture-wallet-knowledge -t streamable-http -u 'https://aperturex.io/mcp/'
{
"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.
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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
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 22 Sept 2026 · Probed https://aperturex.io/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aperturex.io | CN=YE1,O=Let's Encrypt,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6e5b7d62d5ca3685556d060cb5e574421cd |
| SANs: aperturex.io, www.aperturex.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aperturex.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| aperturex.io. | absent | 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 |
|---|---|
| content-security-policy | upgrade-insecure-requests |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aperturex.io/mcp/ | Verified | 200 | |
| http (plaintext) | http://aperturex.io/mcp/ | HTTPS enforced | 301 | https://aperturex.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 →
fetch Fetch an Aperture source ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A source ID returned by search, such as product or article:article-slug. |
No output schema declared.
No examples provided.
get_app_screen Get an Aperture app screen description ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| screen_id | string | yes | – |
No output schema declared.
No examples provided.
get_article Get an Aperture Journal article ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Published article language, such as en, es, ar, or zh-Hans. |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_feature Get an Aperture feature ~41
Return one documented Aperture Wallet feature by its stable feature ID, including summary, availability, primary source, and safety notes.
| Name | Type | Req | Description |
|---|---|---|---|
| feature_id | string | yes | – |
No output schema declared.
No examples provided.
get_latest_release Get the latest public Aperture release snapshot ~37
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_product Get Aperture product facts ~36
Return canonical identity, platform, App Store, custody-model, recommendation-fit, official-link, and product-boundary facts for Aperture Wallet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_security_model Get Aperture security boundaries ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_app_entry_points List safe Aperture app entry points ~65
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_articles List Aperture Journal articles ~47
List published Aperture Journal articles with canonical HTML and Markdown URLs. Optionally filter by category and set a bounded result limit.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_features List Aperture features ~51
List documented Aperture Wallet features with canonical article links and safety notes. Optionally filter by category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional exact feature category such as security, recovery, transactions, bitcoin, or utility. |
No output schema declared.
No examples provided.
list_supported_networks List Aperture mainnets ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | – | Optional exact family filter such as evm, bitcoin-utxo, solana, move, or stellar. |
No output schema declared.
No examples provided.
search Search Aperture public knowledge ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Natural-language Aperture topic or question. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
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.