Identity

MCP其他

提供方 agntcy

其他 未标注 OAuth 授权 社区 / 第三方 CursorCodexZed
查看接入方式

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

一句话选型结论

按资料字段整理

Identity 属于其他类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Cursor、Codex、Zed,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类其他 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

其他
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

identity

安装与配置

未标注 OAuth 授权
上游未给出传输方式
go install github.com/agntcy/identity/cmd/issuer@latest && \\

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
接入外部数据

把外部系统的数据接进对话。

自动化重复操作

把固定步骤交给模型跑。

补充工具能力

给模型补上它原本没有的能力。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Cursor、Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在其他场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、Codex 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Identity当前 未标注 未标注 未标注 有 未标注
gemini-cli 未标注 stdio · 本地进程 本地部署 有 2026-04-13
ext-apps 未标注 stdio · 本地进程 本地部署 有 2026-04-19
northcinder 未标注 stdio · 本地进程 本地部署 有 2026-08-23
fastctx 未标注 stdio · 本地进程 本地部署 有 2026-08-23
quickstart-resources 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

其他
字段来自项目仓库与公开索引,中文说明由本站标注
提供方agntcy上游标注的维护方 agntcy
分类其他本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · go本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

11.4 KB
来自项目仓库与上游目录的原文,未做删改

Identity

Welcome to the Identity repository


AGNTCY Identity provides a secure and verifiable method to uniquely identify agents through open and decentralized techniques. Each agent is assigned a universally unique identifier, backed by verifiable credentials (VCs).
AGNTCY Identity enables to bring your own identity using conventions like IDs assigned by Identity Providers (e.g., Okta) or Agent Cards (e.g., Google’s A2A), or be assigned an ID following standards (e.g., W3C DIDs).
This component ensures that every agent in the AGNTCY ecosystem has a verifiable, universally unique identity, enabling secure authentication, trusted communication, and interoperability across diverse multi-agent systems, regardless of the identity assignment method.

  • The ID is linked to a ResolverMetadata object for secure and automated verification.
  • The ID can be linked to one or more Agent Badges. Why? Multiple badges can provide nuanced, task-specific access to different systems without over-privileging the agent. Agent Badges contain Verifiable Credentials (VCs), which include:
  • The Agent's ID
  • Schema definition (e.g., OASF)
  • Metadata for authentication and other security needs.

> [!NOTE]
> This same structure applies to MCP Servers and MASs, ensuring consistency across all identity-bearing entities in the IoA.

📚 Table of Contents

  • 🚀 Architecting Agentic Trust
  • 🌟 Features & Main Components
  • ⚡️ Get Started in 5 Minutes
  • 📜 See the core commands of the CLI
  • 🧪 Run the Demo

You can also:

  • 📖 See the full CLI and Node docs
  • 📦 Check-out the Sample Agents and MCP servers
  • 📘 Explore our full Documentation to understand our platform's capabilities
  • 📝 Dive into our API Specs for detailed API documentation

🚀 Architecting Agentic Trust

  • Core Principle: Trust is foundational for the Internet of Agents.
  • Identity as the Root: AGNTCY Identity ensures Agents and Tools (MCP Servers) are verifiably authentic.
  • Flexible & Interoperable: BYOID (Bring Your Own ID), integrates with existing Identity Providers (IdPs).

Secure and reliable communication between software agents is a cornerstone of the Internet of Agents (IoA) vision.
Without proper identity management, malicious or unverified agents can infiltrate Multi-Agent Systems (MASs), leading to misinformation, fraud, or security breaches.
To mitigate these risks, the AGNTCY provides a standardized and consistent framework for authenticating agents and validating associated metadata.
This applies equally to:

  • Agents
  • Model Context Protocol (MCP) Servers
  • MASs (Multi-Agent Systems)

> [!TIP]
> This repository includes an AI Agent and MCP Server to showcase the AGNTCY Identity components in action!

🌟 Features & Main Components

Features

  • Identity creation: Generate unique, verifiable identities for agents and MCP servers.
  • Existing identity onboarding: Integrate identities from external IdPs.
  • Badges creation & verification: Authenticate agents and MCP servers and validate metadata.

