Identity

Created By
agntcya year ago
AGNTCY Identity allows to onboard, create and verify identities for Agents, Model Context Protocol (MCP) Servers and Multi-Agent Systems (MASs).
Overview

What is AGNTCY Identity?

AGNTCY Identity is a framework that allows for the onboarding, creation, and verification of identities for agents, Model Context Protocol (MCP) Servers, and Multi-Agent Systems (MASs) using secure and decentralized techniques.

How to use AGNTCY Identity?

To use AGNTCY Identity, you can install the Issuer CLI and Node Backend, which allows you to generate, register, and verify identities and badges for agents and MCP servers. Follow the setup instructions provided in the documentation to get started.

Key features of AGNTCY Identity?

  • Identity creation for agents and MCP servers.
  • Integration with existing identity providers (IdPs).
  • Creation and verification of badges for authentication.
  • Command-line interface for managing identities and metadata.

Use cases of AGNTCY Identity?

  1. Securely onboarding agents in a multi-agent system.
  2. Verifying identities for trusted communication between agents.
  3. Managing identities and credentials for MCP servers.

FAQ from AGNTCY Identity?

  • Can AGNTCY Identity integrate with existing identity providers?

Yes, AGNTCY Identity supports integration with various IdPs like Okta.

  • Is there a command-line interface available?

Yes, the Issuer CLI allows for managing identities and credentials easily.

  • How does AGNTCY Identity ensure security?

It uses verifiable credentials and unique identifiers to ensure secure authentication and communication.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
agntcy
Star
5
Language
Go
License
Apache-2.0 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)

a day ago