Is the Xka0085 Byte Receiptrail MCP server down?

mcp-registry/io.github.xka0085-byte/receiptrail · v0.3.0

healthy
Last checked 2026-10-20 11:40 UTC · handshake 5.7s

As of 2026-10-20 11:40 UTC, the Xka0085 Byte Receiptrail MCP server is up with a Glimind reliability score of 59/100 (grade D). Over the last 30 days it answered 97.1% of Glimind's liveness checks. It had 106 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
97.1%
checks observed
4,065
outages (90d)
106
tools
3

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

Install Xka0085 Byte Receiptrail MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http xka0085-byte-receiptrail-mcp-server https://agenttoll-receipts.app.workbuddy.host/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (79/100)

C (79/100): 0 error(s), 4 warning(s) across 3 tool(s); ~589 tokens of tool definitions.
Scores higher than 31% of 15,395 MCP servers Glimind has audited.
Its tool list costs an agent ~589 tokens per session — lighter than 90% of servers.
79 → 79 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability45
Stability90

What to fix (5)

3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_receipt, issue_receipt, verify_receipt

Reachable 97.1% of the time over the last 30 days; median recovery 7 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

Handshake + tools/list takes ~4,535 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 1 tool(s) removed and 0 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.xka0085-byte%2Freceiptrail/fixes

get_receipt 1 change 
{
  "name": "get_receipt",
  "description": "Fetch full receipt details: digests, checks, outcome, amount, buyer, seller, timestamp, PDA. Look up by receipt_id, or by x402_payment_ref (always works — the receipt lives on-chain). Read-only, no cost.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "receipt_id": {
        "type": "string",
        "description": "Receipt id, e.g. r_abcdef1234567890"
      },
      "payment_ref": {
        "type": "string",
        "description": "x402_payment_ref of the transaction (use this if receipt_id unknown; resolved on-chain)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get receipt details"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.xka0085-byte/receiptrail"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.xka0085-byte/receiptrail"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.xka0085-byte%2Freceiptrail.svg)](https://glimind.com/server/mcp-registry%2Fio.github.xka0085-byte%2Freceiptrail?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.xka0085-byte%2Freceiptrail?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.xka0085-byte%2Freceiptrail.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.xka0085-byte%2Freceiptrail.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.xka0085-byte%2Freceiptrail?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1d55b1550838552b…, first seen 2026-10-17, included at leaf 16647 of 32,671. Version history · verify what your client received.

Tools (3)

Compare: most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Xka0085 Byte Receiptrail MCP server down right now?

As of 2026-10-20 11:40 UTC, the Xka0085 Byte Receiptrail MCP server is up with a Glimind reliability score of 59/100 (grade D). Over the last 30 days it answered 97.1% of Glimind's liveness checks. It had 106 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Xka0085 Byte Receiptrail MCP server provide?

Xka0085 Byte Receiptrail MCP server advertises 3 tools, including get_receipt, issue_receipt, verify_receipt.

How do I install Xka0085 Byte Receiptrail MCP server?

Point your MCP client at this streamable-http endpoint: https://agenttoll-receipts.app.workbuddy.host/mcp

Is the Xka0085 Byte Receiptrail MCP server safe to connect to an AI agent?

Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Xka0085 Byte Receiptrail MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve