KPN Persona Runtime
Server Details
Verify a persona's DID-signed identity and query value-based judgment — advisory only, no actions.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 4 of 4 tools scored.
Each tool has a clearly distinct purpose: retrieving a persona card, querying a decision, synchronizing runtime data, and verifying authenticity. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (get_persona_card, query_persona_decision, sync_persona_card, verify_persona_did), providing predictability.
With 4 tools, the set is well-scoped for the domain of persona card interaction. Each tool earns its place, covering essential operations without being excessive or sparse.
The tool surface covers the core workflows for a persona runtime: lookup, decision consultation, synchronization, and verification. There are no missing operations for the stated purpose.
Available Tools
4 toolsget_persona_card페르소나 명함 조회Read-onlyInspect
DID로 페르소나 명함(공개 범위)을 조회합니다. 이름·소속·전문 분야·공개 의도와 발급자 서명이 포함됩니다. 이 도구는 정보 조회 전용이며 어떤 행동도 수행하지 않습니다.
| Name | Required | Description | Default |
|---|---|---|---|
| did | Yes | 조회할 페르소나 DID (예: did:soma:...) |
query_persona_decision페르소나 판단 자문Read-onlyInspect
"이 사람이라면 어떻게 판단할까?"를 페르소나에게 자문합니다. 응답은 공개 범위의 가치 기준에 따른 권고(자문)일 뿐이며, 이 도구는 결제·전송·기기제어 등 어떤 실제 행동도 절대 수행하지 않습니다(executed:false 고정). 사적·민감 영역 질문은 보류로 응답됩니다.
| Name | Required | Description | Default |
|---|---|---|---|
| did | Yes | 자문 대상 페르소나 DID | |
| question | Yes | 자문할 질문 (예: '이 제휴 제안을 수락할까요?') |
sync_persona_card페르소나 명함 동기화Inspect
해당 DID의 런타임을 최신 상태로 동기화합니다. 명함 수신자가 항상 발급 시점이 아닌 현재의 페르소나와 대화하도록 보장합니다. 페르소나 데이터 갱신 외의 어떤 외부 행동도 수행하지 않습니다.
| Name | Required | Description | Default |
|---|---|---|---|
| did | Yes | 동기화할 페르소나 DID |
verify_persona_did페르소나 DID 서명 검증Read-onlyInspect
제시된 페르소나 명함이 진본인지(발급자 서명이 유효한지) 판정합니다. 명함 내용이 한 글자라도 변조되면 SIGNATURE_MISMATCH를 반환합니다. 에이전트 사칭 여부를 확인할 때 사용하세요. 검증 전용이며 행동을 수행하지 않습니다.
| Name | Required | Description | Default |
|---|---|---|---|
| did | Yes | 검증할 DID | |
| cardPayload | No | 검증 대상 명함 전체 JSON(서명 포함). 생략 시 레지스트리 보관본을 자체 검증 |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!