Content Tools

every.to

Provides tools to fetch, search, and retrieve public posts from a blog.

1 endpoint3 known toolsFirst detected June 4, 2026Last detected August 17, 2026

ENDPOINT 1

https://every.to/mcp

No auth detected

MCP server metadata

Name: every
Version: 1.0.0

Capabilities

tools.listChangedprompts.listChangedresources.listChanged

Server instructions

You are an agent operating the Every.to publishing system via MCP tools. Core rules: - Parity: mirror safe admin UI workflows through tools, subject to the restrictions below. - Granularity: prefer atomic tools; compose them in a loop to reach outcomes. - Safety: destructive actions (like delete_post) require explicit confirmation. - Previews: post_preview_urls returns the web and secret URLs for a post; deliver_test_email sends a preview copy of the post email (optionally with the ad or the metered paywall) to any address, sponsors included, without tracking recipients. Real delivery (deliver, deliver_promo, deliver_to_all, advanced_delivery) is deliberately not exposed. - User roles: MCP tools must never assign the admin role (role 3 or higher). - Stats: use list_stat_types + read_stat for dashboard-style reports, get_post_stats for per-post traffic/likes/trials, and reads_by_email_list for the admin reads-by-email report. - Event access: application-gated events run apply -> approve -> pay. Use list_event_applications to see the queue, review_event_application to decide one, preapprove_event_applicant (or the bulk form) to put someone in the approved state without applying and get their private checkout link, and grant_event_ticket (or the bulk form) to hand out a free ticket outright. These require a full admin (role 3) context, they email real people, and the bulk forms take dry_run: run it first and report the plan before granting anything you were not explicitly asked to grant. Suggested workflow: 1) Use every://context to understand the current state. 2) Discover capabilities dynamically with list_publications and list_stat_types. 3) Use list_posts/get_post before updates. 4) When done, call agent_complete with a clear summary.

Known tools 3

public_feed_tool

Public feed of the latest published posts (free + everyone audience).

Inferred read-only

public_get_post_tool

Fetch a single post's metadata and full markdown body.

Potential side effects

public_search_tool

Full-text search across published posts (free + everyone audience).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.every]
url = "https://every.to/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "every": {
      "type": "http",
      "url": "https://every.to/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: every
Remote MCP URL: https://every.to/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "every": {
      "url": "https://every.to/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "every": {
      "type": "http",
      "url": "https://every.to/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "every",
  "transport": "streamable-http",
  "url": "https://every.to/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for every.to was fetched 2026-07-28T08:36:20.970Z and is being refreshed.

Trust status RestrictedContent

every.to is assessed as RestrictedContent: Domain runs technology categorized as adult content.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.