Brent Burgess
REMOTE · BRENTBURGESS.COM
Read-only facts from brentburgess.com: profile, writing, projects and the site's own datasets.
Available components
Last scanned (22 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1213 tokens (~71/item across 17 items; 7 tools + 10 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 0
- Server version: 1.0.0+1d2fb800b1b3d497 → 1.0.0+ae830e0789adbee3 functional
- 3 Nov 26 +1
- Server version: 1.0.0+2e0d4fb70a91aae7 → 1.0.0+1d2fb800b1b3d497 functional
- 2 Nov 26 0
- Server version: 1.0.0+e66bdbe5e601cf87 → 1.0.0+2e0d4fb70a91aae7 functional
- 1 Nov 26 +1
- Server version: 1.0.0+ec1d0cfd8306a932 → 1.0.0+e66bdbe5e601cf87 functional
- 31 Oct 26 0
- Server version: 1.0.0+01b859c1aaea06ef → 1.0.0+ec1d0cfd8306a932 functional
- 30 Oct 26 +1
- Server version: 1.0.0+4aad11858d49cf2d → 1.0.0+01b859c1aaea06ef functional
- 29 Oct 26 0
- Server version: 1.0.0+edef015d060ad51b → 1.0.0+4aad11858d49cf2d functional
- 28 Oct 26 +1
- Server version: 1.0.0+85ce23a24fa4a7df → 1.0.0+edef015d060ad51b functional
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 4 Nov 2026 · Probed https://brentburgess.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=brentburgess.com | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | eb2a97e0254f73ab13afd62b2ad3bad2 |
| SANs: brentburgess.com, *.brentburgess.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 brentburgess.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| brentburgess.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://brentburgess.com/mcp | Verified | 200 | |
| http (plaintext) | http://brentburgess.com/mcp | HTTPS enforced | 301 | https://brentburgess.com/mcp |
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 →
fetch Read a post, case study or page ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | What to read: an id, path, URL, URI or slug, with an optional #anchor |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Its id, with #anchor when one section was read |
| metadata | object | yes | About the text |
| text | string | yes | The text as Markdown, links absolute |
| title | string | yes | Its title |
| url | string | yes | Its URL, with #anchor when one section was read |
No examples provided.
get_profile Who Brent Burgess is ~63
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | object | yes | His availability for work, as the site states it |
| contact | object | yes | How to reach him |
| intro | string | yes | A short introduction, in his words |
| job_title | string | yes | His job title |
| location | string | yes | Where he is based |
| name | string | yes | His name |
| pages | array | yes | Every page on the site |
| skills | array | yes | What he works with |
| tagline | string | yes | One line on what he does |
| url | string | yes | The site |
No examples provided.
get_site_stats This site’s own numbers ~73
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 and CI runs, and the nightly pipeline’s tests and sources, each with the last day the data covers. For the tables behind them, use query_dataset.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| automated | object | yes | Crawlers, bots and scans |
| building | object | yes | Building the site |
| data_through | string | yes | The last day the numbers cover |
| datasets | array | yes | The tables behind the numbers |
| monthly | object | yes | When the next monthly page and country counts appear |
| pipeline | object | yes | The nightly pipeline |
| reading | object | yes | Reading the site, since launch |
| see_also | array | yes | Pages with numbers this server does not return |
| url | string | yes | The page that shows them |
No examples provided.
list_content List everything published ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Only this kind: post, case_study or page |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | How many items are listed |
| items | array | yes | Posts and case studies newest first, then pages |
No examples provided.
list_projects List his projects ~62
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".
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Only projects with this status |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | How many projects are listed |
| projects | array | yes | The projects, in the order the site lists them |
No examples provided.
query_dataset Read one of the site’s data tables ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | Which table, as get_site_stats lists them |
| from | string | – | The earliest date to include |
| limit | integer | – | How many rows to return at most, 1 to 500 |
| to | string | – | The latest date to include |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The columns, in order |
| data_through | string | yes | The last day the data covers |
| dataset | string | yes | The table |
| date_column | – | yes | The column from and to apply to, or null if the table has none |
| description | string | yes | What a row is |
| grain | string | yes | One row per |
| notes | array | yes | What /data says about these numbers, word for word |
| returned | integer | yes | How many rows were returned |
| rows | array | yes | The rows, oldest first |
| rows_from | – | yes | The first date kept; older rows are left out of the server. Null when every row is kept. |
| title | string | yes | What it holds |
| total | integer | yes | How many rows matched |
| truncated | boolean | yes | Whether more rows matched than were returned |
| url | string | yes | Where /data shows it |
No examples provided.
search Search the site ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Only this kind: post, case_study, page or project |
| limit | integer | – | How many results to return, 1 to 10 |
| query | string | yes | Keywords to look for |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The query searched for |
| results | array | yes | The best matches, best first |
| total | integer | yes | How many sections matched in all |
No examples provided.
How do I install the Brent Burgess MCP server?
Brent Burgess is a hosted endpoint at https://brentburgess.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 · brentburgess.com
claude mcp add --transport http com-brentburgess-site 'https://brentburgess.com/mcp'
What is the Brent Burgess MCP server?
Brent Burgess is an MCP server listed in the public MCP registry as com.brentburgess/site. Read-only facts from brentburgess.com: profile, writing, projects and the site's own datasets. This page covers its hosted endpoint (https://brentburgess.com/mcp).
Is the Brent Burgess MCP server safe to use?
Brent Burgess scores 82 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 Brent Burgess MCP server expose?
Brent Burgess exposes 7 tools: get_profile, list_projects, list_content, search, fetch, and 2 more. Their descriptions and schemas cost roughly 647 tokens of context every time the server is loaded.
Does the Brent Burgess MCP server require authentication?
No. We connected to Brent Burgess without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Brent Burgess MCP server still maintained?
Brent Burgess is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.