Skip to main content
Zachary Roth

Agent Access

This site gives agents anonymous, read-only access to the same public work, writing, experience, and contact options available to human visitors.

Connect a remote client

You need an MCP client that supports Streamable HTTP and protocol revision 2025-11-25 or 2025-06-18. You do not need credentials.

  1. Add https://zacharyr0th.com/mcp as a remote Streamable HTTP server.
  2. Connect without an account, API key, cookie, or access token.
  3. Call tools/list and read the live tool schemas.
  4. Call tools/call with only the arguments declared by the selected tool.

Two access paths

Remote MCP

The public Model Context Protocol (MCP) endpoint is https://zacharyr0th.com/mcp. A compatible client can connect over Streamable HTTP, list the available tools, and call them through JSON-RPC. The endpoint returns JSON responses and does not require an account, API key, cookie, or access token.

The server supports MCP protocol revisions 2025-11-25 and 2025-06-18. It does not yet claim support for the newer 2026-07-28 stateless protocol revision. See the official Streamable HTTP specification and tools specification.

WebMCP

WebMCP lets a page register structured JavaScript tools with a browser-based agent. When a browser exposesdocument.modelContext, every page on this site registers the same seven public tools and routes their execution through the remote MCP endpoint. Browsers without WebMCP support continue to receive the normal website.

WebMCP is a Web Machine Learning Community Group draft, not a W3C Standard. Chrome 149 introduced it through an experimental origin trial. The API and browser support can change while the proposal develops.

To use this path, open any page in a WebMCP-capable browser. The page registers its tools automatically. The browser or agent controls whether and when to invoke a tool.

Available tools

search_work
Search selected public projects by a case-insensitive query.
get_project
Retrieve one public project by its canonical identifier.
list_publications
List up to 50 published articles and publications.
get_publication
Retrieve one publication by its canonical identifier.
search_writing
Search public article metadata by a case-insensitive query.
get_experience
Retrieve the published professional summary, focus areas, and featured systems.
get_contact_options
Retrieve public email and profile links without sending a message.

Tool inputs use JSON Schema. Search queries are limited to 200 characters and return at most 20 matches. Results include a canonical source URL, content type, modification date, and structured data so clients can preserve provenance.

Safety boundary

Every tool is marked read-only and non-destructive. The tools expose only information already published on this site. They exclude private profiles, personal records, job-search records, workspace facts, credentials, and unpublished material. The contact tool returns contact options but cannot send a message.

Tool annotations are guidance for clients, not a security boundary. The server enforces its boundary at execution time through these controls:

  • Reject requests that include credentials or cookies.
  • Validate the request origin and host.
  • Limit request bodies to 32 KiB and responses to 128 KiB.
  • Stop tool execution after 10 seconds.
  • Limit each network source to 30 requests per minute.

Privacy and telemetry

The MCP endpoint does not require identity. Operational telemetry can record:

  • The tool name and transport type.
  • The outcome and response status.
  • The execution duration.
  • An anonymous page-session identifier for WebMCP requests.

Hosting and security logs may process ordinary request data for abuse prevention and diagnostics. The site does not receive an assistant's private conversation unless the assistant includes part of it in a tool request.

See the privacy notice for retention and third-party processing details. Use is governed by the terms of use and the published security policy.

Discovery

Clients can connect directly to /mcp. The site also publishes complementary discovery documents for clients that begin with the domain rather than a known endpoint.

  • Agent tool manifest: the canonical site-specific inventory of tools, schemas, protocol revisions, and boundaries.
  • API catalog: an IETF RFC 9727 catalog that links the endpoint and manifest.
  • AI catalog and MCP server card: experimental discovery metadata, not stable MCP core features.
  • LLM index and full LLM context: Markdown summaries that follow the community llms.txt proposal.
  • Work, writing, and individual article Markdown routes: direct content representations for agents that do not need the visual interface. Canonical page URLs also return Markdown when requested with Accept: text/markdown.
  • XML sitemap and schema map: indexes for canonical pages and machine-readable descriptions.

Static manifests are advisory. Clients should treat the live MCP handshake, capability response, tool list, and runtime errors as authoritative when discovery metadata and runtime behavior differ.

Official references