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

Mainline

REMOTE · MAINLINE.DEV · SCANNED AUG 3

Gives your AI agent your story map and given/when/then acceptance criteria. Read-only.

Available components

remote · mainline.dev 25
+9 this week 25 Trust /100
Trust breakdown (6 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 →

Endpoint Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mainline.dev

# add to Claude Code
claude mcp add --transport http dev-mainline-mcp https://mainline.dev/mcp/%7Bteam_id%7D
# ~/.codex/config.toml
[mcp_servers.dev-mainline-mcp]
url = "https://mainline.dev/mcp/%7Bteam_id%7D"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-mainline-mcp": {
      "type": "remote",
      "url": "https://mainline.dev/mcp/%7Bteam_id%7D",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-mainline-mcp --url https://mainline.dev/mcp/%7Bteam_id%7D --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-mainline-mcp:
    url: "https://mainline.dev/mcp/%7Bteam_id%7D"
// mcp.json
{
  "mcpServers": {
    "dev-mainline-mcp": {
      "type": "http",
      "url": "https://mainline.dev/mcp/%7Bteam_id%7D"
    }
  }
}

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.

  • 31 Jul 26 +9
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 16

    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 3 Aug 2026 · Probed https://mainline.dev/mcp/{team_id}

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mainline.dev CN=YE1,O=Let's Encrypt,C=US 22 Jun 2026 20 Sept 2026 ECDSA 256 ECDSA-SHA384 5252c727233233f044e2def0b99fc556878
SANs: *.mainline.dev, mainline.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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
DNSSEC insecure

Validation of mainline.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
mainline.dev. 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=63072000; includeSubDomains
content-security-policy default-src 'none'; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net https://fonts.googleapis.com https://cdn.paddle.com; font-src 'self' https://fonts.gstatic.com; form-action 'self' https://accounts.google.com https://github.com https://gitlab.com; script-src 'self' 'nonce-b230b4a37c2ec20e026c63e38c843a2d' https://cdn.paddle.com https://public.profitwell.com https://analytics.mainline.dev; connect-src 'self' https://*.paddle.com https://*.profitwell.com https://analytics.mainline.dev; img-src 'self' data:; frame-src https://*.paddle.com; base-uri 'none'; frame-ancestors 'none';
x-content-type-options nosniff
x-frame-options deny
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mainline.dev/mcp/{team_id} HTTP error 400
http (plaintext) http://mainline.dev/mcp/%7Bteam_id%7D HTTPS enforced 301 https://mainline.dev/mcp/%7Bteam_id%7D
MCP tools

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.

No tool schema has been captured from this endpoint yet.