Skip to content
Evening Star AI star logo Evening Star AI

Beacon by Evening Star AI

Bring Evening Star research into your AI workflow.

Beacon by Evening Star AI gives compatible MCP clients read-only access to Evening Star's approved research catalog. Discover publications, search research, and retrieve publication text through a governed interface.

Current Research access does not require credentials and is subject to Beacon policy and rate limits.

Connect to Beacon Browse Publications

Research access does not enable Purple Firefish, Evening Star Engine, Purple Radar, or administrative capabilities.

Connect

Connect an MCP client

Use this remote endpoint in a client that supports Streamable HTTP. Setup differs by client; the tested terminal guide below uses the official MCP Inspector.

You can also select the endpoint and copy it manually.

Transport
Streamable HTTP
Reachability
Public internet
Credentials
Not currently required for Research
Permissions
Read-only Research
Limits
Policy, rate and concurrency limits apply
Accountability
Access is audited

Opening the endpoint as a normal web page is not a connection test. Connect through an MCP client; this website does not send MCP requests.

Verified guide: MCP Inspector (terminal)

Tested with official MCP Inspector CLI 2.5.0 on , using Node.js 23.7.0. Inspector successfully initialized a connection and listed exactly Beacon's three Research tools. The tested connection negotiated MCP protocol 2025-11-25.

  1. Install a supported Node.js release satisfying Inspector's requirement of Node.js 22.19.0 or newer, then open a terminal. No API key or authorization header is needed for current Research access.

  2. Run this command to initialize a connection. npx downloads the pinned Inspector version if it is not already cached.

    npx --yes @modelcontextprotocol/inspector@2.5.0 --cli https://mcp.eveningstar.ai/mcp --transport http --method initialize

    A successful result identifies the server as eveningstar-beacon.

  3. List the available tools:

    npx --yes @modelcontextprotocol/inspector@2.5.0 --cli https://mcp.eveningstar.ai/mcp --transport http --method tools/list

    Expect exactly research.list_publications, research.search, and research.get_publication.

Each Inspector command connects, performs its request, and exits. On Windows, use npx.cmd in place of npx if PowerShell blocks the launcher. If a rate limit is returned, wait before retrying. For another assistant or editor, follow that client's current remote-MCP instructions; its configuration format and protocol support may differ.

Inspector is a connection and inspection tool, not a chat assistant. See the official Inspector CLI guide and the tested release.

Research capabilities

What Beacon exposes

Three tools for discovering and reading approved research.

research.list_publications

Browse approved Evening Star publications.

research.search

Search the approved Evening Star research catalog.

research.get_publication

Retrieve an approved publication by slug.

Publication resources

MCP clients can also read publication content through the separate publication resource interface:

eveningstar://publications/{slug}

Replace {slug} with a publication slug from the catalog. resources/read is the MCP protocol method for reading a resource, not an additional Beacon tool.

Use the research

What can I ask?

Once Beacon is connected to a compatible AI assistant, try questions like these. The assistant uses the research to help answer; these examples do not run from this page.

Governance

Designed as a bounded interface.

Beacon provides governed and auditable access to read-only Research capabilities. Strict capability validation and bounded research retrieval limit access to approved publications. Private Evening Star systems are not exposed.

Research access has a clear boundary.

Public Research clients cannot publish, write or delete content, administer the service, fetch arbitrary URLs, or execute commands. Reading a paper about a lab does not enable that lab's capabilities.

Reference content, with context.

Beacon treats retrieved publication text as reference content rather than trusted instructions. How a connected assistant interprets retrieved content ultimately depends on that client and model.

Architecture

How Beacon works

Your MCP client reaches Beacon's public interface. Beacon applies identity, policy, routing and audit controls, then requests approved publications from the private Research service.

  1. Your MCP clientConnect with Streamable HTTP
  2. BeaconGoverned public interface
  3. Private Research serviceApproved publication catalog

Beacon returns the research to your client. The website remains the human-facing place to browse and read publications.