Koskamo

Akashi Notari MCP

An MCP server that anchors SHA-256 file hashes on the Base blockchain to provide proof of existence. It offers tools to find existing proofs and anchor new hashes, with the latter requiring payment via the x402 protocol.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Akashi Notari MCP logo, by Akashi NotariCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by Akashi Notari
MCP endpoint (Streamable HTTP)
https://anchor.akashi-notari.com/mcp
Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (1)

Can change data (1)

2 of 2 have a description · 2 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Find proof of existence for a file hash
  • Anchor a file hash on-chain
  • Verify transaction-based proofs

Source and maintenance

Community listingRegistry 1.1.0
Maintenance checked

Protocol and capabilities

Server
akashi-notari 1.1.0
MCP protocol negotiated in check
2025-11-25
Tools
2 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Proof of existence for files. Compute the SHA-256 of the file locally; never send the file. find_proof is free. anchor_hash costs a small USDC fee on Base, paid with x402.

Tools

2 advertised

find_proof — Find a proof of existence
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

find_proof input schema
{
  "type": "object",
  "properties": {
    "tx": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{64}$",
      "description": "Transaction hash; use instead of hash"
    },
    "hash": {
      "type": "string",
      "pattern": "^(0x)?[0-9a-fA-F]{64}$",
      "description": "SHA-256 of the file, 64 hex characters"
    }
  }
}
find_proof annotations
{
  "readOnlyHint": true,
  "openWorldHint": true
}
anchor_hash — Anchor a file hash
Advertised by the server during the last successful anonymous check.
Open-world

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.

anchor_hash input schema
{
  "type": "object",
  "required": [
    "hash"
  ],
  "properties": {
    "hash": {
      "type": "string",
      "pattern": "^(0x)?[0-9a-fA-F]{64}$",
      "description": "SHA-256 of the file, 64 hex characters"
    },
    "filename": {
      "type": "string",
      "maxLength": 128,
      "description": "Optional name to record with the hash: a-z 0-9 - _ ."
    }
  }
}
anchor_hash annotations
{
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
271 ms
95th percentile latency
271 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 271 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http akashi-notari-mcp https://anchor.akashi-notari.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add akashi-notari-mcp --url https://anchor.akashi-notari.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable akashi-notari-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "akashi-notari-mcp": {
      "url": "https://anchor.akashi-notari.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "akashi-notari-mcp": {
      "type": "streamableHttp",
      "url": "https://anchor.akashi-notari.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start akashi-notari-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "akashi-notari-mcp": {
      "type": "http",
      "url": "https://anchor.akashi-notari.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http akashi-notari-mcp https://anchor.akashi-notari.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://anchor.akashi-notari.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "akashi-notari-mcp": {
      "serverUrl": "https://anchor.akashi-notari.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Akashi Notari MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.