Skip to content

Add Slashr to community servers list#3824

Open
simonmorley wants to merge 2 commits intomodelcontextprotocol:mainfrom
NullRabbitLabs:main
Open

Add Slashr to community servers list#3824
simonmorley wants to merge 2 commits intomodelcontextprotocol:mainfrom
NullRabbitLabs:main

Conversation

@simonmorley
Copy link
Copy Markdown

Description

Adds [Slashr](https://slashr.dev) to the community servers list — a live cross-chain validator incident MCP server covering Solana, Ethereum, Sui, and Cosmos.

Publishing Your Server

Already submitted to the MCP Registry via mcp-publisher.

Server Details

  • Server: Slashr (mcp.slashr.dev)
  • Changes to: Community servers list (README.md)

Motivation and Context

No existing MCP server surfaces blockchain validator incident data. Slashr tracks delinquency, slashing, jailing, and missed votes in real time across four networks, and exposes this via a hosted remote MCP server. Useful for agents monitoring staking portfolios, validator operations, or delegator health.

Tools exposed:

  • get_validator_incidents — incident history by address and chain
  • get_validator_stats — current performance, stake, commission
  • get_scan_results — infrastructure scan results, CVEs, port states
  • get_rankings — worst/most reliable validators by period
  • check_wallet — delegation health for a wallet address

Transport: Streamable HTTP · Auth: Bearer token · Read-only

How Has This Been Tested?

Tested with Claude Desktop and Claude.ai. Verified all five tools return structured data across Solana, Ethereum, Sui, and Cosmos endpoints.

Breaking Changes

None.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the [MCP Protocol Documentation](https://modelcontextprotocol.io)
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Developer docs and quickstart at [slashr.dev/developers](https://slashr.dev/developers). The server is read-only with Bearer token auth — no write access to any chain or wallet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant