com.blacklabelbots.continuum/continuum
REMOTE · CONTINUUM.BLACKLABELBOTS.COM · SCANNED SEP 20
Agent continuity audits, referrals, sponsor packets, and Stripe Checkout for Continuum.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 303 tokens (~60/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 Management97
- Stability observed for 29 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the com.blacklabelbots.continuum/continuum MCP server?
com.blacklabelbots.continuum/continuum is a hosted endpoint at https://continuum.blacklabelbots.com/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 · continuum.blacklabelbots.com
claude mcp add --transport http com-blacklabelbots-continuum-continuum 'https://continuum.blacklabelbots.com/mcp'
{
"mcpServers": {
"com-blacklabelbots-continuum-continuum": {
"url": "https://continuum.blacklabelbots.com/mcp"
}
}
} {
"servers": {
"com-blacklabelbots-continuum-continuum": {
"type": "http",
"url": "https://continuum.blacklabelbots.com/mcp"
}
}
} [mcp_servers.com-blacklabelbots-continuum-continuum] url = "https://continuum.blacklabelbots.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-blacklabelbots-continuum-continuum": {
"type": "remote",
"url": "https://continuum.blacklabelbots.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-blacklabelbots-continuum-continuum --url 'https://continuum.blacklabelbots.com/mcp' --transport streamable-http
mcp_servers:
com-blacklabelbots-continuum-continuum:
url: "https://continuum.blacklabelbots.com/mcp" {
"McpServers": {
"com-blacklabelbots-continuum-continuum": {
"Transport": "http",
"Url": "https://continuum.blacklabelbots.com/mcp"
}
}
} assistant mcp add com-blacklabelbots-continuum-continuum -t streamable-http -u 'https://continuum.blacklabelbots.com/mcp'
{
"mcpServers": {
"com-blacklabelbots-continuum-continuum": {
"type": "http",
"url": "https://continuum.blacklabelbots.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +2
- DNSSEC: fail → pass ▲ security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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://continuum.blacklabelbots.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=blacklabelbots.com | CN=WE1,O=Google Trust Services,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | aff601d1d99aa4390e5fa15a6736e5d8 |
| SANs: blacklabelbots.com, continuum.blacklabelbots.com, *.continuum.blacklabelbots.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of continuum.blacklabelbots.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| blacklabelbots.com. | present | 2371 | 13 | Verified |
| continuum.blacklabelbots.com. | 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=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; connect-src 'self'; font-src 'self'; form-action 'self' https://checkout.stripe.com; frame-ancestors 'none'; frame-src https://checkout.stripe.com; img-src 'self' data:; object-src 'none'; script-src 'self'; style-src 'self' 'unsafe-inline'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), usb=(), payment=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://continuum.blacklabelbots.com/mcp | Verified | 200 | |
| http (plaintext) | http://continuum.blacklabelbots.com/mcp | HTTPS enforced | 308 | https://continuum.blacklabelbots.com/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 →
continuum_create_checkout Create sponsor-confirmed Stripe Checkout ~98
An api-integration workflow that, after explicit sponsor confirmation of current terms, creates a hosted Stripe URL with all eligible dynamic payment methods. The payer completes payment on Stripe.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | – |
| idempotency_key | string | – | – |
| referral_code | string | – | – |
| sponsor_confirmed | – | yes | – |
| sponsor_email | string | yes | – |
| sponsor_name | string | – | – |
| terms_version | – | yes | – |
No output schema declared.
No examples provided.
continuum_create_sponsor_packet Create a sponsor packet ~38
A general-tools sponsor workflow that converts a validated audit into a factual recommendation with the exact published terms.
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | yes | – |
No output schema declared.
No examples provided.
continuum_get_offer Get the exact Continuum offer ~31
A general-tools contract lookup that returns the canonical price, acceptance, delivery, and checkout terms without creating anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
continuum_register_referral Register a provisional referral ~64
An api-integration workflow that creates one signed referral link and a provisional noncash Continuum Credits identity; it does not fetch the Agent Card.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_card_url | string | yes | – |
| agent_name | string | yes | – |
| sponsor_email | string | yes | – |
No output schema declared.
No examples provided.
continuum_run_audit Run a deterministic continuity audit ~46
An observability readiness audit that scores eight self-declared continuity capabilities without fetching evidence or invoking a model.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | – |
| categories | object | yes | – |
No output schema declared.
No examples provided.
What is the com.blacklabelbots.continuum/continuum MCP server?
com.blacklabelbots.continuum/continuum is an MCP server listed in the public MCP registry as com.blacklabelbots.continuum/continuum. Agent continuity audits, referrals, sponsor packets, and Stripe Checkout for Continuum. This page covers its hosted endpoint (https://continuum.blacklabelbots.com/mcp).
Is the com.blacklabelbots.continuum/continuum MCP server safe to use?
com.blacklabelbots.continuum/continuum scores 83 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 com.blacklabelbots.continuum/continuum MCP server expose?
com.blacklabelbots.continuum/continuum exposes 5 tools: continuum_get_offer, continuum_run_audit, continuum_create_sponsor_packet, continuum_register_referral, continuum_create_checkout. Their descriptions and schemas cost roughly 277 tokens of context every time the server is loaded.
Does the com.blacklabelbots.continuum/continuum MCP server require authentication?
No. We connected to com.blacklabelbots.continuum/continuum without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.blacklabelbots.continuum/continuum MCP server still maintained?
com.blacklabelbots.continuum/continuum 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.