AgentToll Receipts

io.github.xka0085-bytePublished by GitHub account xka0085-bytev0.1.1Updated Oct 1, 2026

On-chain x402 delivery receipts on Solana: hash-locked, verifiable proof of delivery.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote MCP endpoint that provides hash-locked, verifiable delivery receipts for x402 payments on Solana.

What you can do
The manifest lists no tools, so capabilities come from the short description only. It is described as issuing on-chain x402 delivery receipts on Solana. Receipts are described as hash-locked and verifiable proof of delivery. No further operations, inputs or outputs are documented.
When to use it
Consider it when you need verifiable proof that an x402 payment on Solana was matched by delivery, and want an assistant to work with those receipts. Without a tool list or documentation, confirm its actual behavior before relying on it.
Requirements
A remote streamable HTTP endpoint; no local runtime, packages, environment variables or headers are declared. The manifest declares no authentication, so access requirements are unclear. Network access to the hosted endpoint is needed.
Before you install
It concerns on-chain payments on Solana, so treat any receipt as financial evidence and verify it independently. The manifest declares no authentication, so check who can read or create receipts. No tools or documentation are published, so behavior is unverified.

Installation

In SourceWeft

  1. Open AgentToll Receipts in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.xka0085-byte%2Fagenttoll-receipts/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agenttoll-receipts": {
      "type": "http",
      "url": "https://agenttoll-receipts.app.workbuddy.host/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.1LatestSep 17, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.