MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
X402 Notary is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
trust score
6
downloads a day
local
runs on your machine
712
downloads in 30d
What it does
The notary of the x402 agent economy, by ForgeMesh Labs. Cryptographic receipts for AI outputs: notarize any model inference with a signed Ed25519 attestation, sha256 content hash, and Merkle chain-anchor on Base or Solana — $0.001 per call via x402 USDC
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user x402-notary-mcp '--' npx -y @forgemeshlabs/x402-notary-mcp
# 2 — ask your agent for something these tools do
# notarize_inference, notarize_batch, verify_attestation and 3 more
X402 Notary costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts X402 Notary as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user x402-notary-mcp '--' npx -y @forgemeshlabs/x402-notary-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take WALLET_PRIVATE_KEY (Dedicated low-balance Base wallet private key for x402 USDC micropayments. Optional — verification tools work without it. Never use your primary wallet.), NOTARY_RAIL (Payment rail: base or solana. Defaults to base, or solana when NOTARY_BASE_URL contains notary-solana.), NOTARY_BASE_URL (Notary API origin. Use https://notary.forgemesh.io for Base or https://notary-solana.forgemesh.io for Solana.), SOLANA_PRIVATE_KEY (Dedicated low-balance Solana keypair for x402 USDC micropayments. Supports JSON byte array, base58, base64, or hex. Optional — verification tools work without i) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get a cryptographic receipt for one AI inference. Returns a signed Ed25519 attestation, sha256 content hash, and Merkle chain-anchor status for {prompt, response, model_id}. The notary does NOT store your prompt or response — only the hash is retained. Costs $0.001 USDC via x402 (requires…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prompt | string | yes | The exact prompt/input that was sent to the model |
| response | string | yes | The exact model output you want a receipt for |
| model_id | string | yes | Model identifier, e.g. 'openai/gpt-5' or 'claude-fable-5' |
| client_timestamp | string | no | Optional ISO-8601 time the inference ran. Included in the content hash if provided. |
Notarize up to 20 AI inferences in one call — one signed attestation per record. Ideal for audit trails and agent pipelines. Costs $0.005 USDC via x402 (requires WALLET_PRIVATE_KEY for a Base wallet).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| records | array | yes | 1-20 records of {prompt, response, model_id, client_timestamp?} |
FREE — verify any attestation issued by the notary. Supply the attestation_id plus either the original content ({prompt, response, model_id}) or its content_hash. Returns the Ed25519 signature check, hash comparison, and a Merkle inclusion proof once the batch is sealed. No wallet needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attestation_id | string | yes | Attestation id (att_…) from a receipt |
| content_hash | string | no | Alternative to supplying full content: the sha256 content hash to compare directly |
FREE — fetch the public receipt for an attestation: content hash, model, timestamps, Ed25519 signature, and Merkle anchor proof. Raw prompt/response are never stored, so receipts contain proof material only. No wallet needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attestation_id | string | yes | Attestation id (att_…) |
FREE — live aggregate stats: total notarizations, 24h volume, top models by attestation count, sealed/anchored Merkle batches. No wallet needed.
No parameter schema on file.
FREE — the notary's Ed25519 public key (base64, raw 32 bytes) for fully offline signature verification. No wallet needed.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install X402 Notary or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 96 / 100
Release 0.1.10 · scanned 15 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 1 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest8a05fa9ba85c999ca34f266541ed2256b84931b6d273bc9f69cb14a1ea0b818c
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (6 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| notarize_inference | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| notarize_batch | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| verify_attestation | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_receipt | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| notary_stats | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| notary_pubkey | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest8a05fa9ba85c999c
Scanned2026-10-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.10. Pin a release below and the command asks for exactly that one.
0.1.10
8 Oct 2026
latestNo release note was published with this version.
0.1.9
5 Oct 2026
No release note was published with this version.
0.1.8
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish X402 Notary can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.