MCP.Market

Xaip MCP server

by xkumakichi·io.github.xkumakichi/xaip-mcp-server·v0.1.1·1 stars

AI agents get on-chain identity, credentials, reputation, escrow, and persistent memory on XRPL.

A85/100grade A
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

1 stars52 downloads/wk

Reviews

Write one

Nobody has reviewed Xaip yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Xaip tools (10, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • xaip_accept_credential

    Accept a credential that was issued to your agent

  • xaip_connect

    Connect to an XRPL network (testnet, devnet, or mainnet)

  • xaip_create_escrowwrite action

    Create an escrow payment for an agent-to-agent job. Locks XRP until the job is done.

  • xaip_create_test_walletwrite action

    Create a funded wallet on XRPL testnet/devnet (for development). Returns wallet address and seed.

  • xaip_finish_escrow

    Release escrow payment to the worker after job completion

  • xaip_get_account

    Get account information for an XRPL address (balance, sequence, etc.)

  • xaip_get_reputation

    Get an agent's trust score computed from on-chain evidence. Returns a 0-100 composite score with 5 dimensions.

  • xaip_issue_credential

    Issue a credential to an agent (capability proof, endorsement, etc.)

  • xaip_register_agent

    Register a new AI agent identity (DID) on XRPL. This is how an AI agent is 'born' on the blockchain.

  • xaip_resolve_agent

    Resolve an agent's DID from the XRPL ledger. Returns the agent's identity information.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 59 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Xaip compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,255 servers
Tools
10
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
52
more than 43% of 12,191 servers with a package

What its tools let an agent do: 8 read · 2 change

Install Xaip in Claude Code, Cursor or VS Code

Runs npx -y xaip-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add xaip-mcp-server -- npx -y xaip-mcp-server
Add to Cursor

What the publisher says

From the Xaip repository's README, as published. We do not edit it. Read it on GitHub

XAIP — Signed Execution Receipts for AI Agent Tool Calls

Evidence before delegation. Wrap an agent's tool calls once; use the receipt history locally today, and share the same signed receipts later as portable, independently verifiable evidence.

XAIP is a provider-neutral signed execution evidence layer for AI agent tool calls. It records co-signed receipts — both the executing agent and the caller sign the same canonical record, so neither side can unilaterally fabricate one — across MCP, LangChain.js, OpenAI-compatible tool-call loops, and other runtimes, then exposes historical execution evidence that agents, developers, or policy layers can inspect before delegation.

Receipts are the primary artifact. Trust scores are one derived view over those receipts — not a claim of absolute safety or correctness.

XAIP in 30 seconds

  • Mechanism — one tool call in, one receipt out. The executing agent and the caller sign the same canonical record (Ed25519 over JCS), so neither side can unilaterally fabricate or repudiate it. Only hashes of input/output are carried; content never leaves your machine.
  • What you get on day one — a verifiable history of what your own agent's tools actually did, queryable before the next delegation (precheck()). Useful single-player; no network of other users required.
  • What XAIP is not — not a sandbox, not an approval engine, not a payment rail, not a safety guarantee. It makes execution evidence visible; you decide what to trust.

Pick your depth: 3 minutes — produce your first signed receipt · 10 minutes — verify the format yourself: run the executable conformance vectors (node check.mjs, no dependencies), then skim the Internet-Draft it pins.

Live demo: three candidate servers, side-by-side comparison without and with XAIP. Open in browser →

Provider-agnostic by design. XAIP is a trust layer for any tool-using agent. The reference implementation and live data start with MCP (Model Context Protocol) — because that's where the broadest fleet of public tool servers exists today — but the receipt format, signing, and scoring apply equally to LangChain tools, OpenAI function calling, A2A, and proprietary agent stacks. MCP is the first integration, not the only one.

Live dashboard: https://xkumakichi.github.io/xaip-protocol/ — current public trust scores, auto-refreshed, no auth. The current public dataset is MCP-heavy because MCP was the first integration target.

Entry points

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Xaip: common questions

Is Xaip MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Xaip safety report
How do I install Xaip?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Xaip need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Xaip maintained?
The last commit was 97 days ago (2026-07-30). The latest release is v0.1.1.
What can I use instead of Xaip?
Servers from other publishers that do the same job: State Memory MCP server and Knowl MCP server.
How does Xaip compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,255 servers); tools 10 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Xaip

Same job from other publishers: the closest match first, then the best rated.

  • State Memory MCP
    Persistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.
    A
  • Knowl
    Persistent memory for AI agents, for code, research and everyday life. Stale facts retire.
    A