← Index

Junê

io.github.Junemind/june-mcpv0.4.3Search

Shared, cited knowledge-graph memory for agents — ask, search, remember, keep standing instructions

The current version, v0.4.3, was published to the official MCP registry on 2026-09-18. It is distributed as june-mcp on PyPI, filed under Search by this index, and declares 13 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Junê in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-09-29 05:05 UTC
screened 2026-08-30tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidenceNo malicious instructionsvia static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-19).

Contracts can change after screening, with no version bump. The gate pins Junê’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for Junê](https://mcpindex.ai/server/io-github-junemind-june-mcp) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-junemind-june-mcp">Independent trust record for Junê</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-junemind-june-mcp)](https://mcpindex.ai/server/io-github-junemind-june-mcp)
HTML
<a href="https://mcpindex.ai/server/io-github-junemind-june-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-junemind-june-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
JUNE_BASE_URL
required

Your June endpoint, e.g. http://localhost:8000 (the Junê desktop app's local engine, your own june-local service, or a hosted Team workspace)

JUNE_CANVAS
required

The canvas (workspace) to bind this connection to — a name (e.g. 'work') or a canvas id; names resolve at startup and ambiguous names fail closed

JUNE_API_KEY
requiredsecret

Your June API key (set JUNE_ALLOW_ANON=1 instead to explicitly opt out for keyless local setups)

JUNE_LLM_KEY
secret

Bring-your-own LLM key for cited answers — forwarded per-request as a header, never logged or stored on the service

JUNE_CANVAS_CREATE

Set to 1 to create the named canvas on first run if it doesn't exist yet (refused in read-only mode)

JUNE_READONLY

Set to 1 to hide and refuse all write tools (memory becomes read-only)

JUNE_FILES_ROOT

Opt-in directory agents may upload files from via june_ingest_file — unset means that tool doesn't exist

JUNE_DOCS_CANVAS

Canvas holding the agent's standing docs/skills/learnings (default 'agent_docs')

JUNE_DOCS_REFRESH

Set to 0 to disable the periodic standing-docs digest re-injected on tool results (default on)

JUNE_REFRESH_CALLS

Tool calls between digest injections (default 12) — lower it for small-context agents

JUNE_REFRESH_MINUTES

Wall-clock fallback between digest injections (default 10)

JUNE_DIGEST_CHARS

Standing-docs digest size cap in characters (default 2000)

JUNE_EXPORT_ROOT

Opt-in directory for repo sync — enables june_docs_export / june_page_export / june_page_import (fenced writes, commit-only git); unset means those tools don't exist

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Search