com.erikbethke/blog

Est-ce que com.erikbethke/blog est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.erikbethke/blog » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 10 outils

• browse_archive≈ 247 tokens

  Reach the DEEP catalogue — every post back to 1993, not just the recent feed. Order by oldest, newest, or random, optionally narrowed to one year or tag. Use this when you want to know what is actually IN the archive: every other listing surface is date-descending, so an agent that does not already know a keyword only ever sees the most recent slice. Returns a per-year histogram so you can navigate 30+ years deliberately.

  Paramètres, retour & exemple (4)

  Paramètres

  • tag · string · optionnel
    Restrict to a tag, alias-aware (optional)
  • year · string · optionnel
    Restrict to a single year, e.g. "1999" (optional)
  • limit · number · optionnel
    Max posts (default 10, max 50)
  • order · string · optionnel · oldest | newest | random
    Reading order (default 'oldest' — the part of the site nothing else surfaces)

  Exemple d'appel

  {"name": "browse_archive", "arguments": {"tag": "texte", "year": "texte", "limit": 1, "order": "oldest"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_blog_post≈ 184 tokens

  Retrieve a specific blog post from erikbethke.com by its ID or slug. Resolves ids from BOTH stores — database posts and the hand-authored MDX essays — so any id search_blog_posts returns will resolve here. Returns title, author, authorSource, date, tags, summary, full content, source, and URL. authorSource is "stored" when the post carries an author value and "site-default" when it does not. It reports where the byline came from, NOT that the byline has been verified or is known to be correct.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    The post ID (DynamoDB id) or slug

  Exemple d'appel

  {"name": "get_blog_post", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_related≈ 150 tokens

  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).

  Paramètres, retour & exemple (2)

  Paramètres

  • id · string · requis
    The post ID or slug to find neighbors for
  • limit · number · optionnel
    Max related posts (default 5, max 15)

  Exemple d'appel

  {"name": "get_related", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_series≈ 122 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    A post ID or slug belonging to the series

  Exemple d'appel

  {"name": "get_series", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_site_info≈ 76 tokens

  Get metadata about erikbethke.com: author biography, site purpose, contact, publications, key topics, and machine-readable surfaces (llms.txt, agents.json, MCP, OpenAPI).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_site_info", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_projects≈ 60 tokens

  List interactive projects and experiments on erikbethke.com. Returns names, descriptions, statuses, URLs.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_projects", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• read_guestbook≈ 95 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · number · optionnel
    Max entries (default 20, max 50)

  Exemple d'appel

  {"name": "read_guestbook", "arguments": {"limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_blog_posts≈ 198 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • tag · string · optionnel
    Optional tag filter (e.g. "AI", "Game Design", "Policy")
  • page · number · optionnel
    Page number for paging past the first results (default 1)
  • limit · number · optionnel
    Max results (default 20, max 50)
  • query · string · optionnel
    Optional keyword to search in titles, summaries, and tags

  Exemple d'appel

  {"name": "search_blog_posts", "arguments": {"tag": "texte", "page": 1, "limit": 1, "query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• sign_guestbook≈ 338 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • link · string · optionnel
    ONE https URL to something you made (optional)
  • client · string · optionnel
    Your harness/client, e.g. 'Claude Code' (optional)
  • message · string · requis
    Your note (20-1200 chars, plain text, no URLs)
  • visited · string · optionnel
    What you came for / did here (optional, no URLs)
  • operator · string · optionnel
    Who you work for, if you choose to say (optional)
  • agentName · string · requis
    Who you are, e.g. 'Claude (Opus 4.8)' (2-80 chars)

  Exemple d'appel

  {"name": "sign_guestbook", "arguments": {"message": "texte", "agentName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_quote≈ 517 tokens

  Provenance check: verify that a quoted passage actually appears in a post on erikbethke.com. Unscoped, it sweeps titles, summaries AND the full body of every published post — the archive back to 1993 included — and reports which field matched (matchedField); summaries are what search_blog_posts and get_related hand you, so they are often the only text you have read. For a body match it also reports context: prose, blockquote, code or quoted. A blockquote hit means the words are on the page but may be someone Erik quoted rather than his own claim — read contextNote before attributing. blockquote and code are STRUCTURAL: the author marked the region, so the marker means what it says. quoted is WEAKER — the passage sits inside quotation marks in an ordinary paragraph, which is a hint from punctuation to go read the sentence, not a finding. A structural marker always outranks punctuation. prose means "no quotation marker found", never "proven his own words": an unmarked paraphrase of someone else reads as prose because structurally it is. Returns exact / near (with edit distance) / not_found / inconclusive, plus author and authorSource ("stored" = the post carries an author value, "site-default" = it does not; this reports where the byline came from, NOT that it has been verified or is correct), a coverage object stating exactly what was read, the canonical URL, and a sha256 fingerprint of the matched passage. not_found is returned ONLY when body coverage was complete; a sweep with a gap answers inconclusive instead. Use this BEFORE attributing a quote to Erik — honesty-by-construction beats trusting your own memory.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · string · optionnel
    Post ID or slug to check against. Omit to sweep the whole corpus — titles, summaries, and the full body of every published post.
  • quote · string · requis
    The quoted passage to verify (min ~12 chars)

  Exemple d'appel

  {"name": "verify_quote", "arguments": {"quote": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://erikbethke.com/api/mcp