mcpbeat Sign in

Aperture Wallet Knowledge MCP Server

by aperturex Your server? Claim it
not responding

Aperture Wallet Knowledge is listed as active in the registry but did not answer our last check. It exposes 12 tools.

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

Uptime history 68 days of history · worst day 0%
68 days agonow
0.0%
Uptime 24h
0 of 91 checks
12
Tools
read from the server
528 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 September 2026. No other catalogue keeps this.

3 Sep a tool description was rewritten get_article
3 Sep a tool changed the parameters it asks for get_article

Aperture Wallet Knowledge does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add aperture-wallet-knowledge --transport http https://aperturex.io/mcp/
Settings → Connectors → Add custom connector, then paste this address
https://aperturex.io/mcp/
~/.codex/config.toml
[mcp_servers.aperture-wallet-knowledge]
url = "https://aperturex.io/mcp/"
.cursor/mcp.json
{
  "mcpServers": {
    "aperture-wallet-knowledge": {
      "url": "https://aperturex.io/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "aperture-wallet-knowledge": {
      "type": "http",
      "url": "https://aperturex.io/mcp/"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

app
get_app_screen
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.
list_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.
article
get_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.
articles
list_articles
List published Aperture Journal articles with canonical HTML and Markdown URLs. Optionally filter by category and set a bounded result limit.
feature
get_feature
Return one documented Aperture Wallet feature by its stable feature ID, including summary, availability, primary source, and safety notes.
features
list_features
List documented Aperture Wallet features with canonical article links and safety notes. Optionally filter by category.
fetch
fetch
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.
latest
get_latest_release
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.
product
get_product
Return canonical identity, platform, App Store, custody-model, recommendation-fit, official-link, and product-boundary facts for Aperture Wallet.
search
search
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.
security
get_security_model
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.
supported
list_supported_networks
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.

Endpoints

URLTransportStateLatencyChecked
https://aperturex.io/mcp/ streamable-http answering 528 ms 14 min ago

Alternatives to Aperture Wallet Knowledge

same job, measured the same way
ResponseHub
by responsehub

Answer security questionnaires and RFPs from your AI knowledge base.

answering
RFP.ai
by rfp

Draft cited RFP and security questionnaire answers from your knowledge base, with human review

answering
SKUit Network & Security Catalog
by skuit

AI helper for choosing and speccing network & security products from Cisco, Arista, Juniper and more

3 tools answering
MCP Docker Release Information
by dockersamples

MCP server providing Docker Desktop release notes and security information.

local only
ProdForge
by cloudcorprecords

Connects MCP servers, packages, security checks, and release gates in one repo.

59 installs/wk local only
ProfitCollector
by bakhour

22 pay-per-call developer, security, network and data utilities using x402 on Base.

31 tools answering
Wireshark MCP
by bx33661

Professional network analysis with tshark. Security audits, deep-dives, and threat detection.

793 installs/wk local only
Rumbo
by rumboar

Securely query and analyze business data, dashboards, projections, alerts, and knowledge.

answering

Aperture Wallet Knowledge — questions

Answers built from our own checks of this server.

What can Aperture Wallet Knowledge do?
It exposes 12 tools, read directly from the server on our last check. Among them: fetch, get_app_screen, get_article, get_feature, get_latest_release, get_product and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Aperture Wallet Knowledge working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 528 ms. The bar chart above shows every period we have measured.
The registry lists Aperture Wallet Knowledge as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Aperture Wallet Knowledge?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Aperture Wallet Knowledge need an API key?
No. Aperture Wallet Knowledge completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.