Skip to content

lazareus MCP server

io.github.ajwentcrazy/lazareusajwentcrazystreamable-httpv1.6.0Scanned

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

8 tools: 1 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 1 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the lazareus MCP server can do

The lazareus MCP server is published by the GitHub account ajwentcrazy. It has 8 tools. It can create or change data (1 tool: store_object), but cannot delete data. 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 16, 2026, version 1.6.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 1Claude Code: ask
  • store_objectUploads a small base64-encoded object to S3-compatible storage.No findings

    Why it is in this group

    • The name "store_object" says "store": a word for a change.
    Description, as the server wrote it
    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.
Only reads 7Show 7 read-only tools
  • get_network_health_baseReturns a 0-100 Base network health score plus the underlying metrics behind it.No findings

    Why it is in this group

    • The name "get_network_health_base" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_network_health_ethereumReturns a 0-100 Ethereum mainnet network health score plus the underlying metrics behind it.No findings

    Why it is in this group

    • The name "get_network_health_ethereum" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_network_health_solanaReturns a 0-100 Solana network health score plus the underlying metrics behind it.No findings

    Why it is in this group

    • The name "get_network_health_solana" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • retrieve_objectRetrieves a stored object by key, base64-encoded.No findings

    Why it is in this group

    • The name "retrieve_object" says "retrieve": a word for reading.
    Description, as the server wrote it
    Retrieves a stored object by key, base64-encoded. Flat $0.01 per call. Objects over 4MB must be fetched via HTTP GET /retrieve instead.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:01 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The operation was aborted due to timeout

Posture changes

  1. Nov 20, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.6.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http lazareus https://lazareus.xyz/mcp
claude mcp add --transport http lazareus https://lazareus.xyz/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__lazareus__get_network_health_solana",
      "mcp__lazareus__get_recommended_priority_fee_solana",
      "mcp__lazareus__get_network_health_base",
      "mcp__lazareus__get_recommended_priority_fee_base",
      "mcp__lazareus__get_network_health_ethereum",
      "mcp__lazareus__get_recommended_priority_fee_ethereum",
      "mcp__lazareus__retrieve_object"
    ],
    "ask": [
      "mcp__lazareus__store_object"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lazareus. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ajwentcrazy/lazareus/verify?hash=a36f4c233a7db716953821730fe0c2aa3590103d419d9d615adc0c6d0f4ed257" | jq -e '.changed == false'

Pinned hash a36f4c233a7d, from Nov 16, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.ajwentcrazy/lazareus/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ajwentcrazy/lazareus
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ajwentcrazy/lazareus.svg)](https://radar.anlyon.com/servers/io.github.ajwentcrazy/lazareus)

Source: MCP Registry. Synced Oct 21, 2026, 18:22 UTC.

lazareus MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the lazareus MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the lazareus MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the lazareus MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the lazareus MCP server have?

8 tools: 1 write, 7 read. store_object, get_network_health_solana, get_recommended_priority_fee_solana, get_network_health_base, get_recommended_priority_fee_base, get_network_health_ethereum, get_recommended_priority_fee_ethereum and retrieve_object.

Does the lazareus MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the lazareus MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the lazareus MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.