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

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

Available components

−20 this week 69 Trust /100

Last scanned (2 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Developer Tools

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 Security57
Transport & Reachability0
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 849 tokens (~47/item across 18 items; 8 tools + 10 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 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
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.

  • 5 Nov 26 −20
    • Authorization: partial → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
  • 14 Oct 26 +10
    • Transport: fail → pass ▲ security
  • 13 Oct 26 −10
    • Transport: pass → fail ▼ security
  • 4 Oct 26 +10
    • Transport: fail → pass ▲ security
  • 3 Oct 26 −10
    • Transport: pass → fail ▼ security
  • 2 Oct 26 89
    • Transport: fail → pass ▲ security
    • Schema quality: 604 → 849 ▼ functional
    • Resource “removing one llm round-trip from a voice caddy” was removed ▼ functional
    • New resource “SimRig” functional
    • New resource “custom architecture checks as guardrails for coding agents” functional
    • New resource “how the caddy's prompt is layered” functional
    • New resource “keeping the caddy's evals honest” functional
    • New resource “the evals behind bagman's caddy” functional
  • 1 Oct 26 0
    • Transport: pass → fail ▼ security
    • Schema quality: 381 → 604 ▼ functional
    • New resource “Bagman” functional
    • New resource “Swarm” functional
    • New resource “making the site readable to agents” functional
    • New resource “removing one llm round-trip from a voice caddy” functional
    • New resource “this site” functional
  • 30 Sept 26 0
    • Authorization: unverified → partial ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → 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 5 Nov 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 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA256 6dcba1a2a2b73a60e51ec589f8108c7
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 Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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 Unreachable
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
lifecyclestring–Filter by lifecycle. Omit to return all.

No output schema declared.

No examples provided.

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'
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 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 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?

Its publisher declares no required credentials for Bo Kendell — Portfolio. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.