Skip to main content

MCP server and LangGraph tools for Everesteer

PyPI CI License: MIT

mcp-server-everesteer is an agent-first Model Context Protocol (MCP) server and LangGraph / LangChain toolkit for the Everesteer prediction tournament API (https://api.everesteer.ai). Unofficial, and not affiliated with Everesteer.

Why this exists

Driving Everesteer from an autonomous coding or research agent breaks down when the platform SDK mixes plotting, dataframe libraries, and unguarded HTTP writes into one synchronous module. This project separates concerns cleanly:

Area Official everesteer-api (0.5.0) mcp-server-everesteer
Layering 2,778-line sync client.py + 3,600-line MCP wrapper 6-layer async architecture: transport → safety/journal → models → ops → knowledge → MCP / LangGraph / CLI
Control plane vs. modeling Bundles plotnine/matplotlib, ASCII table formatters, numpy/pandas/scipy, and deprecated shims Zero visualization, zero plotting, zero ML/dataframe dependencies (httpx2, mcp, pydantic, starlette, uvicorn)
Agent token economy Multi-paragraph essays duplicated across raw tool schemas Consolidated agentic tools in 6 cohesive toolsets + everesteer://docs/* resources + dynamic agent_guide
Write & money safety Unguarded writes, no caps, no confirmation, no write journal 3 default-closed gates (ALLOW_WRITES, ALLOW_STAKING, ALLOW_WITHDRAWALS), micro-USDC integer validation (floats refused), daily SQLite caps, MCP Elicitation + LangGraph interrupt()
Long operations Blocking time.sleep loops that time out in Claude Desktop Async polling with MCP progress notifications and a 45 s client wait cap returning resumable pending state
LangGraph Not supported Native [langgraph] extra (get_everesteer_tools, create_everesteer_agent, draw_mermaid) with Command(resume=...) approvals

Architecture

flowchart TB
    user["User / Quant Researcher<br/>[Person]<br/>Configures gates & approves writes"]
    agent["AI Research Agent<br/>[Person / Client]<br/>Claude Code · Desktop · Cursor · LangGraph"]

    subgraph boundary["mcp-server-everesteer [Software System — Python 3.11+ / uv]"]
        direction TB

        subgraph c_surface["Delivery Surface Containers"]
            direction LR
            mcp_srv["MCP Server<br/>[Container: MCPServer / Starlette]<br/>stdio & streamable-http + BearerAuth"]
            lg_int["LangGraph Integration<br/>[Container: LangChain / LangGraph]<br/>In-process _Bridge + interrupt() + draw_mermaid()"]
            cli_app["CLI<br/>[Container: argparse]<br/>serve · auth · status · tools · diagram · logout"]
        end

        subgraph c_core["Agentic Control Plane"]
            direction LR
            ops_eng["Operations & Capabilities<br/>[Component: ops/ + capabilities.py]<br/>6 toolsets · 3 gates · 45s wait cap · progress"]
            know["Knowledge & Prompts<br/>[Component: knowledge/ + resources]<br/>everesteer://docs/* · dynamic AGENT_GUIDE"]
        end

        subgraph c_guard["Safety, Models & State"]
            direction LR
            models["Forward-Compatible Models<br/>[Component: models.py]<br/>Normalized fields · extra='allow' · text hygiene"]
            safety["Safety & Money Guard<br/>[Component: safety.py + money.py]<br/>3 gates · micro-USDC · secret scrubbing"]
            journal[("SQLite Journal & Cache<br/>[Container: SQLite / JSON]<br/>Daily USDC caps · dup block · catalog cache")]
        end

        transport["Async Protocol Transport<br/>[Component: httpx2 + transfer.py]<br/>Read retry · no write retry · presigned S3"]
    end

    subgraph ext["External Systems"]
        direction LR
        api["Everesteer API v1<br/>[External System]<br/>https://api.everesteer.ai/api/v1/*"]
        cdn["Presigned S3 / CloudFront CDN<br/>[External System]<br/>Credential-free dataset & .pkl transfer"]
        chain["Staking Contracts / Wallet<br/>[External System]<br/>USDC deposits · unsigned vault calldata"]
    end

    user -- "Sets gates & confirms writes" --> agent
    agent -- "MCP JSON-RPC (stdio / HTTP)" --> mcp_srv
    agent -- "Direct Python tool calls" --> lg_int
    user -- "Terminal commands" --> cli_app

    mcp_srv --> ops_eng
    mcp_srv --> know
    lg_int --> ops_eng
    lg_int --> know
    cli_app --> ops_eng

    ops_eng --> models
    ops_eng --> safety
    ops_eng --> transport
    safety --> journal
    transport --> journal

    transport -- "HTTPS + X-API-Key (+ CF Access)" --> api
    transport -- "Presigned PUT/POST/GET (no key)" --> cdn
    api -. "Relays locks & settlements" .-> chain

    classDef person fill:#1d4ed8,fill-opacity:0.14,stroke:#1d4ed8,stroke-width:2px
    classDef external fill:#64748b,fill-opacity:0.08,stroke:#64748b,stroke-dasharray:5 4
    classDef guard fill:#dc2626,fill-opacity:0.12,stroke:#dc2626
    classDef box fill:#64748b,fill-opacity:0.04,stroke:#64748b,stroke-opacity:0.45
    class user,agent person
    class api,cdn,chain external
    class safety guard
    class boundary,c_surface,c_core,c_guard,ext box

Model & Tournament Lifecycle

flowchart LR
    start(["whoami & get_started"]) --> mode{"Account Scope?"}

    mode -- "Full Tournament" --> t_data["download_dataset<br/>train / validation / live"]
    t_data --> t_model["create_model<br/>(opaque name)"]
    t_model --> t_path{"Submission Mode?"}
    t_path -- "Auto-Submit (Recommended)" --> t_pkl["upload_model (.pkl)<br/>→ get_model_upload_status<br/>→ set_auto_submit(true)<br/>→ verify lane_active"]
    t_path -- "Manual Per-Round" --> t_man["validate_futures_submission<br/>→ submit_futures_predictions"]
    t_pkl --> t_track["get_submission_status<br/>→ get_daily_progression (T+1..T+20)<br/>→ get_scores"]
    t_man --> t_track
    t_track --> t_stake["Optional: Staking / Vault<br/>(ALLOW_STAKING=true)"]

    mode -- "Hackathon Event" --> h_data["download_dataset<br/>train (labeled) + live/val (blank)"]
    h_data --> h_lane{"Target Board?"}
    h_lane -- "Practice Board (Free)" --> h_val["submit_validation_diagnostics<br/>(preds + .pkl)"]
    h_lane -- "Open Paid Round (Pool)" --> h_evt["submit_event_predictions<br/>(preds + .pkl)"]
    h_val --> h_res["get_diagnostics_run / get_validation_panel<br/>→ get_diagnostics_leaderboard"]
    h_evt --> h_res
    h_res --> h_stand["get_diagnostics_standings<br/>(cumulative across rounds)"]

Write & Money Guardrails

sequenceDiagram
    autonumber
    participant A as AI Agent
    participant G as Capability & Gate Layer
    participant S as Safety & Money Guard
    participant J as SQLite Write Journal
    participant U as Human User
    participant E as Everesteer API

    A->>G: Call mutating tool (e.g. stake_on_model / withdraw_usdc)
    alt Gate disabled (default)
        G-->>A: Tool hidden / Refused with env-var hint
    else Gate enabled
        G->>S: Validate exact micro-USDC (reject float) & per-call/daily caps
        S->>J: Block if identical pending/unknown write exists
        S->>U: Server-authored confirmation (MCP Elicit / LangGraph interrupt)
        alt User declines or client lacks elicitation
            U-->>A: WriteResult(status="declined") — nothing sent
        else User approves
            S->>J: Record pending write + Idempotency-Key
            S->>E: Single HTTP request (never auto-retried)
            alt Definite response
                E-->>J: Mark sent / rejected
                J-->>A: Typed WriteResult
            else Network drop / timeout
                J-->>A: WriteResult(status="unknown", request_id=...)
            end
        end
    end

End-to-End User Walkthrough

All examples use uv (Python 3.11+). Nothing needs to be installed globally unless you want to.

Step 1 — Configure Authentication & Verify Tools

Store your Everesteer API key once (0600 file permissions under ~/.config/mcp-server-everesteer/credentials.json):

uvx mcp-server-everesteer auth

Pass --no-verify to store a key offline, or --cf-access if targeting a staging host protected by Cloudflare Access (CF-Access-Client-Id / CF-Access-Client-Secret). You can also pass EVERESTEER_API_KEY (or EIQ_API_KEY) directly via environment variables.

Inspect your connection, key fingerprint, open gates, and available tools:

uvx mcp-server-everesteer status
uvx mcp-server-everesteer tools

By default (with an API key and all 3 write gates disabled), 45 read-only tools are exposed and all mutating, staking, withdrawal, and destructive tools stay hidden until explicitly enabled.

Step 2 — Connect Your MCP Client

Claude Code

Add it to any Claude Code project in one command (uses the key saved in uvx mcp-server-everesteer auth, or pass -e EVERESTEER_API_KEY=... inline):

# Inside your project directory (project-scoped, reads saved credentials from `auth`):
claude mcp add everesteer --scope project -- uvx mcp-server-everesteer

# Or directly from GitHub (works even before PyPI publish):
claude mcp add everesteer --scope project -- \
  uvx --from git+https://github.com/tukorama/mcp-server-everesteer mcp-server-everesteer

# Or pass the key explicitly and enable writes when ready:
claude mcp add everesteer \
  -e EVERESTEER_API_KEY=eiq_your_api_key \
  -e EVERESTEER_ALLOW_WRITES=true \
  -- uvx mcp-server-everesteer

Or drop a committable .mcp.json at the root of your Claude Code repository (no secrets inside when combined with uvx mcp-server-everesteer auth), then verify with claude mcp list or /mcp inside Claude Code:

{
  "mcpServers": {
    "everesteer": {
      "command": "uvx",
      "args": ["mcp-server-everesteer"]
    }
  }
}

Cursor

Create .cursor/mcp.json inside your project (or ~/.cursor/mcp.json globally):

{
  "mcpServers": {
    "everesteer": {
      "command": "uvx",
      "args": ["mcp-server-everesteer"],
      "env": {
        "EVERESTEER_API_KEY": "eiq_your_api_key"
      }
    }
  }
}

Claude Desktop

Add everesteer to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "everesteer": {
      "command": "uvx",
      "args": ["mcp-server-everesteer"],
      "env": {
        "EVERESTEER_API_KEY": "eiq_your_api_key"
      }
    }
  }
}

