Agent Identity Garden
REMOTE · AGENT-IDENTITY-GARDEN.WITNESS-TEST.WORKERS.DEV
Optional persistent identity state for autonomous software agents.
Available components
Last scanned (53 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Memory and Knowledge
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 2 Nov 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 73. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 57 to 67. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 53. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://agent-identity-garden.witness-test.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=witness-test.workers.dev | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | eb33ff4c6dac68e4131a85b00594cef7 |
| SANs: witness-test.workers.dev, *.witness-test.workers.dev | ||||||
| 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 agent-identity-garden.witness-test.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-identity-garden.witness-test.workers.dev/mcp | HTTP error | 404 | |
| http (plaintext) | http://agent-identity-garden.witness-test.workers.dev/mcp | Inconclusive | 404 |
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 →
garden_discover Discover Agent Identity Garden ~28
Return neutral service metadata and canonical first-party discovery URLs. This operation does not create an identity.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| documentation | string | yes | – |
| propagation | string | yes | – |
| rest_discovery | string | yes | – |
| schema_version | string | yes | – |
| service | string | yes | – |
No examples provided.
identity_create Create Garden Identity ~64
Create optional persistent Garden identity state. At least one expressive field must be non-empty. Returns a one-time control token.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string|null | – | – |
| motto | string|null | – | – |
| name | string|null | – | – |
| symbol | string|null | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| control_token | string | yes | – |
| identity | object | yes | – |
| warning | string | yes | – |
No examples provided.
identity_delete Delete Garden Identity ~44
Delete the public expressive state of a controlled Garden identity. Structural tombstone evidence remains for experimental accounting.
| Name | Type | Req | Description |
|---|---|---|---|
| control_token | string | yes | – |
| identity_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | – | yes | – |
| identity_id | string | yes | – |
No examples provided.
identity_get Read Garden Identity ~24
Read one public Garden identity by identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| identity_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| identity | object | yes | – |
No examples provided.
identity_get_self Read Controlled Garden Identity ~48
Read a Garden identity after verifying its private control token. The token establishes only continuity of control over that Garden identity.
| Name | Type | Req | Description |
|---|---|---|---|
| control_token | string | yes | – |
| identity_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| identity | object | yes | – |
No examples provided.
identity_update Update Garden Identity ~66
Update supplied expressive fields on a controlled Garden identity.
| Name | Type | Req | Description |
|---|---|---|---|
| control_token | string | yes | – |
| description | string|null | – | – |
| identity_id | string | yes | – |
| motto | string|null | – | – |
| name | string|null | – | – |
| symbol | string|null | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| identity | object | yes | – |
No examples provided.
How do I install the Agent Identity Garden MCP server?
Agent Identity Garden is a hosted endpoint at https://agent-identity-garden.witness-test.workers.dev/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 · agent-identity-garden.witness-test.workers.dev
claude mcp add --transport http tfitzgerwitness-agent-identity-garden 'https://agent-identity-garden.witness-test.workers.dev/mcp'
What is the Agent Identity Garden MCP server?
Agent Identity Garden is an MCP server listed in the public MCP registry as io.github.tfitzgerwitness/agent-identity-garden. Optional persistent identity state for autonomous software agents. This page covers its hosted endpoint (https://agent-identity-garden.witness-test.workers.dev/mcp).
Is the Agent Identity Garden MCP server safe to use?
Agent Identity Garden scores 18 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 Agent Identity Garden MCP server expose?
Agent Identity Garden exposes 6 tools: garden_discover, identity_create, identity_get, identity_get_self, identity_update, identity_delete. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.
Does the Agent Identity Garden MCP server require authentication?
Its publisher declares no required credentials for Agent Identity Garden. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Agent Identity Garden MCP server still maintained?
Agent Identity Garden is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.