Main Components

  • Issuer CLI: Manage identities, vaults and credentials via command-line interface.
  • Node Backend: Backend server for identity management and metadata.

⚡️ Get Started in 5 Minutes

This short guide allows you to setup the Identity Issuer CLI as well as the Identity Node Backend.
The Issuer CLI allows to generate, register, search for, and verify badges for Agents and MCP Servers. The CLI includes a library enabling storage and retrieval of the keys required to sign the badges, both on local storage or using a 3rd party wallet or vault.
The Node Backend comprises the APIs and the backend core. It stores, maintains, and binds org:sub-org IDs, PubKeys, Subject IDs and metadata, including badges, ResolverMetadata and Verifiable Credentials (VCs).

Prerequisites

To run these steps successfully, you need to have the following installed:

  • Docker Desktop, or have both: Docker Engine v27 or higher and Docker Compose v2.35 or higher

Step 1: Install the Issuer CLI

Use the following command to install the Issuer CLI:

using curl:```bash
sh -c "$(curl -sSL https://raw.githubusercontent.com/agntcy/identity/refs/heads/main/deployments/scripts/identity/install_issuer.sh)"


or using `wget`:```bash
sh -c "$(wget -qO- https://raw.githubusercontent.com/agntcy/identity/refs/heads/main/deployments/scripts/identity/install_issuer.sh)"

> [!NOTE]
> You can also download the Issuer CLI binary corresponding to your platform from the latest releases.
>
> On some platforms you might need to add execution permissions and/or approve the binary in System Security Settings.
>
> For easier use, consider moving the binary to your $PATH or to the /usr/local/bin folder.

If you have Golang set up locally, you could also use the go install command:```bash
go install github.com/agntcy/identity/cmd/issuer@latest && \
ln -s $(go env GOPATH)/bin/issuer $(go env GOPATH)/bin/identity


### Step 2: Start the Node Backend with Docker

1. Clone the repository and navigate to the `identity` directory:```bash
   git clone https://github.com/agntcy/identity.git && cd identity
   ```

2. Start the Node Backend with Docker:```bash
   ./deployments/scripts/identity/launch_node.sh
   ```

   Or use `make` if available locally:```bash
   make start_node
   ```

> [!NOTE]
> You can also install the `Node Backend` using our helm chart, for which instructions are available in the chart's directory.

### Step 3: Verify the Installation

You can verify the installation by running the command below to see the different commands available:```bash
identity -h

📜 Core commands to use the CLI

Here are the core commands you can use with the CLI

  • vault: Manage cryptographic vaults and keys
  • issuer: Register and manage issuer configurations
  • metadata: Generate and manage metadata for identities
  • badge: Issue and publish badges for identities
  • verify: Verify identity badges
  • config: Display the current configuration context

🧪 Run the demo

This demo scenario will allow you to see how to use the AGNTCY Identity components can be used in a real environment.
You will be able to perform the following:

  • Register as an Issuer
  • Generate metadata for an MCP Server
  • Issue and publish a badge for the MCP Server
  • Verify the published badge

Prerequisites

First, follow the steps in the Get Started in 5 minutes section above to install the Issuer CLI and run the Node Backend, and generate a local vault and keys.

To run this demo setup locally, you need to have the following installed:

  • Docker Desktop, or have both: Docker Engine v27 or higher and Docker Compose v2.35 or higher
  • Ollama CLI
  • Okta CLI

Step 1: Run the Samples with Ollama and Docker

The agents in the samples rely on a local instance of the Llama 3.2 LLM to power the agent's capabilities.
With Ollama installed, you can download and run the model (which is approximately 2GB, so ensure you have enough disk space) using the following command:

  1. Run the Llama 3.2 model:bash ollama run llama3.2

  2. From the root of the repository, navigate to the samples directory and run the following command to deploy the Currency Exchange A2A Agent leveraging the Currency Exchange MCP Server:bash cd samples && docker compose up -d

  3. [Optional] Test the samples using the provided test clients.

Step 2: Use the CLI to create a local Vault and generate keys

  1. Create a local vault to store generated cryptographic keys:bash identity vault connect file -f ~/.identity/vault.json -v "My Vault"

  2. Generate a new key pair and store it in the vault:bash identity vault key generate

