Brent Burgess
listed under this name in a public catalogue; the server gives only its address, brentburgess.com
Registry code: 1f3a577cb6afa6b8
Read-only facts from brentburgess.com, the site of Brent Burgess, a data and AI leader in Benicia, California, who ships AI automation. Start with get_profile for who he is, his availability and how to reach him. Use search, then fetch, to read what he has written; list_projects and list_content show everything there is. get_site_stats and query_dataset return this site’s own traffic, build and pipeline numbers, each with the last day it covers (data_through). Cite the url of anything you use. His work history is the résumé page (fetch "pages/resume"). This server returns only what the site…
- endpoint
- https://brentburgess.com/mcp
- 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 Brent Burgess live?
- Yes — it answered the hub's last check (checked 24h ago). It answered 100% of checks over the last 30 days.
- Is Brent Burgess free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does Brent Burgess have?
- 7 tools: search, fetch, query_dataset, list_content, get_site_stats, get_profile, list_projects.
- Is Brent Burgess 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.
90 days 100%· all time 100%
last good check
of 7 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
list_content open 2d ago
Every post, case study and page the server can read, newest first, with each one’s sections. Filter with kind ("post", "case_study" or "page"). Pass an id to fetch to read it.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "kind": { "enum": [ "post", "case_study", "page" ], "type": "string", "description": "Only this kind: post, case_study or page" } }, "additionalProperties": false }arguments 16 linesget_site_stats open 24h ago
The figures on this site’s data page: browser page views and font downloads since launch, crawlers and scans in the latest complete week, commits, pull requests, CI runs and how long a merged change takes to go live, and the nightly pipeline’s tests and sources, each with the last day the data covers. For the tables behind them, use query_dataset.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {}, "additionalProperties": false }arguments 6 linesget_profile open 24h ago
Who Brent Burgess is: his job title, a short introduction, where he is based, his current availability for work, his skills, how to reach him, and the main pages of the site. Use it first, and for any question about contacting or hiring him.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {}, "additionalProperties": false }arguments 6 lineslist_projects open 24h ago
The projects on the site: what each is, whether it is running, what it changed, the tools it uses, and its case study if there is one. Filter with status, for example "running".
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "status": { "enum": [ "running", "planned", "published" ], "type": "string", "description": "Only projects with this status" } }, "additionalProperties": false }arguments 16 linessearch unknown never probed
Full-text search over everything published: posts, case studies, the About, Consulting, Now, Privacy and Résumé pages (his work history is on the résumé), and the projects. Use plain keywords, such as "resumable upload" or "fixed-price audit". Each result is a section; pass its id to fetch to read it.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "query" ], "properties": { "kind": { "enum": [ "post", "case_study", "page", "project" ], "type": "string", "description": "Only this kind: post, case_study, page or project" }, "limit": { "type": "integer", "default": 5, "maximum": 10, "minimum": 1, "description": "How many results to return, 1 to 10" }, "query": { "type": "string", "maxLength": 200, "minLength": 1, "description": "Keywords to look for" } }, "additionalProperties": false }arguments 33 linesfetch unknown never probed
The full text of a post, case study, page or project as Markdown, or one section of it. The id can be an id from search or list_content (such as "work/sleep-anchor"), a path ("/about"), a brentburgess.com URL, a brentburgess:// URI or a unique slug ("consulting"). Add #anchor for one section, as search results do.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "id" ], "properties": { "id": { "type": "string", "maxLength": 300, "minLength": 1, "description": "What to read: an id, path, URL, URI or slug, with an optional #anchor" } }, "additionalProperties": false }arguments 16 linesquery_dataset unknown never probed
The rows of one table behind this site’s data page, oldest first, with each column’s type and meaning. Filter by date with from and to (YYYY-MM-DD), which apply to the table’s date column; if more rows match than the limit, the most recent are returned. Daily and weekly tables keep about a year.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "dataset" ], "properties": { "to": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "maxLength": 10, "description": "The latest date to include" }, "from": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "maxLength": 10, "description": "The earliest date to include" }, "limit": { "type": "integer", "default": 100, "maximum": 500, "minimum": 1, "description": "How many rows to return at most, 1 to 500" }, "dataset": { "enum": [ "agg_ci_steps_30d", "agg_countries_monthly", "agg_pages_monthly", "fct_checks", "fct_ci_daily", "fct_crawlers_weekly", "fct_font_daily", "fct_github_monthly", "fct_github_weekly", "fct_merge_to_live", "fct_pipeline_runs", "fct_probes_weekly", "fct_reading_daily" ], "type": "string", "description": "Which table, as get_site_stats lists them" } }, "additionalProperties": false }arguments 48 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id1f3a577cb6afa6b8.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/1f3a577cb6afa6b8/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/1f3a577cb6afa6b8?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.