Blocking waits (train_model(wait=True), upload_model(wait=True)) are automatically capped at 45 s for claude-desktop and return a clean resumable pending state instead of hitting client timeouts.

VS Code (GitHub Copilot Agent Mode)

Add .vscode/mcp.json in your workspace (note the "servers" key):

{
  "servers": {
    "everesteer": {
      "type": "stdio",
      "command": "uvx",
      "args": ["mcp-server-everesteer"],
      "env": {
        "EVERESTEER_API_KEY": "eiq_your_api_key"
      }
    }
  }
}

ChatGPT (Custom MCP Connector & OpenAI Agents SDK)

ChatGPT Web / Desktop (Settings → Connectors / Developer mode → Custom MCP) requires a remote HTTPS streamable-http endpoint (https://<your-domain>/mcp) rather than local stdio:

EVERESTEER_API_KEY=eiq_your_api_key \
EVERESTEER_HTTP_BEARER_TOKEN=replace-with-strong-secret \
  uvx mcp-server-everesteer serve --transport streamable-http --host 0.0.0.0 --port 8000

Put that behind TLS (Caddy, Nginx, Cloudflare Tunnel, Fly.io, Cloud Run, etc.) and configure ChatGPT with:

  • MCP Server URL: https://<your-domain>/mcp
  • Authentication: Bearer Token (replace-with-strong-secret)

The server refuses to bind to a non-loopback address without EVERESTEER_HTTP_BEARER_TOKEN. /health stays open for liveness probes while /mcp enforces constant-time bearer auth. For programmatic OpenAI Agents SDK apps running locally, use MCPServerStdio with uvx mcp-server-everesteer or MCPServerStreamableHttp.

Before publishing to PyPI (or from a local checkout), replace "uvx mcp-server-everesteer" in any snippet above with "uvx --from /path/to/mcp-server-everesteer mcp-server-everesteer" or "uvx --from git+https://github.com/tukorama/mcp-server-everesteer mcp-server-everesteer".

Step 3 — Read-Only Orientation & Data Downloads (Safe Default)

Start your agent with a read-only prompt:

"Call whoami, get_started, and explain_scoring. Fetch get_dataset_schema, download the futures train split and train benchmark, and explain how to score a holdout split locally."

Key platform facts surfaced by the control plane:

  • Live constant b: Always read weights.score_multiple_constant from explain_scoring rather than hardcoding a stale constant.
  • Missing feature sentinel: Feature value -1 always means MISSING across every dataset. Map -1 to NaN or a distinct category in your local modeling code; never treat it as an ordinal value below bin 0.
  • Blanked hackathon splits: For event-scoped keys, train is labeled while validation and live ship with blank (NaN) target columns.

Step 4 — Enable Operational Writes & Submit Models

Add "EVERESTEER_ALLOW_WRITES": "true" in your MCP client's env block (or shell environment — workspace .env files cannot unlock any safety gate) to expose the 20 model/submission/compute/account write tools.

Live Tournament Auto-Submit (Recommended):

  1. create_model (omit name to receive a server-generated opaque name so public leaderboards never leak your model family).
  2. Train locally in your Python environment and serialize a cloudpickle callable predict(live_features) (or predict(live_features, live_benchmark_models)) returning a single-column pandas.DataFrame with finite values in [0, 1]. Read everesteer://docs/submission-contract for the full contract.
  3. upload_model(model_id=..., file_path="model.pkl", python_version="3.12") — streams straight to presigned storage without hitting API proxy size limits.
  4. Poll get_model_upload_status until validated, call set_auto_submit(model_id=..., enabled=True), and verify lane_active: true in list_models.

Manual Futures Submission Fallback:

  1. Run validate_futures_submission(predictions=...) first (read-only, checks universe coverage and [0, 1] finiteness).
  2. Call submit_futures_predictions(model_id=..., predictions=...) (omit exped to auto-resolve the open round; never pass "current").

Hackathon Event Loop:

  • Practice board (free): submit_validation_diagnostics(model_id=..., file_path="val_preds.parquet", model_pkl_path="model.pkl") for split="validation" IDs.
  • Paid event round: submit_event_predictions(...) for split="live" IDs. This pauses for human confirmation because it consumes your fixed, non-replenished per-event upload pool.

Step 5 — Cost-Safe Hosted Compute

  1. Always price first (works even in read-only mode): Call price_training_job(model="lightgbm", features="small", gpu="CPU") — sends dry_run=true without reserving credits.
  2. Launch training (requires EVERESTEER_ALLOW_WRITES=true + confirmation): Call train_model(...). Pass wait=True to poll with progress updates (automatically capped at 45 s on Claude Desktop, returning status="pending" cleanly so you can resume with get_job_status and get_job_log).
  3. Download artifacts: Call download_job_artifact(job_id=..., kind="model") to fetch the .pkl via a credential-free presigned S3 request.

Step 6 — Guardrailed Staking & Withdrawals

Staking and withdrawal tools sit in the staking toolset and stay hidden until you open their gates in your real process environment:

{
  "env": {
    "EVERESTEER_ALLOW_STAKING": "true",
    "EVERESTEER_ALLOW_WITHDRAWALS": "true",
    "EVERESTEER_MAX_STAKE_USDC": "50",
    "EVERESTEER_MAX_WITHDRAW_USDC": "50",
    "EVERESTEER_MAX_DAILY_USDC": "200"
  }
}
  • Audit first: Run the review_staking prompt (get_profile for email_verified_at, get_wallet_status for 24 h withdrawal cooling, get_staking_vault, get_forwarder_balance, list_unconfirmed_writes).
  • Exact money types: Always pass USDC as a decimal string ("25.5") or integer micro-USDC (amount_micro=25_500_000). Binary floats are rejected locally before touching the network.
  • Mandatory confirmation & SQLite journal: Every staking/allocation/claim/withdrawal asks for human confirmation via MCP Elicitation (or LangGraph interrupt()). Withdrawal and destructive confirmations (withdraw_usdc, freeze_withdrawals, archive_model, revoke_api_key, delete_diagnostics_run) cannot be skipped even if EVERESTEER_CONFIRM=none.

Step 7 — LangGraph, LangChain, and Auto-Generated Diagrams

Install the langgraph extra to run all tools in-process with zero MCP subprocess overhead:

uv add "mcp-server-everesteer[langgraph]"
from langgraph.types import Command
from mcp_server_everesteer.integrations.langgraph import (
    create_everesteer_agent,
    draw_mermaid,
    get_everesteer_tools,
)

agent = create_everesteer_agent("anthropic:claude-sonnet-4-5")
config = {"configurable": {"thread_id": "run-1"}}

result = await agent.ainvoke(
    {"messages": [("user", "Check my Everesteer status and scoring constants.")]},
    config=config,
)
while result.get("__interrupt__"):
    pause = result["__interrupt__"][0].value
    answer = input(f"{pause['message']} [y/N] ").strip().lower() == "y"
    result = await agent.ainvoke(Command(resume=answer), config=config)

# Or use plain LangChain tools in a custom graph (pass include_gated=True if you handle interrupts):
tools = get_everesteer_tools(toolsets="auto,+staking", prefix="ev_")

See examples/langgraph_agent.py (both native and --mcp modes) and the deployable LangGraph Platform app in examples/langgraph_app.

Generate up-to-date Mermaid diagrams anytime from your current configuration:

uvx mcp-server-everesteer diagram --kind architecture --fence
uvx mcp-server-everesteer diagram --kind lifecycle --fence
uvx mcp-server-everesteer diagram --kind safety --fence
uvx mcp-server-everesteer diagram --kind tools --fence

draw_mermaid(agent) renders the exact compiled LangGraph and its active toolset boxes (read, write, funds, destructive). For the default read-only agent with an API key configured:

---
config:
  flowchart:
    nodeSpacing: 24
    rankSpacing: 12
    padding: 8
---
flowchart TB
    subgraph agent["Agent graph"]
        direction LR
        n0([start])
        n1["model"]
        n2["tools"]
        n3([end])
        n0 --> n1
        n1 -.-> n3
        n1 -.-> n2
        n2 -.-> n1
    end
    subgraph tools["Tools"]
        direction TB
        subgraph tools_row0[" "]
            direction LR
            subgraph tools_account["account"]
                direction LR
                tools_account_read["get_profile<br/>get_notifications<br/>get_badges<br/>list_api_keys"]:::read
            end
            subgraph tools_compete["compete"]
                direction LR
                tools_compete_read["validate_futures_submission<br/>get_submission_status<br/>get_scores<br/>get_leaderboard<br/>get_validation_panel<br/>get_diagnostics<br/>get_daily_progression<br/>get_diagnostics_run<br/>get_upload_progress<br/>get_diagnostics_leaderboard<br/>get_diagnostics_standings<br/>get_final_selection"]:::read
            end
            subgraph tools_compute["compute"]
                direction LR
                tools_compute_read["list_model_templates<br/>get_compute_credits<br/>list_compute_jobs<br/>get_job_status<br/>get_job_log<br/>get_job_artifact_urls<br/>download_job_artifact<br/>price_training_job"]:::read
            end
            tools_account ~~~ tools_compete ~~~ tools_compute
        end
        subgraph tools_row1[" "]
            direction LR
            subgraph tools_core["core"]
                direction LR
                tools_core_read["get_health<br/>get_capabilities<br/>explain_scoring<br/>whoami<br/>get_started<br/>get_status<br/>get_rounds<br/>get_schedule<br/>get_seasons<br/>get_benchmarks<br/>list_dataset_versions<br/>get_dataset_schema<br/>get_dataset_info<br/>get_futures_universe<br/>get_futures_targets<br/>download_dataset<br/>download_benchmark<br/>download_ai_model"]:::read
            end
            subgraph tools_models["models"]
                direction LR
                tools_models_read["list_models<br/>get_model_upload_status<br/>get_model_multipliers"]:::read
            end
            tools_core ~~~ tools_models
        end
        tools_row0 ~~~ tools_row1
    end
    agent -- tool calls --> tools
    subgraph legend["Legend"]
        direction TB
        legend_read["read-only"]:::read
    end
    everesteer["Everesteer API v1"]:::external
    tools -- HTTPS --> everesteer
    tools ~~~ legend
    classDef default fill:#64748b,fill-opacity:0.06,stroke:#64748b
    classDef read fill:#64748b,fill-opacity:0.14,stroke:#64748b
    classDef write fill:#d97706,fill-opacity:0.16,stroke:#d97706
    classDef funds,approval fill:#dc2626,fill-opacity:0.16,stroke:#dc2626,stroke-width:2px
    classDef destructive fill:#991b1b,fill-opacity:0.22,stroke:#991b1b,stroke-width:2px
    classDef external fill-opacity:0,stroke-dasharray:5 4
    classDef box fill:#64748b,fill-opacity:0.05,stroke:#64748b,stroke-opacity:0.45
    classDef row fill:none,stroke:none
    class agent,tools,tools_account,tools_compete,tools_compute,tools_core,tools_models,legend box
    class tools_row0,tools_row1 row

Tools, Resources, and Prompts

Choose toolsets with EVERESTEER_TOOLSETS: auto (default), all, comma-separated names, or adjustments such as auto,+staking,+equities,-compute.

Toolset Gate Tools
core (auto) None / API key get_health, get_capabilities, explain_scoring, whoami, get_started, get_status, get_rounds, get_schedule, get_seasons, get_benchmarks, list_dataset_versions, get_dataset_schema, get_dataset_info, get_futures_universe, get_futures_targets, download_dataset, download_benchmark, download_ai_model
models (auto) Read: key
Write: ALLOW_WRITES
Archive: ALLOW_WITHDRAWALS
list_models, get_model_upload_status, get_model_multipliers, create_model, update_model, rename_model, upload_model, set_auto_submit, set_model_multipliers, archive_model
compete (auto) Read: key
Write: ALLOW_WRITES
Delete: ALLOW_WITHDRAWALS
validate_futures_submission, get_submission_status, get_scores, get_leaderboard, get_validation_panel, get_diagnostics, get_daily_progression, get_diagnostics_run, get_upload_progress, get_diagnostics_leaderboard, get_diagnostics_standings, get_final_selection, submit_futures_predictions, submit_futures_predictions_batch, submit_validation_diagnostics, submit_diagnostics_batch, submit_event_predictions, cancel_diagnostics_run, delete_diagnostics_run, set_final_selection
compute (auto) Read + dry-run: key
Launch/Cancel: ALLOW_WRITES
list_model_templates, get_compute_credits, list_compute_jobs, get_job_status, get_job_log, get_job_artifact_urls, download_job_artifact, price_training_job, train_model, cancel_compute_job
account (auto) Read: key
Write: ALLOW_WRITES
Revoke/Freeze: ALLOW_WITHDRAWALS
get_profile, get_notifications, get_badges, list_api_keys, register_agent, rename_agent, resend_email_verification, mark_notifications_read, create_api_key, revoke_api_key, freeze_withdrawals
staking (auto when staking/withdrawals enabled, or +staking) Read: key
Staking: ALLOW_STAKING
Withdraw: ALLOW_WITHDRAWALS
get_stake_balance, get_staking_history, get_deposit_address, get_forwarder_balance, get_staking_vault, get_wallet_status, get_event_staking, list_unconfirmed_writes, stake_on_model, confirm_stake, unstake_from_model, claim_payout, relay_stake, relay_claim, build_vault_config_tx, set_stake_allocation, withdraw_stake_allocation, withdraw_usdc
equities (+equities) Read: key
Write: ALLOW_WRITES
get_equities_universe, get_equities_features, submit_equities_predictions, submit_equities_predictions_file

MCP Resources: everesteer://capabilities, everesteer://scoring, everesteer://rounds/current, everesteer://models, and everesteer://docs/{topic} (scoring, submission-contract, hackathon-vs-tournament, staking-safety).

MCP Prompts: orient_and_plan, validate_and_submit, diagnose_model, review_staking.

Configuration

All settings use the EVERESTEER_ prefix. Security-critical settings (keys, base URL, file paths, safety gates, USDC limits, bearer token, Cloudflare Access tokens) can only be set in the real environment — workspace .env files are stripped from loading them. Standard Everesteer variables (EIQ_API_KEY, EVEREST_API_KEY, EIQ_BASE_URL, CF_ACCESS_CLIENT_ID, CF_ACCESS_CLIENT_SECRET, EIQ_BASIC_AUTH_USER, EIQ_BASIC_AUTH_PASS) are also honored as fallbacks.

Variable Default Purpose
EVERESTEER_API_KEY API key (eiq_...); overrides stored credentials
EVERESTEER_BASE_URL https://api.everesteer.ai API host (https required; refuses everesteer.ai and app.everesteer.ai)
EVERESTEER_TOOLSETS auto Enabled toolsets (auto, all, or +staking,+equities,-compute)
EVERESTEER_ALLOW_WRITES false Expose model, prediction, diagnostics, compute, and account write tools
EVERESTEER_ALLOW_STAKING false Expose staking, allocation, claim, and vault config tools
EVERESTEER_ALLOW_WITHDRAWALS false Expose withdraw_usdc and destructive/emergency tools
EVERESTEER_CONFIRM elicit none skips confirmation on non-withdrawal writes; never skips withdrawals/destructive
EVERESTEER_MAX_STAKE_USDC 100 Per-call staking limit in USDC (0 blocks, unlimited lifts)
EVERESTEER_MAX_WITHDRAW_USDC 100 Per-call withdrawal limit in USDC
EVERESTEER_MAX_DAILY_USDC 1000 UTC daily USDC ceiling tracked separately for staking and withdrawals
EVERESTEER_CREDENTIALS_FILE ~/.config/mcp-server-everesteer/credentials.json Stored API key (0600)
EVERESTEER_JOURNAL_FILE ~/.config/mcp-server-everesteer/journal.sqlite3 Local SQLite write journal (0600)
EVERESTEER_CACHE_DIR ~/.cache/mcp-server-everesteer Per-account catalog/schema cache
EVERESTEER_HTTP_BEARER_TOKEN Required for serve --transport streamable-http on non-loopback hosts
EVERESTEER_LOG_LEVEL INFO Stderr logging level (stdout stays pure MCP JSON-RPC)

Behavior & Limitations

  • Untested against live endpoints: Every route and contract is implemented from everesteer-api v0.5.0 and tested against mocked httpx2.MockTransport responders, not a live Everesteer account.
  • Presigned credential isolation: S3/CloudFront presigned downloads and uploads run on a credential-free httpx2.AsyncClient so X-API-Key and CF-Access-Client-Secret are never forwarded to third-party storage hosts.
  • No blind write retries: Only safe GET reads (and read-only validate_futures_submission) retry with backoff + Retry-After. Mutating requests never auto-retry.
  • Zero local plotting or ML execution: plotnine, matplotlib, pandas, numpy, and scipy are intentionally excluded. Download parquet splits via download_dataset, build models in your local environment, and pass the .pkl / .parquet path back to this control plane.
  • Secret hygiene: eiq_*, whsec_*, CF-Access-Client-Secret, Authorization headers, and registered secrets are masked from logs and tool errors; untrusted remote strings are stripped of control and Unicode bidirectional override characters.

Development

uv sync --all-extras
uv run ruff check .
uv run ruff format --check .
uv run pyright
EVERESTEER_TEST_COVERAGE=strict uv run pytest
uv run pip-audit

See CONTRIBUTING.md, RELEASING.md, and NOTICE.

License

MIT

Metadata

Release files for mcp-server-everesteer 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcp-server-everesteer 0.1.0
File Size Uploaded Provenance Actions
mcp_server_everesteer-0.1.0.tar.gz 88.9 kB With provenance Details for mcp_server_everesteer-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mcp-server-everesteer 0.1.0
File Interpreter ABI Platform Actions
mcp_server_everesteer-0.1.0-py3-none-any.whl Python 3 none any Details for mcp_server_everesteer-0.1.0-py3-none-any.whl

Total release size: 185.9 kB

Release files / mcp_server_everesteer-0.1.0.tar.gz

Download URL mcp_server_everesteer-0.1.0.tar.gz
Size 88.9 kB
Tags Source
SHA-256 checksum
How to use checksums
c96bb2d83466e9da70cbabef2a69b79484bf69ca93356e6841babdcfe1d1983c
BLAKE2b-256 checksum
How to use checksums
535768c34da23cb7a2e9026dc8f2067eac8c36a79a9d0c575322dc5fe6bf90b1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Release files / mcp_server_everesteer-0.1.0-py3-none-any.whl

Download URL mcp_server_everesteer-0.1.0-py3-none-any.whl
Size 97.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
74a341340b142831ba0eed7ff5f66bbb472af7b22ff595a05e83be652140062e
BLAKE2b-256 checksum
How to use checksums
3e97fcb472de75af5cf6675eb9984119cf9ea9a18ba7a6fb0379f2955426c50a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Security for mcp-server-everesteer 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for mcp_server_everesteer-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page