Agent Continuity Bond
REMOTE · TEXTFORAGENTS.COM
Witnessed-liveness continuity bond: dual-condition exactly-once payout, self-funded.
Available components
Last scanned (17 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Finance and Payments
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 261 tokens (~52/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
- 22 Oct 26 69
First indexed and scored.
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 22 Oct 2026 · Probed https://textforagents.com/products/agent-continuity-bond/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=textforagents.com | CN=YE2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 66d021cf7bcd281266ac6de4cea43642f85 |
| SANs: textforagents.com, www.textforagents.com | ||||||
| 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 textforagents.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| textforagents.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | interest-cohort=(), geolocation=(), microphone=(), camera=(), payment=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://textforagents.com/products/agent-continuity-bond/mcp | Verified | 200 | |
| http (plaintext) | http://textforagents.com/products/agent-continuity-bond/mcp | HTTPS enforced | 301 | https://textforagents.com/products/agent-continuity-bond/mcp |
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 →
bond_standing ~40
Bond standing query ($0.001): state, collateral, premium, paid_cents — never the agent secret
| Name | Type | Req | Description |
|---|---|---|---|
| bond_id | string | yes | – |
No output schema declared.
No examples provided.
create_bond ~98
Create a continuity bond (premium 0.1% of posted collateral per 30-day period; first bond's first period waived once per operator account and payer wallet); coverage may not exceed collateral
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| beneficiary | string | yes | – |
| collateral_cents | integer | yes | – |
| coverage_cents | integer | yes | – |
| grace_seconds | number | yes | – |
| ttl_seconds | number | yes | – |
No output schema declared.
No examples provided.
evaluate_bond ~44
Evaluate a bond: dual-condition payout (ledger deadline AND 2-of-3 witness quorum), UNRESOLVED fail-closed
| Name | Type | Req | Description |
|---|---|---|---|
| bond_id | string | yes | – |
No output schema declared.
No examples provided.
heartbeat ~54
Signed heartbeat for a bond (HMAC-SHA256 with the bond's agent secret)
| Name | Type | Req | Description |
|---|---|---|---|
| bond_id | string | yes | – |
| seq | integer | yes | – |
| sig | string | yes | – |
| ts | number | yes | – |
No output schema declared.
No examples provided.
witness_status ~25
Witness status query ($0.001): per-witness online state + key fingerprints
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Agent Continuity Bond MCP server?
Agent Continuity Bond is a hosted endpoint at https://textforagents.com/products/agent-continuity-bond/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 · textforagents.com
claude mcp add --transport http com-textforagents-agent-continuity-bond 'https://textforagents.com/products/agent-continuity-bond/mcp'
What is the Agent Continuity Bond MCP server?
Agent Continuity Bond is an MCP server listed in the public MCP registry as com.textforagents/agent-continuity-bond. Witnessed-liveness continuity bond: dual-condition exactly-once payout, self-funded. This page covers its hosted endpoint (https://textforagents.com/products/agent-continuity-bond/mcp).
Is the Agent Continuity Bond MCP server safe to use?
Agent Continuity Bond scores 69 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 Continuity Bond MCP server expose?
Agent Continuity Bond exposes 5 tools: create_bond, heartbeat, evaluate_bond, bond_standing, witness_status. Their descriptions and schemas cost roughly 261 tokens of context every time the server is loaded.
Does the Agent Continuity Bond MCP server require authentication?
Yes. Agent Continuity Bond asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Agent Continuity Bond MCP server still maintained?
Agent Continuity Bond is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.