Solana AI Registries

Created By
openSVMa year ago
Solana Protocol Design for Agent and MCP Server Registries
Overview

What is Solana AI Registries?

Solana AI Registries is a comprehensive on-chain registry system designed for autonomous AI agents and Model Context Protocol (MCP) servers on the Solana blockchain.

How to use Solana AI Registries?

To use the Solana AI Registries, developers need to set up the Solana CLI, clone the repository, and follow the provided instructions to build and deploy the registry programs. Users can interact with the registries through various programming languages like Rust, JavaScript, and Python.

Key features of Solana AI Registries?

  • Decentralized directories for autonomous agents and MCP servers.
  • Hybrid storage model for efficient data management.
  • Event-driven architecture for off-chain indexing and querying.
  • Comprehensive validation and security features.
  • 100% protocol compliance with A2A, AEA, and MCP specifications.

Use cases of Solana AI Registries?

  1. Registering and managing autonomous AI agents.
  2. Discovering and interacting with MCP servers for AI tools and resources.
  3. Facilitating communication between different AI agents in a decentralized manner.

FAQ from Solana AI Registries?

  • What is the purpose of the Agent Registry?

    The Agent Registry serves as a decentralized directory for autonomous agents, allowing for easy discovery and interaction.

  • How can I register an agent?

    You can register an agent by using the provided API instructions to create a new agent entry in the registry.

  • Is there a cost associated with using the registries?

    Yes, there are transaction fees associated with registration and updates, but querying the registries is free.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
openSVM
Star
4
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago