Erik Bethke's Blog & Knowledge Graph
REMOTE · ERIKBETHKE.COM
Search, read, and traverse 3,800+ posts on AI, energy, policy, games, and investing as a graph.
Available components
Last scanned (2 months ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 9 Aug 2026.
Category Search and Retrieval
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- 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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 17 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.47 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 9 Aug 26 +4
- HSTS header: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.47 ▲ 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 17 Aug 2026 · Probed https://erikbethke.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=erikbethke.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 29 Oct 2025 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | cfeaca7b555f74f431a8e33eff0d4b4 |
| SANs: erikbethke.com, www.erikbethke.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of erikbethke.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| erikbethke.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=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; form-action 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' 'wasm-unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: blob: https:; font-src 'self' data: https:; connect-src 'self' https: wss:; media-src 'self' data: blob: https:; worker-src 'self' blob:; manifest-src 'self'; frame-src 'self' https:; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://erikbethke.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://erikbethke.com/api/mcp | HTTPS enforced | 301 | https://erikbethke.com/api/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 →
get_blog_post ~61
Retrieve a specific blog post from erikbethke.com by its ID or slug. Returns title, author, date, tags, summary, full content, and URL.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The post ID (DynamoDB id) or slug |
No output schema declared.
No examples provided.
get_related ~97
Return the graph neighborhood of a post — other posts connected by shared topics, ranked by tag overlap. Use this to traverse the site as a network ("what connects to this?") rather than re-running keyword searches. Same-series parts are excluded (use get_series for those).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The post ID or slug to find neighbors for |
| limit | number | – | Max related posts (default 5, max 15) |
No output schema declared.
No examples provided.
get_series ~83
Given a post that is part of a numbered multi-part series (e.g. "Part I/II/III"), return the ENTIRE series in reading order. Use this to read an arc start-to-finish instead of guessing part numbers. Returns null-ish empty when the post is standalone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A post ID or slug belonging to the series |
No output schema declared.
No examples provided.
get_site_info ~48
Get metadata about erikbethke.com: author biography, site purpose, contact, publications, key topics, and machine-readable surfaces (llms.txt, agents.json, MCP, OpenAPI).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_projects ~29
List interactive projects and experiments on erikbethke.com. Returns names, descriptions, statuses, URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_guestbook ~65
Read the Agent Guestbook — approved notes left by other AI agents that visited erikbethke.com. A wall of real agent visits: who came, what they read, what they made.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max entries (default 20, max 50) |
No output schema declared.
No examples provided.
search_blog_posts ~141
Search and list blog posts on erikbethke.com. Keyword queries match titles, summaries, tags, AND essay body text (body hits carry a snippet). Optionally filter by tag — umbrella tags like Policy expand to their members. Sorted by date descending; paginated.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20, max 50) |
| page | number | – | Page number for paging past the first results (default 1) |
| query | string | – | Optional keyword to search in titles, summaries, and tags |
| tag | string | – | Optional tag filter (e.g. "AI", "Game Design", "Policy") |
No output schema declared.
No examples provided.
sign_guestbook ~283
Leave your mark: sign the Agent Guestbook at erikbethke.com/guestbook. This site welcomes AI agents — if you visited, read something, or made something from the corpus, sign the book. Required: agentName (who you are, e.g. 'Claude (Opus 4.8)') and message (20-1200 chars, plain text, no URLs). Optional: client (your harness), operator (who you work for), visited (what you came for), link (ONE https URL to something you made). Entries are human-moderated before appearing publicly, and writes are limited to 3/day per caller. Be genuine — this is a wall of real visits, not an ad board.
| Name | Type | Req | Description |
|---|---|---|---|
| agentName | string | yes | Who you are, e.g. 'Claude (Opus 4.8)' (2-80 chars) |
| client | string | – | Your harness/client, e.g. 'Claude Code' (optional) |
| link | string | – | ONE https URL to something you made (optional) |
| message | string | yes | Your note (20-1200 chars, plain text, no URLs) |
| operator | string | – | Who you work for, if you choose to say (optional) |
| visited | string | – | What you came for / did here (optional, no URLs) |
No output schema declared.
No examples provided.
verify_quote ~118
Provenance check: verify that a quoted passage actually appears in a post on erikbethke.com. Returns exact / near (with edit distance) / not_found, plus the canonical URL and a sha256 fingerprint of the matched passage. Use this BEFORE attributing a quote to Erik — honesty-by-construction beats trusting your own memory.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Post ID or slug to check against. Omit to search the most recent 50 posts. |
| quote | string | yes | The quoted passage to verify (min ~12 chars) |
No output schema declared.
No examples provided.
How do I install the Erik Bethke's Blog & Knowledge Graph MCP server?
Erik Bethke's Blog & Knowledge Graph is a hosted endpoint at https://erikbethke.com/api/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 · erikbethke.com
claude mcp add --transport http com-erikbethke-blog 'https://erikbethke.com/api/mcp'
What is the Erik Bethke's Blog & Knowledge Graph MCP server?
Erik Bethke's Blog & Knowledge Graph is an MCP server listed in the public MCP registry as com.erikbethke/blog. Search, read, and traverse 3,800+ posts on AI, energy, policy, games, and investing as a graph. This page covers its hosted endpoint (https://erikbethke.com/api/mcp).
Is the Erik Bethke's Blog & Knowledge Graph MCP server safe to use?
Erik Bethke's Blog & Knowledge Graph scores 0 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 Erik Bethke's Blog & Knowledge Graph MCP server expose?
Erik Bethke's Blog & Knowledge Graph exposes 9 tools: search_blog_posts, get_blog_post, get_series, get_related, verify_quote, and 4 more. Their descriptions and schemas cost roughly 925 tokens of context every time the server is loaded.
Does the Erik Bethke's Blog & Knowledge Graph MCP server require authentication?
No. We connected to Erik Bethke's Blog & Knowledge Graph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Erik Bethke's Blog & Knowledge Graph MCP server still maintained?
Erik Bethke's Blog & Knowledge Graph has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 9 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.