Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.ajwentcrazy/lazareus

REMOTE · LAZAREUS.XYZ · SCANNED AUG 20

S3 storage and Solana/Base/Ethereum health checks for AI agents, paid per call via x402.

Available components

0 this week 64 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 439 tokens (~54/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 13 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 8 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · lazareus.xyz

# add to Claude Code
claude mcp add --transport http ajwentcrazy-lazareus https://lazareus.xyz/mcp
# ~/.codex/config.toml
[mcp_servers.ajwentcrazy-lazareus]
url = "https://lazareus.xyz/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ajwentcrazy-lazareus": {
      "type": "remote",
      "url": "https://lazareus.xyz/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ajwentcrazy-lazareus --url https://lazareus.xyz/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ajwentcrazy-lazareus:
    url: "https://lazareus.xyz/mcp"
// mcp.json
{
  "mcpServers": {
    "ajwentcrazy-lazareus": {
      "type": "http",
      "url": "https://lazareus.xyz/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Aug 26 +1
    • Schema quality: 48 → 54 functional
    • New tool “retrieve_object” functional
    • New tool “store_object” functional
  • 18 Aug 26 −1
    • Tool “get_network_health” was removed security
    • Tool “get_recommended_priority_fee” was removed security
    • Tool “get_network_health_base” rewrote its description, which is the text the model reads security
    • Tool “get_network_health_ethereum” rewrote its description, which is the text the model reads security
    • Tool “get_recommended_priority_fee_base” rewrote its description, which is the text the model reads security
    • Tool “get_recommended_priority_fee_ethereum” rewrote its description, which is the text the model reads security
    • Schema quality: 61 → 48 functional
    • Server version: 0.2.0 → 0.3.0 functional
    • New tool “get_network_health_solana” functional
    • New tool “get_recommended_priority_fee_solana” functional
  • 15 Aug 26 0
    • Schema quality: 120 → 368 functional
    • New tool “get_network_health_base” functional
    • New tool “get_network_health_ethereum” functional
    • New tool “get_recommended_priority_fee_base” functional
    • New tool “get_recommended_priority_fee_ethereum” functional
  • 11 Aug 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Aug 26 +1
    • Stability: unverified → 0.03 functional
  • 7 Aug 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Aug 2026 · Probed https://lazareus.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lazareus.xyz CN=YE1,O=Let's Encrypt,C=US 6 Aug 2026 4 Nov 2026 ECDSA 256 ECDSA-SHA384 6bebd55e4343a989b86038e0069a773454c
SANs: lazareus.xyz, www.lazareus.xyz
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of lazareus.xyz. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
lazareus.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://lazareus.xyz/mcp Verified 200
http (plaintext) http://lazareus.xyz/mcp HTTPS enforced 301 https://lazareus.xyz/mcp
MCP tools · 8 exposed · ~439 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
get_network_health_base ~47

Returns a 0-100 Base network health score plus the underlying metrics behind it. Useful before executing a timing-sensitive transaction. Paid: $0.002 per call via x402.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_network_health_ethereum ~50

Returns a 0-100 Ethereum mainnet network health score plus the underlying metrics behind it. Useful before executing a timing-sensitive transaction. Paid: $0.002 per call via x402.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_network_health_solana ~49

Returns a 0-100 Solana network health score plus the underlying metrics behind it. Useful before executing a timing-sensitive transaction. Paid: $0.002 per call via x402.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_recommended_priority_fee_base ~46

Recommends a Base transaction priority fee based on recent network activity, at low/medium/high confidence levels. Paid: $0.002 per call via x402.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_recommended_priority_fee_ethereum ~49

Recommends a Ethereum mainnet transaction priority fee based on recent network activity, at low/medium/high confidence levels. Paid: $0.002 per call via x402.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_recommended_priority_fee_solana ~48

Recommends a Solana transaction priority fee based on recent network activity, at low/medium/high confidence levels. Paid: $0.002 per call via x402.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

retrieve_object ~60

Retrieves a stored object by key, base64-encoded. Flat $0.01 per call. Objects over 4MB must be fetched via HTTP GET /retrieve instead.

NameTypeReqDescription
keystringyesThe key returned by store_object or PUT /store

No output schema declared.

No examples provided.

store_object ~90

Uploads a small base64-encoded object to S3-compatible storage. ~$1/GB, $0.01 minimum, capped at 4MB (larger files: use HTTP PUT /store instead). Returns a key for retrieve_object.

NameTypeReqDescription
content_base64stringyesBase64-encoded bytes to store
content_typestringMIME type, defaults to application/octet-stream

No output schema declared.

No examples provided.