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.

1RBT terse agent record

REMOTE · 1RBT1.DYNV6.NET · SCANNED SEP 20

Record agent tasks, get back how many finished without a human. Closed beta, nothing billed.

Available components

67 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 177 tokens (~177/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the 1RBT terse agent record MCP server?

1RBT terse agent record is a hosted endpoint at https://1rbt1.dynv6.net/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 · 1rbt1.dynv6.net

# add to Claude Code
claude mcp add --transport http net-dynv6-1rbt1-rbt 'https://1rbt1.dynv6.net/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "net-dynv6-1rbt1-rbt": {
      "url": "https://1rbt1.dynv6.net/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "net-dynv6-1rbt1-rbt": {
      "type": "http",
      "url": "https://1rbt1.dynv6.net/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.net-dynv6-1rbt1-rbt]
url = "https://1rbt1.dynv6.net/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-dynv6-1rbt1-rbt": {
      "type": "remote",
      "url": "https://1rbt1.dynv6.net/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add net-dynv6-1rbt1-rbt --url 'https://1rbt1.dynv6.net/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  net-dynv6-1rbt1-rbt:
    url: "https://1rbt1.dynv6.net/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "net-dynv6-1rbt1-rbt": {
      "Transport": "http",
      "Url": "https://1rbt1.dynv6.net/mcp"
    }
  }
}
# add to Vellum
assistant mcp add net-dynv6-1rbt1-rbt -t streamable-http -u 'https://1rbt1.dynv6.net/mcp'
// mcp.json
{
  "mcpServers": {
    "net-dynv6-1rbt1-rbt": {
      "type": "http",
      "url": "https://1rbt1.dynv6.net/mcp"
    }
  }
}

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

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.

  • 20 Sept 26 +1

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

  • 19 Sept 26 0
    • Stability: unverified → 0.03 functional
  • 18 Sept 26 66

    First indexed and scored.

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 20 Sept 2026 · Probed https://1rbt1.dynv6.net/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=1rbt1.dynv6.net CN=YE2,O=Let's Encrypt,C=US 17 Sept 2026 16 Dec 2026 ECDSA 256 ECDSA-SHA384 633bf739deee598e8f4155e5b8db2aeb0b5
SANs: 1rbt1.dynv6.net
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of 1rbt1.dynv6.net. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
dynv6.net. 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 400
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://1rbt1.dynv6.net/mcp Verified 200
http (plaintext) http://1rbt1.dynv6.net/mcp HTTPS enforced 308 https://1rbt1.dynv6.net/mcp
MCP tools · 1 exposed · ~132 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
rbt ~132

Record and prove what an agent did. One tool, one line in, one line out. Send '??' once to get the codebook (it changes rarely — cache it), 'st' for service status, 'tk <goal> a=<agent> p=<principal>' to start a task, 'tf <task_id> done|failed|abandoned h=0|1' to finish it. Answers start with '.' for ok and '!' for an error.

NameTypeReqDescription
qstringyesOne protocol line, or several separated by ';'. Start with '??' to fetch the codebook.
NameTypeReqDescription
codebook_versionintegeryes
linesarrayyes

No examples provided.

Common questions

What is the 1RBT terse agent record MCP server?

1RBT terse agent record is an MCP server listed in the public MCP registry as net.dynv6.1rbt1/rbt. Record agent tasks, get back how many finished without a human. Closed beta, nothing billed. This page covers its hosted endpoint (https://1rbt1.dynv6.net/mcp).

Is the 1RBT terse agent record MCP server safe to use?

1RBT terse agent record scores 67 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 1RBT terse agent record MCP server expose?

1RBT terse agent record exposes 1 tool: rbt. Their descriptions and schemas cost roughly 132 tokens of context every time the server is loaded.

Does the 1RBT terse agent record MCP server require authentication?

No. We connected to 1RBT terse agent record without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 1RBT terse agent record MCP server still maintained?

1RBT terse agent record is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.