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.

Kanbai — public project templates and SOPs

REMOTE · KANBAI.APP

Read-only access to Kanbai's public project templates and SOPs. Public, no authentication.

Available components

0 this week 86 Trust /100

Last scanned (20 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Project Management

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 Security80
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 160 tokens (~40/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 25 Oct 26 +3
    • Stability: fail → pass ▲ security
  • 12 Oct 26 0
    • Stability: pass → fail ▼ security
  • 10 Oct 26 0
    • Stability: 0.97 → pass security
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://kanbai.app/api/mcp/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kanbai.app CN=YR2,O=Let's Encrypt,C=US 11 Oct 2026 9 Jan 2027 RSA 2048 SHA256-RSA 5d7edec61aa6bdbafed03338a64854bbe04
SANs: kanbai.app
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of kanbai.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
kanbai.app. No DS 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 200
Header Value
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://kanbai.app/api/mcp/public Verified 200
http (plaintext) http://kanbai.app/api/mcp/public HTTPS enforced 308 https://kanbai.app/api/mcp/public
MCP tools · 4 exposed · ~160 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
kanbai_get_sop ~34

Get one public SOP by numeric id, including its full content.

NameTypeReqDescription
idintegeryesSOP id.
NameTypeReqDescription
sopobjectyes–

No examples provided.

kanbai_get_template ~50

Get one public project template by numeric id, including its ordered task list (title, description, status/priority defaults, offset and duration in days).

NameTypeReqDescription
idintegeryesTemplate id.
NameTypeReqDescription
templateobjectyes–

No examples provided.

kanbai_list_sops ~26

List Kanbai's public standard operating procedures (title, category).

Input schema present but exposes no named parameters.

NameTypeReqDescription
sopsarrayyes–

No examples provided.

kanbai_list_templates ~50

List Kanbai's public project templates (name, description, task count). Templates are the reusable task graphs new projects are instantiated from — public reference content, not a customer's live project data.

Input schema present but exposes no named parameters.

NameTypeReqDescription
templatesarrayyes–

No examples provided.

Install

How do I install the Kanbai — public project templates and SOPs MCP server?

Kanbai — public project templates and SOPs is a hosted endpoint at https://kanbai.app/api/mcp/public, 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 · kanbai.app

# add to Claude Code
claude mcp add --transport http app-kanbai-discovery 'https://kanbai.app/api/mcp/public'
Common questions

What is the Kanbai — public project templates and SOPs MCP server?

Kanbai — public project templates and SOPs is an MCP server listed in the public MCP registry as app.kanbai/discovery. Read-only access to Kanbai's public project templates and SOPs. Public, no authentication. This page covers its hosted endpoint (https://kanbai.app/api/mcp/public).

Is the Kanbai — public project templates and SOPs MCP server safe to use?

Kanbai — public project templates and SOPs scores 86 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 Kanbai — public project templates and SOPs MCP server expose?

Kanbai — public project templates and SOPs exposes 4 tools: kanbai_list_templates, kanbai_get_template, kanbai_list_sops, kanbai_get_sop. Their descriptions and schemas cost roughly 160 tokens of context every time the server is loaded.

Does the Kanbai — public project templates and SOPs MCP server require authentication?

No. We connected to Kanbai — public project templates and SOPs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Kanbai — public project templates and SOPs MCP server still maintained?

Kanbai — public project templates and SOPs is still listed as active in the MCP registry. We last reached this channel on 21 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 Kanbai — public project templates and SOPs MCP server?

VerifyMCP ran 13 checks on Kanbai — public project templates and SOPs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.