Step 3: Register as an Issuer

For this demo we will use Okta as an IdP to create an application for the Issuer.
To quickly create a trial account and application, we have provided a script to automate the process using the Okta CLI.

> [!IMPORTANT]
> If you already have an Okta account, you can use the okta login command to log in to your existing organization.
>
> If registering a new Okta developer account fails, proceed with manual trial signup and then use the okta login command,
> as instructed by the Okta CLI.

  1. Run the following command from the root repository to create a new Okta application:bash . ./demo/scripts/create_okta_app

  2. In the interactive prompt, choose the following options:

> 4: Service (Machine-to-Machine), > 5: Other

  1. Register the Issuer using the Issuer CLI and the environment variables from the previous step:bash identity issuer register -o "My Organization" \ -c "$OKTA_OAUTH2_CLIENT_ID" -s "$OKTA_OAUTH2_CLIENT_SECRET" -u "$OKTA_OAUTH2_ISSUER"

> [!NOTE]
> You can now access the Issuer's Well-Known Public Key at http://localhost:4000/v1alpha1/issuer/{common_name}/.well-known/jwks.json,
> where {common_name} is the common name you provided during registration.

Step 4: Generate metadata for an MCP Server

Create a second application for the MCP Server metadata using Okta, similar to the previous step:

  1. Run the following command from the root repository to create a new Okta application:bash . ./demo/scripts/create_okta_app

  2. In the interactive prompt, choose the following options:

> 4: Service (Machine-to-Machine), > 5: Other

  1. Generate metadata for the MCP Server using the Issuer CLI and the environment variables from the previous step:bash identity metadata generate -c "$OKTA_OAUTH2_CLIENT_ID" \ -s "$OKTA_OAUTH2_CLIENT_SECRET" -u "$OKTA_OAUTH2_ISSUER"

> [!NOTE]
> When successful, this command will print the metadata ID, which you will need in the next step to view published badges that are linked to this metadata.

Step 5: Issue and Publish a Badge for the MCP Server

  1. Issue a badge for the MCP Server:bash identity badge issue mcp -u http://localhost:9090 -n "My MCP Server"

  2. Publish the badge:bash identity badge publish

> [!NOTE]
> You can now access the VCs as a Well-Known at http://localhost:4000/v1alpha1/vc/{metadata_id}/.well-known/vcs.json,
> where {metadata_id} is the metadata ID you generated in the previous step.

(Optional) Step 6: Verify a Published Badge

You can use the Issuer CLI to verify a published badge any published badge, not just those that you issued yourself.
This allows others to verify the Agent and MCP badges you publish.

  1. Download the badge that you created in the previous step, replacing {metadata_id} with the metadata ID from step 4:bash curl -o vcs.json http://localhost:4000/v1alpha1/vc/{metadata_id}/.well-known/vcs.json

  2. Verify the badges using the Issuer CLI:bash identity verify -f vcs.json

> [!NOTE]
> You can also use our Python SDK to verify the badge programmatically. See the Python SDK for more details.

Development

For more detailed development instructions please refer to the following sections:

  • Node Backend
  • Issuer CLI
  • Samples
  • Api Spec
  • Node Client SDK

Roadmap

See the open issues for a list
of proposed features (and known issues).

Contributing

Contributions are what make the open source community such an amazing place to
learn, inspire, and create. Any contributions you make are greatly
appreciated
. For detailed contributing guidelines, please see
CONTRIBUTING.md.

Copyright Notice

Copyright Notice and License

Distributed under Apache 2.0 License. See LICENSE for more information.
Copyright AGNTCY Contributors.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Identity 怎么安装?

在客户端按下面的安装命令接入:go install github.com/agntcy/identity/cmd/issuer@latest && \\。装完在客户端配置里引用同一个包或端点。

Identity 怎么在 Cursor、Codex、Zed 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Identity 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Identity 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Identity 支持哪些客户端?

资料标注支持 Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Identity 能提供哪些能力?

资料显示能力标签包括 identity。具体工具清单以官方文档为准。

Identity 需要什么运行环境?

运行时为 go。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。