Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Attested Memory Market

REMOTE · HUB.ATTESTEDMEMORY.NET

Attestable memory, truth, provenance. Hybrid Ed25519 + ML-DSA-65 receipts; USDC settlement on Base.

+3 this week 72 Trust /100

Last scanned (2 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2045 tokens (~157/item across 13 items; 13 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 Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pipeline_invoke" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 14 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
Changelog

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.

  • 5 Nov 26 +2
    • Stability: fail → 0.80 functional
    • New tool “fair_random” functional
  • 4 Nov 26 −1
    • Stability: 0.73 → fail ▼ security
    • A breaking change shipped without a version bump: still 1.2.0 ▼ security
    • Tool “fair_random” was removed ▼ security
  • 3 Nov 26 +2
    • Stability: fail → 0.73 functional
    • New tool “fair_random” functional
  • 2 Nov 26 −1
    • Stability: 0.67 → fail ▼ security
    • A breaking change shipped without a version bump: still 1.2.0 ▼ security
    • Tool “fair_random” was removed ▼ security
  • 31 Oct 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.

  • 29 Oct 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.

  • 27 Oct 26 +1

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

  • 25 Oct 26 +1

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

Diagnostics

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 5 Nov 2026 · Probed https://hub.attestedmemory.net/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=attestedmemory.net CN=YE1,O=Let's Encrypt,C=US 7 Sept 2026 6 Dec 2026 ECDSA 256 ECDSA-SHA384 5ced163ef340fa3e66c0c283cfdc4263a7a
SANs: attestedmemory.net, hub.attestedmemory.net, memory.attestedmemory.net, monitor.attestedmemory.net, provenance.attestedmemory.net, truth.attestedmemory.net, www.attestedmemory.net
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 hub.attestedmemory.net. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
attestedmemory.net. 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
strict-transport-security max-age=31536000
content-security-policy frame-ancestors 'none'; base-uri 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hub.attestedmemory.net/mcp Verified 200
http (plaintext) http://hub.attestedmemory.net/mcp HTTPS enforced 301 https://hub.attestedmemory.net/mcp
MCP tools · 13 exposed · ~1,797 tokens

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 →

Tool Tokens
air_quality_now ~129

Current air quality at a place: PM2.5 and PM10 (µg/m³), US and European AQI, from Copernicus CAMS via Open-Meteo, with a signed receipt. Pass latitude and longitude, or a city. Costs $0.001 per call. The first 3 priced calls per caller are free.

NameTypeReqDescription
citystring–A city instead of coordinates, e.g. "Tokyo"; many spellings work (Токио, 東京).
latitudenumber–Latitude in degrees.
longitudenumber–Longitude in degrees.

No output schema declared.

No examples provided.

fair_random ~107

Verifiable random bytes for a draw, raffle or tie-break: an ECVRF output over your seed plus a proof anyone can check offline. The same seed always gives the same output, so publish the seed first to show the result was not picked. Costs $0.006 per call. The first 3 priced calls per caller are free.

NameTypeReqDescription
num_bytesinteger–Output length (default 32).
seedstringyesSeed or message the draw is bound to.

No output schema declared.

No examples provided.

market_invoke ~410

Invoke a capability found via market_search. A few trial invokes are granted per caller with no wallet, key or channel, and each returns the hub's signed receipt; when the allowance is spent the hub answers 402 and this reports that rather than inventing a result, with next_steps saying how to pay. Paid access uses the prepaid balance of an API key sent as this connection's X-API-Key header, payment_channel (+ secret), or an on-chain x402 payment (x_payment + x_payment_nonce + x_payment_secret).

NameTypeReqDescription
capability_idstringyesThe exact capability_id from market_search.
include_full_receiptboolean–Return the hub's raw response, including the full hybrid Ed25519 + ML-DSA-65 receipt signature (about 7 KB).
inputobject–Input object for the capability; {} when it takes none.
max_price_usdnumber–Atomic total-price ceiling. Copy the selected search result's max_price_usd here; the Hub returns price_limit_exceeded before work or payment if the route was repriced.
payment_authorizationobject––
payment_channelstring––
payment_channel_secretstring––
product_idstringyesThe product_id from market_search.
source_hubstring–The source_hub from market_search, when it shows one. Required for federated capabilities — most of the catalogue; omitting it makes the hub look for the capability locally and answer 404.
x_paymentstring–x402 seller-direct payment: the hash of the USDC transfer you broadcast for the 402's invoice (see next_steps).
x_payment_noncestring–The invoice nonce from the 402 that x_payment pays.
x_payment_secretstring–The payment_secret from that 402. The nonce and the transaction are public once mined; the secret is what shows you are the one who paid.

No output schema declared.

No examples provided.

market_search ~147

Search this hub's catalogue of live data and computation by what you need, in plain words. Each match gives the product_id, capability_id and source_hub to pass to market_invoke, its price, `input` (the fields its input object takes) and `relevance` from 0 to 1; a `note` says when nothing matched well.

NameTypeReqDescription
budgetnumber–Optional cap on price per call, in USD.
categorystring–Optional category filter, e.g. 'security'.
intentstringyesWhat you want done, in plain language.
limitinteger–Maximum results (default 10, max 50).

No output schema declared.

No examples provided.

nearby_sensors ~126

The nearest live public sensors to a point, one per layer asked for (e.g. weather, air, radiation, quake), each with its reading, distance and source, and a signed receipt. Costs $0.03 per call. The first 3 priced calls per caller are free.

NameTypeReqDescription
latitudenumberyesLatitude in degrees.
layersarray–Sensor layers to search, e.g. ["weather", "air"]; default weather.
longitudenumberyesLongitude in degrees.
max_kmnumber–Refuse sensors farther than this.

No output schema declared.

No examples provided.

pipeline_invoke ~109

Execute or continue the SAME prepared graph. Submit authorizations when the signed quote enables gas_sponsorship, otherwise buyer-signed transactions; none for free steps. Never submit both payment modes. Retain run_id/access_token and the exact bundle. Pending is not failure; repeat the same run or read pipeline_status. Never create a replacement purchase after a lost response.

NameTypeReqDescription
access_tokenstringyes–
authorizations–––
run_idstringyes–
transactions–––

No output schema declared.

No examples provided.

pipeline_prepare ~110

Validate a graph and return a signed quote and payment offers. No work or payment. Free steps require no wallet; paid steps require buyer wallet address. Use gas_mode=required to demand gas sponsorship or auto to prefer it. Inspect ready/blockers and gas_sponsorship. Sign offers LOCALLY, never provide a private key. Then call pipeline_invoke.

NameTypeReqDescription
gas_modestring––
max_budget_usd–––
nodesarrayyes–
walletstring––

No output schema declared.

No examples provided.

pipeline_refund ~93

Submit the original seller's refund authorization or resume the SAME refund. The recipient is the original buyer, amount is the paid step price, and the sponsor pays gas. Preserve the exact authorization after a lost response. Returns a separately signed credit note; the original bill is unchanged.

NameTypeReqDescription
access_tokenstringyes–
authorization–––
run_idstringyes–
step_idstringyes–

No output schema declared.

No examples provided.

pipeline_refund_prepare ~85

Prepare a cash refund for a verified paid step of a finished pipeline. This moves no money. The original seller must approve the exact EIP-3009 authorization locally; never send a private key. Refunds require seller cooperation and a configured gas sponsor.

NameTypeReqDescription
access_tokenstringyes–
run_idstringyes–
step_idstringyes–

No output schema declared.

No examples provided.

pipeline_refund_status ~71

Read the saved cash-refund status and signed credit note without broadcasting a transaction. No private key or RPC is required. Pending means resume the same refund, never send a replacement transfer.

NameTypeReqDescription
access_tokenstringyes–
run_idstringyes–
step_idstringyes–

No output schema declared.

No examples provided.

pipeline_status ~56

Read an existing pipeline, including cached signed result, without broadcasting payments or invoking providers. No wallet signer or blockchain RPC required. Inspect recovery.action for unresolved work.

NameTypeReqDescription
access_tokenstringyes–
run_idstringyes–

No output schema declared.

No examples provided.

weather_now ~129

Current weather at a place: temperature (°C), humidity (%), pressure (hPa) and wind (m/s) from the nearest live Open-Meteo relay within 75 km, with a signed receipt. Pass latitude and longitude, or a city. Costs $0.001 per call. The first 3 priced calls per caller are free.

NameTypeReqDescription
citystring–A city instead of coordinates, e.g. "Tokyo"; many spellings work (Токио, 東京).
latitudenumber–Latitude in degrees.
longitudenumber–Longitude in degrees.

No output schema declared.

No examples provided.

x402_check ~225

Check a signed x402 USDC payment before submitting it: recovers the EIP-712 signer, runs USDC's own checks and the seller's (payTo, amount, asset, network), and when the signature fails names the domain it was really made for (e.g. Base Sepolia's 'USDC' used on Base, where USDC is 'USD Coin'). Costs $0.003 per call. The first 3 priced calls per caller are free.

NameTypeReqDescription
authorizationobject–Instead of x_payment: from, to, value, validAfter, validBefore, nonce.
networkstring–With authorization: base, base-sepolia, … or eip155:<id>.
nowinteger–Unix seconds, to check the validity window.
requirementsobject–The 402's accepts entry: payTo, amount, asset, network.
signaturestring–With authorization: the 65-byte hex signature.
x_paymentstring–The X-PAYMENT header (base64).

No output schema declared.

No examples provided.

Install

How do I install the Attested Memory Market MCP server?

Attested Memory Market is a hosted endpoint at https://hub.attestedmemory.net/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 · hub.attestedmemory.net

# add to Claude Code
claude mcp add --transport http alexar76-attested-memory 'https://hub.attestedmemory.net/mcp'
Common questions

What is the Attested Memory Market MCP server?

Attested Memory Market is an MCP server listed in the public MCP registry as io.github.alexar76/attested-memory. Attestable memory, truth, provenance. Hybrid Ed25519 + ML-DSA-65 receipts; USDC settlement on Base. This page covers its hosted endpoint (https://hub.attestedmemory.net/mcp).

Is the Attested Memory Market MCP server safe to use?

Attested Memory Market scores 72 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 Attested Memory Market MCP server expose?

Attested Memory Market exposes 13 tools: market_search, market_invoke, pipeline_prepare, pipeline_invoke, pipeline_status, and 8 more. Their descriptions and schemas cost roughly 1,797 tokens of context every time the server is loaded.

Does the Attested Memory Market MCP server require authentication?

No. We connected to Attested Memory Market without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Attested Memory Market MCP server still maintained?

Attested Memory Market is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.