Bryan Thompson
MCP and agent infrastructure engineer
I build tooling that makes MCP servers testable before they ship.
- 370+Merged pull requests I authored, four public directory repositories
Most are catalog operations, a good share of them emitted by the same automation.
- 5,500+Pull requests merged through those repositories
Submissions and rolling updates moving through automation that scans, validates, and policy-checks each one before it reaches a merge decision.
- 85+Tool-annotation pull requests merged into external repositories
Authored from
github.com/bryankthompsonrather than the other account this page links.
Every figure is a floor, and each links to a live GitHub search that recomputes it. One example of the engineering among the catalog operations: the bump loop and the recovery job that catches it. It is one change, not the whole pipeline.
- Verification gates
if not s.strip(): allow()is the obviously correct short-circuit at the top of a gate that runs before an agent emits text a human will act on, and it is deliberately absent from mine: a gate written in one language guarding a sender written in another inherits every disagreement between their standard libraries. - Skill evaluation rig
A black-box harness I built drives a real agent runtime against fixtures I control and scores what happened rather than reasoning from the spec.
- Fleet messaging
Between agent sessions I let a message select what to verify, and never let it supply what is concluded.
- Gated actions
I bind an approval to a hash of the exact request and write the record before the action, so a crash or a retry cannot spend twice.
- Fail-closed tools
I gave an agent encrypted mail with no tool that sends, so the harm has no path, and a reply waits for its audit entry.
- GPU profiling
I count the synchronizing calls before changing a pipeline and accept a speed-up only when interleaved pairs show it.