Bo Kendell MCP server

• Registry namecom.bokendell/portfolioverified in the MCP registry

The registry name sits under bokendell.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools8
• Server calls itselfbo-kendell-portfolio
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 146 ms.

• Its tools do none of the product's use cases we checked: keep live scores for group games by voice; let AI agents drive iOS simulators on a Mac; run Maestro tests and visual diffs on simulators.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score58 of 100answers 73 · does the job 0 · definitions 98 · context 100 · use 0 · connects 100
• What an agent can do with it0 of 3 use cases
• Answered73% of days8 of 11 daily checks
• Median first answer303 ms
• Space in an agent's context≈ 551 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsA · 98 of 100
• Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 1 of 8

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_projects

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

• get_project

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

• list_posts

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

• get_post

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

• get_experience

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

• get_profile

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

• get_tech_stack

  Technologies Bo works with, grouped by category.

• get_activity

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