symbiotic-relay

Descriptor

Candidate descriptor · transport http

Tools

• get_aggregation_proof — Get aggregation proof
• get_aggregation_proofs_by_epoch — Get aggregation proofs by epoch
• get_aggregation_status — Get aggregation status, can be sent only to aggregator nodes
• get_last_all_committed — Get last committed epochs for all settlement chains
• get_last_committed — Get last committed epoch for a specific settlement chain
• get_current_epoch — Get current epoch
• sign_message — Sign a message
• get_signature_request_i_ds_by_epoch — Get all signature request IDs by epoch
• get_signature_request — Get signature request by request id
• get_signature_requests_by_epoch — Get all signature requests by epoch
• get_signatures_by_epoch — Get signature by epoch
• get_signatures — Get signature by request id
• listen_proofs — Stream aggregation proofs in real-time. If start_epoch is provided, sends historical data first
• listen_signatures — Stream signatures in real-time. If start_epoch is provided, sends historical data first
• listen_validator_set — Stream validator set changes in real-time. If start_epoch is provided, sends historical data first
• get_validator_set — Get current validator set
• get_custom_schedule_node_status — Checks if the current node should be active based on a custom schedule derived from the validator set. This enables external applications to use the relay's validator set for coordinating distributed tasks, such as deciding which application instances should commit data on-chain or perform other coordinated actions. The schedule ensures deterministic but randomized selection of active nodes at any given time.
• get_validator_set_header — Get validator set header
• get_validator_set_metadata — Get validator set metadata like extra data and request id to fetch aggregation and signature requests
• get_validator_by_address — Get validator by address
• get_validator_by_key — Get validator by key
• get_local_validator — Get local validator

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

curl "https://apis.io/api/v1/mcp/symbiotic-relay"

curl "https://apis.io/api/v1/mcp?limit=25"