lazareus
Registry code: 88339b87fd71ada9
Solana network and validator health checks for AI agents, paid per call via x402.
from a public catalogue that lists it, not from the operator
- endpoint
- https://lazareus.xyz/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is lazareus live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is lazareus free to use?
- No — it charges per call, from 0.002 USDC, quoted in its own 402 answers.
- What tools does lazareus have?
- 8 tools: get_network_health_base, get_network_health_solana, store_object, retrieve_object, get_network_health_ethereum, get_recommended_priority_fee_base, get_recommended_priority_fee_ethereum, get_recommended_priority_fee_solana.
- Is lazareus safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.9%· all time 98.9%
last good check
of 8 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- crypto & onchain
- used for
- check blockchain network health
- get recommended priority fee
- store a small object
- retrieve a stored object
- takes → gives
- text, data → data
- tools
- 7 reads1 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_network_health_base reads 0.002 USDC paid 20h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_network_health_solana reads 0.002 USDC paid 20h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesstore_object changes data paid never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "content_base64" ], "properties": { "content_type": { "type": "string", "description": "MIME type, defaults to application/octet-stream" }, "content_base64": { "type": "string", "description": "Base64-encoded bytes to store" } }, "additionalProperties": false }arguments 18 linesretrieve_object reads paid never probed
Retrieves a stored object by key, base64-encoded. Flat $0.01 per call. Objects over 4MB must be fetched via HTTP GET /retrieve instead.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "key" ], "properties": { "key": { "type": "string", "description": "The key returned by store_object or PUT /store" } }, "additionalProperties": false }arguments 14 linesget_network_health_ethereum reads 0.002 USDC paid 20h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_recommended_priority_fee_base reads 0.002 USDC paid 3h ago
Recommends a Base transaction priority fee based on recent network activity, at low/medium/high confidence levels. Paid: $0.002 per call via x402.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_recommended_priority_fee_ethereum reads 0.002 USDC paid 3h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_recommended_priority_fee_solana reads 0.002 USDC paid 3h ago
Recommends a Solana transaction priority fee based on recent network activity, at low/medium/high confidence levels. Paid: $0.002 per call via x402.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id88339b87fd71ada9.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/88339b87fd71ada9/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/88339b87fd71ada9?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.