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.

Bo Kendell — Portfolio

REMOTE · BOKENDELL.COM · SCANNED SEP 20

Bo Kendell's portfolio: projects, writing, work history, resume, and live activity.

Available components

+3 this week 87 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 Security80
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 604 tokens (~43/item across 14 items; 8 tools + 6 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
Install

How do I install the Bo Kendell — Portfolio MCP server?

Bo Kendell — Portfolio is a hosted endpoint at https://bokendell.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 · bokendell.com

# add to Claude Code
claude mcp add --transport http com-bokendell-portfolio 'https://bokendell.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-bokendell-portfolio": {
      "url": "https://bokendell.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-bokendell-portfolio": {
      "type": "http",
      "url": "https://bokendell.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-bokendell-portfolio]
url = "https://bokendell.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-bokendell-portfolio": {
      "type": "remote",
      "url": "https://bokendell.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-bokendell-portfolio --url 'https://bokendell.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-bokendell-portfolio:
    url: "https://bokendell.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-bokendell-portfolio": {
      "Transport": "http",
      "Url": "https://bokendell.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-bokendell-portfolio -t streamable-http -u 'https://bokendell.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-bokendell-portfolio": {
      "type": "http",
      "url": "https://bokendell.com/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.

  • 19 Sept 26 +1

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

  • 17 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.

  • 15 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.

  • 13 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.

  • 12 Sept 26 +19
    • Authorization: unverified → partial security
    • HSTS header: unverified → pass security
    • Transport: fail → pass security
  • 11 Sept 26 −9
    • Transport: pass → fail security
  • 10 Sept 26 −9
    • Authorization: partial → unverified security
    • HSTS header: pass → unverified security
  • 9 Sept 26 +10
    • Authorization: unverified → partial security
    • HSTS header: unverified → 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 20 Sept 2026 · Probed https://bokendell.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bokendell.com CN=WE1,O=Google Trust Services,C=US 1 Sept 2026 30 Nov 2026 ECDSA 256 ECDSA-SHA256 4436b1a491600d12134c580a4dfa6248
SANs: bokendell.com, rig.bokendell.com, *.rig.bokendell.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 insecure

Validation of bokendell.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
bokendell.com. 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 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://us-assets.i.posthog.com https://cdn.jsdelivr.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: blob: https:; connect-src 'self' https://api.bokendell.com https://us.i.posthog.com https://us-assets.i.posthog.com https://o4508753140318208.ingest.us.sentry.io; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests; frame-ancestors 'none'; report-uri /api/csp-report; report-to csp-endpoint
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bokendell.com/mcp Verified 200
http (plaintext) http://bokendell.com/mcp HTTPS enforced 301 https://bokendell.com/mcp
MCP tools · 8 exposed · ~257 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
get_activity ~31

Current GitHub contributions + LeetCode stats. Changes throughout the day — call fresh each time rather than caching.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_experience ~31

Employment, education, projects, certifications, and awards — the full timeline.

NameTypeReqDescription
typestring

No output schema declared.

No examples provided.

get_post ~33

Full post metadata by slug (MDX body is served by the app routes).

NameTypeReqDescription
slugstringyesPost slug.

No output schema declared.

No examples provided.

get_profile ~30

Bo's name, bio, current role, social links. The canonical 'who is this person' summary.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_project ~38

Full project detail — full description, tech stack, links, status.

NameTypeReqDescription
slugstringyesProject slug (e.g. 'warm-machine').

No output schema declared.

No examples provided.

get_tech_stack ~19

Technologies Bo works with, grouped by category.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_posts ~26

Published posts, newest first. Returns metadata only — call get_post for the full body.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_projects ~49

Return every portfolio project (title, brief description, lifecycle, tech stack). Use get_project for the full body + screenshots.

NameTypeReqDescription
lifecyclestringFilter by lifecycle. Omit to return all.

No output schema declared.

No examples provided.

Common questions

What is the Bo Kendell — Portfolio MCP server?

Bo Kendell — Portfolio is an MCP server listed in the public MCP registry as com.bokendell/portfolio. Bo Kendell's portfolio: projects, writing, work history, resume, and live activity. This page covers its hosted endpoint (https://bokendell.com/mcp).

Is the Bo Kendell — Portfolio MCP server safe to use?

Bo Kendell — Portfolio scores 87 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 Bo Kendell — Portfolio MCP server expose?

Bo Kendell — Portfolio exposes 8 tools: list_projects, get_project, list_posts, get_post, get_experience, and 3 more. Their descriptions and schemas cost roughly 257 tokens of context every time the server is loaded.

Does the Bo Kendell — Portfolio MCP server require authentication?

No. We connected to Bo Kendell — Portfolio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Bo Kendell — Portfolio MCP server still maintained?

Bo Kendell — Portfolio 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.