# Akashi Notari (remote · anchor.akashi-notari.com)

Proof of existence for files: anchor a SHA-256 hash on Base, look up proofs. Paid with x402.

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

## Components

- remote · `anchor.akashi-notari.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/self-reality-akashi-notari/anchor.md), [page](https://verifymcp.io/servers/self-reality-akashi-notari/anchor)

## Channel facts

- Endpoint: `https://anchor.akashi-notari.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-11-05.

- **Endpoint Security**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 84/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 257 tokens (~128/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Akashi Notari MCP server?

Akashi Notari is a hosted endpoint at https://anchor.akashi-notari.com/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 self-reality-akashi-notari 'https://anchor.akashi-notari.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "self-reality-akashi-notari": {
      "url": "https://anchor.akashi-notari.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "self-reality-akashi-notari": {
      "type": "http",
      "url": "https://anchor.akashi-notari.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.self-reality-akashi-notari]
url = "https://anchor.akashi-notari.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "self-reality-akashi-notari": {
      "type": "remote",
      "url": "https://anchor.akashi-notari.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add self-reality-akashi-notari --url 'https://anchor.akashi-notari.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  self-reality-akashi-notari:
    url: "https://anchor.akashi-notari.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "self-reality-akashi-notari": {
      "Transport": "http",
      "Url": "https://anchor.akashi-notari.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add self-reality-akashi-notari -t streamable-http -u 'https://anchor.akashi-notari.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "self-reality-akashi-notari": {
      "type": "http",
      "url": "https://anchor.akashi-notari.com/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-11-05 (score 82, +1)

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

### 2026-11-02 (score 81, +1)

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

### 2026-10-31 (score 80, +1)

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

### 2026-10-29 (score 79, +1)

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

### 2026-10-27 (score 78, +1)

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

### 2026-10-25 (score 77, +1)

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

### 2026-10-23 (score 76, +1)

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

### 2026-10-21 (score 75, +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.

## MCP tools (2)

### `find_proof` (~89 tokens)

Find a proof of existence

Free. Look up whether a file hash is anchored on Base and when, or read the proof written by a transaction. Pass `hash` or `tx`. Call it before anchor_hash to avoid paying for a hash that is already anchored.

Input parameters:

- `hash` (string): SHA-256 of the file, 64 hex characters
- `tx` (string): Transaction hash; use instead of hash

### `anchor_hash` (~122 tokens)

Anchor a file hash

Paid with x402 (USDC on Base). Writes the SHA-256 hash of a file on-chain; the block time becomes the proof of existence. Compute the hash locally and never send the file. The hash, the filename and the payer address become public and permanent. Without a payment in _meta["x402/payment"] the result is the payment requirement.

Input parameters:

- `filename` (string): Optional name to record with the hash: a-z 0-9 - _ .
- `hash` (string, required): SHA-256 of the file, 64 hex characters

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/self-reality-akashi-notari/anchor#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79
- 2026-10-28: 78
- 2026-10-27: 78
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72
- 2026-10-14: 72
- 2026-10-13: 71
- 2026-10-12: 71
- 2026-10-11: 70
- 2026-10-10: 70
- 2026-10-09: 69

## Common questions

### What is the Akashi Notari MCP server?

Akashi Notari is an MCP server listed in the public MCP registry as io.github.self-reality/akashi-notari. Proof of existence for files: anchor a SHA-256 hash on Base, look up proofs. Paid with x402. This page covers its hosted endpoint (https://anchor.akashi-notari.com/mcp).

### Is the Akashi Notari MCP server safe to use?

Akashi Notari scores 82 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 Akashi Notari MCP server expose?

Akashi Notari exposes 2 tools: find_proof, anchor_hash. Their descriptions and schemas cost roughly 211 tokens of context every time the server is loaded.

### Does the Akashi Notari MCP server require authentication?

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

### Is the Akashi Notari MCP server still maintained?

Akashi Notari 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.

## Links

- Remote endpoint: https://anchor.akashi-notari.com/mcp
- Repository: https://github.com/self-reality/verifier
- Website: https://akashi-notari.com/
- Changelog RSS feed: https://verifymcp.io/servers/self-reality-akashi-notari/anchor.xml
- Changelog JSON feed: https://verifymcp.io/servers/self-reality-akashi-notari/anchor.json
- HTML version of this page: https://verifymcp.io/servers/self-reality-akashi-notari/anchor