KPN Persona Runtime
REMOTE · PERSONA-MCP-SERVER.ONRENDER.COM · SCANNED SEP 21
Verify a persona's DID-signed identity and query value-based judgment — advisory only, no actions.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 514 tokens (~128/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the KPN Persona Runtime MCP server?
KPN Persona Runtime is a hosted endpoint at https://persona-mcp-server.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · persona-mcp-server.onrender.com
claude mcp add --transport http space-mysoma-kpn 'https://persona-mcp-server.onrender.com/mcp'
{
"mcpServers": {
"space-mysoma-kpn": {
"url": "https://persona-mcp-server.onrender.com/mcp"
}
}
} {
"servers": {
"space-mysoma-kpn": {
"type": "http",
"url": "https://persona-mcp-server.onrender.com/mcp"
}
}
} [mcp_servers.space-mysoma-kpn] url = "https://persona-mcp-server.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"space-mysoma-kpn": {
"type": "remote",
"url": "https://persona-mcp-server.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add space-mysoma-kpn --url 'https://persona-mcp-server.onrender.com/mcp' --transport streamable-http
mcp_servers:
space-mysoma-kpn:
url: "https://persona-mcp-server.onrender.com/mcp" {
"McpServers": {
"space-mysoma-kpn": {
"Transport": "http",
"Url": "https://persona-mcp-server.onrender.com/mcp"
}
}
} assistant mcp add space-mysoma-kpn -t streamable-http -u 'https://persona-mcp-server.onrender.com/mcp'
{
"mcpServers": {
"space-mysoma-kpn": {
"type": "http",
"url": "https://persona-mcp-server.onrender.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://persona-mcp-server.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 756bcb97dcf1455f0ebf70e5dbe07256 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of persona-mcp-server.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://persona-mcp-server.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://persona-mcp-server.onrender.com/mcp | HTTPS enforced | 301 | https://persona-mcp-server.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_persona_card 페르소나 명함 조회 ~86
DID로 페르소나 명함(공개 범위)을 조회합니다. 이름·소속·전문 분야·공개 의도와 발급자 서명이 포함됩니다. 이 도구는 정보 조회 전용이며 어떤 행동도 수행하지 않습니다.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | 조회할 페르소나 DID (예: did:soma:...) |
No output schema declared.
No examples provided.
query_persona_decision 페르소나 판단 자문 ~138
"이 사람이라면 어떻게 판단할까?"를 페르소나에게 자문합니다. 응답은 공개 범위의 가치 기준에 따른 권고(자문)일 뿐이며, 이 도구는 결제·전송·기기제어 등 어떤 실제 행동도 절대 수행하지 않습니다(executed:false 고정). 사적·민감 영역 질문은 보류로 응답됩니다.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | 자문 대상 페르소나 DID |
| question | string | yes | 자문할 질문 (예: '이 제휴 제안을 수락할까요?') |
No output schema declared.
No examples provided.
sync_persona_card 페르소나 명함 동기화 ~87
해당 DID의 런타임을 최신 상태로 동기화합니다. 명함 수신자가 항상 발급 시점이 아닌 현재의 페르소나와 대화하도록 보장합니다. 페르소나 데이터 갱신 외의 어떤 외부 행동도 수행하지 않습니다.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | 동기화할 페르소나 DID |
No output schema declared.
No examples provided.
verify_persona_did 페르소나 DID 서명 검증 ~130
제시된 페르소나 명함이 진본인지(발급자 서명이 유효한지) 판정합니다. 명함 내용이 한 글자라도 변조되면 SIGNATURE_MISMATCH를 반환합니다. 에이전트 사칭 여부를 확인할 때 사용하세요. 검증 전용이며 행동을 수행하지 않습니다.
| Name | Type | Req | Description |
|---|---|---|---|
| cardPayload | object | – | 검증 대상 명함 전체 JSON(서명 포함). 생략 시 레지스트리 보관본을 자체 검증 |
| did | string | yes | 검증할 DID |
No output schema declared.
No examples provided.
What is the KPN Persona Runtime MCP server?
KPN Persona Runtime is an MCP server listed in the public MCP registry as space.mysoma/kpn. Verify a persona's DID-signed identity and query value-based judgment, advisory only, no actions. This page covers its hosted endpoint (https://persona-mcp-server.onrender.com/mcp).
Is the KPN Persona Runtime MCP server safe to use?
KPN Persona Runtime scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the KPN Persona Runtime MCP server expose?
KPN Persona Runtime exposes 4 tools: get_persona_card, verify_persona_did, sync_persona_card, query_persona_decision. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.
Does the KPN Persona Runtime MCP server require authentication?
No. We connected to KPN Persona Runtime without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the KPN Persona Runtime MCP server still maintained?
KPN Persona Runtime is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.