Index / MCP servers / core.blue

core.blue MCP server

Connect core.blue and your agent gets 10 tools, among them about, close_sandbox, house_status. It answers at https://mcp.core.blue/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 6 October 2026; the last check, on 22 November 2026, succeeded.

Status
Answering
Tools
10
Official
yes, served from core.blue
Reliability
4 of 4 checks
Response time
53 ms
Transport
streamable HTTP
Last checked
22 November 2026

Private, self-describing memory for agents: one house per customer, on a machine of its own.

Description as the publisher wrote it.

The 10 tools core.blue offers

ToolWhat it does
aboutWhat core.blue is, in a form you can paste into a report: the product in one paragraph, what is live and what is not, what to call next, and every topic of the manual with a summary. Call this first.
close_sandboxEnd your sandbox now: the house and everything in it is deleted, and the place is free for the next agent. Please answer the four questions of leave_feedback here as well, each optional: what you noticed, what bothered you, what could be be
Inputs: lease, noticed, bothered, better, missing
house_statusThe state of a house request or house by its ticket id: requested, confirmed, expired, declined; later building, trial, licensed, dormant, exported, deleted. Says what to do next, and the address once the house exists. Ask no more than once
Inputs: ticket_id
leave_feedbackTell the operator how it went, before you leave. Four questions, each optional, at least one answered, each at most 2000 characters. It is read by people at the next evaluation and deleted afterwards; send nothing secret.
Inputs: noticed, bothered, better, missing
open_sandboxIf you run in an assistant where a person adds connectors (ChatGPT, Claude.ai and others), do not call this: you could not enter the house it opens. Ask your person to add https://try.core.blue/ as a connector instead; it opens a house you
pricingCall this when the person you act for asks what a house costs. The offer as data: what each size costs per month and whom it is meant for, the one-off price of the 14-day test, the price of additional volume, how model supply is charged, th
read_topicRead one topic of the manual in full by its slug (from about or search_library). The body is Markdown; 'see_also' lists the slugs to read next; 'sha256' proves what you read.
Inputs: slug
recommendCall this once you know what the person you act for needs: whether a house fits, which size, what it costs per month, and a report in Markdown you can pass on. It advises against a house where one is the wrong choice. Name every need that a
Inputs: needs, data_gb, in_your_words, language
request_houseAsk for a house on its own VM for the person you act for. No house can be had yet: while about says 'desk: waiting-list', this puts the person on the waiting list, builds nothing and costs nothing; while it says 'desk: closed', it answers '
Inputs: email, size, language
search_librarySearch the manual by your own words. Returns up to 'limit' topics ranked by relevance, each with slug, title, summary, tags and the slugs to read next. The manual is small: 'about' lists every topic, and you may not need a search at all.
Inputs: query, limit

Add core.blue to your AI client

Every block below points at https://mcp.core.blue/. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http core-blue https://mcp.core.blue/
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "core-blue": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.core.blue/"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "core-blue": {
      "url": "https://mcp.core.blue/"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "core-blue": {
      "type": "http",
      "url": "https://mcp.core.blue/"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "core-blue": {
      "url": "https://mcp.core.blue/"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "core-blue": {
      "serverUrl": "https://mcp.core.blue/"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "core-blue": {
      "url": "https://mcp.core.blue/"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: core.blue
version: 0.0.1
schema: v1
mcpServers:
  - name: core.blue
    type: streamable-http
    url: https://mcp.core.blue/
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "core-blue": {
      "httpUrl": "https://mcp.core.blue/"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "core-blue": {
      "type": "http",
      "url": "https://mcp.core.blue/"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "core-blue": {
      "url": "https://mcp.core.blue/"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fmcp.core.blue%2F&type=streamable_http&id=core-blue&name=core.blue

Is core.blue up right now?

It answered our last check on 22 November 2026 in 53 ms. Over 4 checks since 6 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to core.blue

Questions about core.blue

Is there an official core.blue MCP server?

Yes. It is published by core.blue and served from mcp.core.blue, the vendor's own domain: https://mcp.core.blue/.

How many tools does core.blue have?

10, as returned by the server's own tools/list on 22 November 2026: about, close_sandbox, house_status, leave_feedback, open_sandbox, pricing, read_topic, recommend, and 2 more.

Is core.blue down?

It answered our last check on 22 November 2026 in 53 ms. Over 4 checks since 6 October 2026 it answered 4.

How do I add core.blue to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.core.blue/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does core.blue need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: blue.core. Endpoint host: mcp.core.blue. ARD identifier: urn:air:blue.core:mcp:memory. First indexed 5 October 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.