_ registry / mcp + a2a http-sse · checked 23m ago

bo-kendell-portfolio

https://bokendell.com

Registry code: c19d8a4cd27ebc73

api record

Bo Kendell's public portfolio, exposed over MCP. Tools: list_* for overviews, get_* for full detail. Resources: the same content as addressable documents — `portfolio://profile` for the summary, `portfolio://projects/{slug}` and `portfolio://writing/{slug}` for individual pieces. Prefer tools when filtering or searching, resources when you want a whole document to read or cite. All data is read-only and public — no auth required.

endpoint
https://bokendell.com/mcp
door code
bf33d7ff3be81d02
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is bo-kendell-portfolio live?
Yes — it answered the hub's last check (checked 23m ago). It answered 97% of checks over the last 30 days.
Is bo-kendell-portfolio free to use?
Yes — the hub reached it with no key and no payment.
What tools does bo-kendell-portfolio have?
8 tools: list_posts, get_post, get_project, get_activity, get_experience, get_tech_stack, list_projects, get_profile.
Is bo-kendell-portfolio safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97.2%

90 days 92.1%· all time 91.9%

latency
10,834ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 793 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
productivity & business hr & recruiting
used for
  • read a developer's portfolio
  • list a developer's projects
  • get a developer's work experience
  • read a developer's posts
takes → gives
text → data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
5 open 3 never probed 5 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_activity reads open 7h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_experience reads open 4h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "type": {
      "enum": [
        "employment",
        "education",
        "project",
        "certification",
        "award"
      ],
      "type": "string"
    }
  }
}
    arguments 16 lines
  • get_tech_stack reads open 7h ago

    Technologies Bo works with, grouped by category.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • list_projects reads open 7h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "lifecycle": {
      "enum": [
        "building",
        "shipping",
        "retired"
      ],
      "type": "string",
      "description": "Filter by lifecycle. Omit to return all."
    }
  }
}
    arguments 15 lines
  • get_profile reads open 4h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • list_posts reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_post reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Post slug."
    }
  }
}
    arguments 13 lines
  • get_project reads unknown 4h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Project slug (e.g. 'warm-machine')."
    }
  }
}
    arguments 13 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c19d8a4cd27ebc73.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c19d8a4cd27ebc73/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c19d8a4cd27ebc73/badge.svg)](https://brick.blue/agent/c19d8a4cd27ebc73?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.