# AgentTwin Documentation (remote · agenttwin.si)

Search AgentTwin agent testing guides, Node CLI commands and supported synthetic service contracts.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `agenttwin.si`: 70/100 (this document), [markdown](https://verifymcp.io/servers/sashank-singh-agenttwin-docs/mcp-docs.md), [page](https://verifymcp.io/servers/sashank-singh-agenttwin-docs/mcp-docs)

## Channel facts

- Endpoint: `https://agenttwin.si/mcp/docs`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 33/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 372 tokens (~10/item across 37 items; 2 tools + 35 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the AgentTwin Documentation MCP server?

AgentTwin Documentation is a hosted endpoint at https://agenttwin.si/mcp/docs, 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.

### Claude

```bash
claude mcp add --transport http sashank-singh-agenttwin-docs 'https://agenttwin.si/mcp/docs'
```

### Cursor

```json
{
  "mcpServers": {
    "sashank-singh-agenttwin-docs": {
      "url": "https://agenttwin.si/mcp/docs"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sashank-singh-agenttwin-docs": {
      "type": "http",
      "url": "https://agenttwin.si/mcp/docs"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sashank-singh-agenttwin-docs]
url = "https://agenttwin.si/mcp/docs"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sashank-singh-agenttwin-docs": {
      "type": "remote",
      "url": "https://agenttwin.si/mcp/docs",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sashank-singh-agenttwin-docs --url 'https://agenttwin.si/mcp/docs' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sashank-singh-agenttwin-docs:
    url: "https://agenttwin.si/mcp/docs"
```

### Netclaw

```json
{
  "McpServers": {
    "sashank-singh-agenttwin-docs": {
      "Transport": "http",
      "Url": "https://agenttwin.si/mcp/docs"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sashank-singh-agenttwin-docs -t streamable-http -u 'https://agenttwin.si/mcp/docs'
```

### Other

```json
{
  "mcpServers": {
    "sashank-singh-agenttwin-docs": {
      "type": "http",
      "url": "https://agenttwin.si/mcp/docs"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 70, +1)

- [functional regression] Resource “AgentTwin pricing” was removed
- [functional] New resource “AgentTwin enterprise pricing”

### 2026-11-02 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 68, 0)

- [functional] New resource “Pull request checks”

### 2026-10-31 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 67, 0)

- [functional regression] Resource “AgentTwin pricing and access” was removed
- [functional] New resource “AgentTwin pricing”

### 2026-10-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 66, 0)

- [functional regression] Resource “AgentTwin agent testing for Node.js and AI agents” was removed
- [functional regression] Resource “Contact AgentTwin | Node.js workflow testing support” was removed
- [functional regression] Resource “Discover, test and retest” was removed
- [functional regression] Resource “Example: timeout after a write” was removed
- [functional regression] Resource “Explore the browser demo” was removed
- [functional regression] Resource “Infrastructure and evidence” was removed
- [functional regression] Resource “Safety and isolation” was removed
- [functional regression] Resource “Welcome to AgentTwin” was removed
- [functional regression] Resource “Your first verified fix” was removed
- [functional] New resource “AgentTwin | Digital twins for testing AI agents”
- [functional] New resource “Contact AgentTwin | AI agent testing and enterprise access”
- [functional] New resource “Documentation for coding agents”
- [functional] New resource “Explore the browser preview”
- [functional] New resource “How a workflow becomes a test”
- [functional] New resource “Runtime requirements and verification”
- [functional] New resource “Safety and execution limits”
- [functional] New resource “Set up your project”
- [functional] New resource “Start with your project”
- [functional] New resource “Try the sample test”
- [functional] New resource “Understand a timeout after a write”

### 2026-10-26 (score 66, +1)

- [functional regression] Resource “AgentTwin agent testing — test workflows before production” was removed
- [functional regression] Resource “Contact AgentTwin” was removed
- [functional] New resource “AgentTwin MCP servers and connection guide”
- [functional] New resource “AgentTwin REST API reference”
- [functional] New resource “AgentTwin agent testing for Node.js and AI agents”
- [functional] New resource “Contact AgentTwin | Node.js workflow testing support”

## MCP tools (2)

### `search_docs` (~33 tokens)

Search public AgentTwin guides, CLI commands and operation contracts. Does not access customer data.

Input parameters:

- `query` (string, required)

### `read_doc` (~34 tokens)

Read a published AgentTwin Markdown guide by its exact path returned by search_docs or resources/list.

Input parameters:

- `path` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sashank-singh-agenttwin-docs/mcp-docs#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 69
- 2026-11-02: 69
- 2026-11-01: 68
- 2026-10-31: 68
- 2026-10-30: 67
- 2026-10-29: 67
- 2026-10-28: 67
- 2026-10-27: 66
- 2026-10-26: 66
- 2026-10-25: 65
- 2026-10-24: 65

## Common questions

### What is the AgentTwin Documentation MCP server?

AgentTwin Documentation is an MCP server listed in the public MCP registry as io.github.Sashank-Singh/agenttwin-docs. Search AgentTwin agent testing guides, Node CLI commands and supported synthetic service contracts. This page covers its hosted endpoint (https://agenttwin.si/mcp/docs).

### Is the AgentTwin Documentation MCP server safe to use?

AgentTwin Documentation scores 70 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 AgentTwin Documentation MCP server expose?

AgentTwin Documentation exposes 2 tools: search_docs, read_doc. Their descriptions and schemas cost roughly 67 tokens of context every time the server is loaded.

### Does the AgentTwin Documentation MCP server require authentication?

No. We connected to AgentTwin Documentation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AgentTwin Documentation MCP server still maintained?

AgentTwin Documentation 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.

### What did VerifyMCP test on the AgentTwin Documentation MCP server?

VerifyMCP ran 13 checks on AgentTwin Documentation, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://agenttwin.si/mcp/docs
- Website: https://agenttwin.si/developers/
- Changelog RSS feed: https://verifymcp.io/servers/sashank-singh-agenttwin-docs/mcp-docs.xml
- Changelog JSON feed: https://verifymcp.io/servers/sashank-singh-agenttwin-docs/mcp-docs/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/sashank-singh-agenttwin-docs/mcp-docs.json
- HTML version of this page: https://verifymcp.io/servers/sashank-singh-agenttwin-docs/mcp-docs