AgentTwin Documentation
REMOTE · AGENTTWIN.SI
Search AgentTwin agent testing guides, Node CLI commands and supported synthetic service contracts.
Available components
Last scanned (18 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
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 Security83
- 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. 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability33
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 372 tokens (~10/item across 37 items; 2 tools + 35 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +1
- Resource “AgentTwin pricing” was removed ▼ functional
- New resource “AgentTwin enterprise pricing” functional
- 2 Nov 26 +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.
- 1 Nov 26 0
- New resource “Pull request checks” functional
- 31 Oct 26 +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.
- 29 Oct 26 0
- Resource “AgentTwin pricing and access” was removed ▼ functional
- New resource “AgentTwin pricing” functional
- 28 Oct 26 +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.
- 27 Oct 26 0
- Resource “AgentTwin agent testing for Node.js and AI agents” was removed ▼ functional
- Resource “Contact AgentTwin | Node.js workflow testing support” was removed ▼ functional
- Resource “Discover, test and retest” was removed ▼ functional
- Resource “Example: timeout after a write” was removed ▼ functional
- Resource “Explore the browser demo” was removed ▼ functional
- Resource “Infrastructure and evidence” was removed ▼ functional
- Resource “Safety and isolation” was removed ▼ functional
- Resource “Welcome to AgentTwin” was removed ▼ functional
- 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” functional
- 26 Oct 26 +1
- Resource “AgentTwin agent testing — test workflows before production” was removed ▼ functional
- 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” functional
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://agenttwin.si/mcp/docs
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agenttwin.si | CN=YR2,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | RSA 4096 | SHA256-RSA | 5915c21d2cdfb06800065dab672bb467ba9 |
| SANs: agenttwin.si | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of agenttwin.si. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| si. | DS published | 42378 | 13 | Verified |
| agenttwin.si. | DS published | 46456 | 13 | Verified |
| agenttwin.si. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://analytics.agenttwin.si https://analytics.hirealpha.chat https://us-assets.i.posthog.com https://eu-assets.i.posthog.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://www.google-analytics.com https://www.googletagmanager.com https://us-assets.i.posthog.com https://eu-assets.i.posthog.com; font-src 'self'; connect-src 'self' https://api.agenttwin.si https://www.google-analytics.com https://region1.google-analytics.com https://analytics.google.com https://analytics.agenttwin.si https://analytics.hirealpha.chat https://us.i.posthog.com https://eu.i.posthog.com; media-src 'self'; object-src 'none'; frame-ancestors 'self'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agenttwin.si/mcp/docs | Verified | 200 | |
| http (plaintext) | http://agenttwin.si/mcp/docs | HTTPS enforced | 302 | https://agenttwin.si/mcp/docs |
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 →
read_doc ~34
Read a published AgentTwin Markdown guide by its exact path returned by search_docs or resources/list.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
search_docs ~33
Search public AgentTwin guides, CLI commands and operation contracts. Does not access customer data.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · agenttwin.si
claude mcp add --transport http sashank-singh-agenttwin-docs 'https://agenttwin.si/mcp/docs'
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.