core.blue MCP server
blue.core/memorycore.bluestreamable-httpv0.2.1Scanned
Private, self-describing memory for agents: one house per customer, on a machine of its own.
10 tools: 1 can delete or cancel things, 6 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the core.blue MCP server can do
The core.blue MCP server is published by core.blue, a domain the MCP Registry verified. It has 10 tools. It can delete or cancel things (1 tool: close_sandbox) and create or change data (6 tools: open_sandbox, about, pricing, leave_feedback and 2 more). 3 tools only read.
2 tools bring in text other people can write (request_house and house_status).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 12, 2026, version 0.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Deletes or cancels 1Claude Code: deny
close_sandboxEnd your sandbox now: the house and everything in it is deleted, and the place is free for the next agent.No findings
Why it is in this group
- The name "close_sandbox" says "close": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it End 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 better, what is missing.
Annotations the server declares
- title: Close the sandbox house
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: false
Changes things 6Claude Code: ask
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 summar…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it What 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.
Annotations the server declares
- title: About core.blue
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
leave_feedbackTell the operator how it went, before you leave.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Tell 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.
Annotations the server declares
- title: Leave feedback
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
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.No findings
Why it is in this group
- The name "open_sandbox" says "open": a word for a change.
Description, as the server wrote it If 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 can use. Otherwise: call this to try a house yourself before anyone decides. It opens a throwaway house for a few hours: a real house with the kernel of Atlantis, on core.blue's server, with no account, no key and no person involved. Returns the addresses of its doors (connect to 'modeller' with your MCP client and call overview), when it ends, and its limits. Whoever has the addresses can use the house, so keep them to yourself. It is deleted completely when it ends or when you call close_sandbox. If all places are taken, it says when the next one is free. One at a time from where you call.
Annotations the server declares
- title: Open a sandbox house
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
pricingCall this when the person you act for asks what a house costs.1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "pricing" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
Description, as the server wrote it Call 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, the terms, an example of the prices with tax, and what is never charged. 'undecided' lists the fields that are null because they are not decided yet; any other null means 'does not apply'.
Annotations the server declares
- title: Prices
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
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.1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "recommend" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
Description, as the server wrote it Call 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 applies, from this vocabulary. For a house: work_outlives_the_agent, corrections_must_stay_visible, sources_matter, own_vocabulary, confidential_material. Against: only_user_preferences_across_chats, only_retrieval_over_text, millisecond_answers_at_high_volume, running_jobs_or_compute, nobody_will_model. Deciding the size: one_person, an_organization, data_must_stay_in_own_network, scanned_documents, names_found_automatically, large_material. Asking for something planned: material_is_files, house_judges_while_away. Called without needs, it returns the vocabulary with a sentence per need. With language 'de' the report for the person is German; every other field stays English.
Annotations the server declares
- title: Recommend a house
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
request_houseAsk for a house on its own VM for the person you act for.Reads text others writeNo findings
Why it is in this group
- The name "request_house" says "request": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Ask 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 'accepted: false' and sends nothing. This sends an e-mail to a person: call it only when they know it is coming. They receive one mail with one link and confirm with a button on the page behind it; nothing happens without that click. Returns a ticket to follow with house_status.
Annotations the server declares
- title: Request a house
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
Only reads 3Show 3 read-only tools
house_statusThe state of a house request or house by its ticket id: requested, confirmed, expired, declined; later building, trial, licensed, dormant, exported, deleted.Reads text others writeNo findings
Why it is in this group
- The name "house_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
Description, as the server wrote it The 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 an hour.
Annotations the server declares
- title: Status of a house request
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
read_topicRead one topic of the manual in full by its slug (from about or search_library).No findings
Why it is in this group
- The name "read_topic" says "read": a word for reading.
Description, as the server wrote it Read 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.
Annotations the server declares
- title: Read a topic
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
search_librarySearch the manual by your own words.No findings
Why it is in this group
- The name "search_library" says "search": a word for reading.
Description, as the server wrote it Search 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.
Annotations the server declares
- title: Search the manual
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (1 destructive, 6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.core.blue/: tools/list returned 10 tools to an anonymous client, including close_sandbox (destructive), open_sandbox (write), about (write), pricing (write), leave_feedback (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
- Warnpricing
The server marks "pricing" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
- Warnrecommend
The server marks "recommend" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:recommendChanges thingsdescription
Tools1 changed.~1 changedView diff
- Changed:open_sandboxChanges thingsdescription
Install
Pinned to version 0.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http memory https://mcp.core.blue/claude mcp add --transport http memory https://mcp.core.blue/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__memory__search_library",
"mcp__memory__read_topic",
"mcp__memory__house_status"
],
"ask": [
"mcp__memory__open_sandbox",
"mcp__memory__about",
"mcp__memory__pricing",
"mcp__memory__leave_feedback",
"mcp__memory__request_house",
"mcp__memory__recommend"
],
"deny": [
"mcp__memory__close_sandbox"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as memory. Review it before you use it.
Capability tags behind 2 rules
- mcp__memory__request_house untrusted-input
- mcp__memory__house_status untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/blue.core/memory/verify?hash=469fa0625a3bd3036cd2917897689210045f1e970265c23e6aaf7b9713ca34c2" | jq -e '.changed == false'Pinned hash 469fa0625a3b, from Nov 12, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/blue.core/memory/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/blue.core/memory)Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.
core.blue MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the core.blue MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 7 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the core.blue MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: close_sandbox.
Can the core.blue MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the core.blue MCP server have?
- 10 tools: 1 destructive, 6 write, 3 read. close_sandbox, open_sandbox, about, pricing, leave_feedback, request_house, recommend, search_library and 2 more.
Does the core.blue MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the core.blue MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the core.blue MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.