Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentTwin Documentation

REMOTE · AGENTTWIN.SI

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

Available components

−26 this week 42 Trust /100

Last scanned (18 hours ago)

Scores higher than 41% of remote servers

Unreachable for 4 days in a row. Last reached 17 Nov 2026.

Category Testing and QA

Degraded

One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

Trust breakdown (7 categories)

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 Security14
Transport & Reachability0
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.

What we tested

Checks we ran (3)

  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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 →

Changelog

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.

  • 21 Nov 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 20 Nov 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 18 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: 0.37 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 0 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 17 Nov 26 +1

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

  • 15 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.

  • 13 Nov 26 +1
    • Resource “Contact AgentTwin | AI agent testing and enterprise access” was removed ▼ functional
    • New resource “Contact AgentTwin about AI agent testing” functional
  • 10 Nov 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.

  • 8 Nov 26 +1
    • Schema quality: 10 → 9 ▲ functional
    • New resource “Data Processing Agreement” functional
    • New resource “Security at AgentTwin” functional
    • New resource “Subprocessors” functional
    • New resource “Terms of Service” functional
Diagnostics

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 Nov 2026 · Probed https://agenttwin.si/mcp/docs

TLS unreached
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 Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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 Unreachable
http (plaintext) http://agenttwin.si/mcp/docs HTTPS enforced
MCP tools · 2 exposed · ~67 tokens

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 →

Tool Tokens
read_doc ~34

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

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

search_docs ~33

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

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

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.

remote · agenttwin.si

# add to Claude Code
claude mcp add --transport http agenttwin-agenttwin-docs 'https://agenttwin.si/mcp/docs'
Common questions

What is the AgentTwin Documentation MCP server?

AgentTwin Documentation is an MCP server listed in the public MCP registry as io.github.AgentTwin/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 42 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?

Its publisher declares no required credentials for AgentTwin Documentation. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the AgentTwin Documentation MCP server still maintained?

AgentTwin Documentation is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 17 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 3 checks on AgentTwin Documentation, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about AgentTwin Documentation: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.