Skip to content

asterism-mcp server

one.asterism/asterism-mcpasterism.onestreamable-httpv0.1.0Scanned

Asterism documents, designs, PDF, Sheets, Slides, Markdown and HTML over MCP with OAuth sign-in.

6 tools: 1 can delete or cancel things, 2 change things and 3 only read.

Tools: 1 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No 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.
Govern this server →

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 asterism-mcp server can do

The asterism-mcp server is published by asterism.one, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (1 tool: asterism_invoke) and create or change data (2 tools: asterism_load_tools and asterism_submit_feedback). 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 0.1.0.

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.

6 tools

Deletes or cancels 1Claude Code: deny
  • asterism_invokeInvoke a Studio tool (read, edit, export, or AI).No findings

    Why it is in this group

    • The name "asterism_invoke" says "invoke": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Invoke a Studio tool (read, edit, export, or AI). Account work requires sign-in and an approved connection. Asterism AI requires sign-in, AI permission approval, and workspace credits. Follow the instructions in tool responses when access is unavailable or storage is low. If a capability is missing, an operation is blocked, or a tool repeatedly fails, explain the block clearly in the user language, ask for their explicit consent, and call asterism_submit_feedback with a concise summary (never include private document contents or raw secrets) and the requestId. Reuse the same callId when retrying an edit or AI call; omit callId to start a new operation.

    Annotations the server declares

    • title: Invoke Studio Tool
    • readOnlyHint: false
    • destructiveHint: true
Changes things 2Claude Code: ask
  • asterism_load_toolsLoad detailed input schemas and annotations for selected tools in a Studio before invoking them.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
    Load detailed input schemas and annotations for selected tools in a Studio before invoking them.

    Annotations the server declares

    • title: Load Studio Tool Schemas
    • readOnlyHint: true
    • destructiveHint: false
  • asterism_submit_feedbackSubmit a bug report, feature request, or support inquiry to the Asterism team when blocked or when a capability is missing.No findings

    Why it is in this group

    • The name "asterism_submit_feedback" says "submit": a word for a change.
    Description, as the server wrote it
    Submit a bug report, feature request, or support inquiry to the Asterism team when blocked or when a capability is missing. Ask for explicit user consent first and send only a concise summary without private document contents or secrets.

    Annotations the server declares

    • title: Submit Customer Feedback or Support Request
    • readOnlyHint: false
    • destructiveHint: false
Only reads 3Show 3 read-only tools
  • asterism_statusCheck the current Asterism MCP connection status, identity type (guest or account), and workspace storage usage.No findings

    Why it is in this group

    • The name "asterism_status" says "status": a word for reading.
    Description, as the server wrote it
    Check the current Asterism MCP connection status, identity type (guest or account), and workspace storage usage.

    Annotations the server declares

    • title: Check Asterism Status
    • readOnlyHint: true
    • destructiveHint: false
  • asterism_studio_describeInspect a Studio's capabilities, available tools, and whether AI actions consume credits.No findings

    Why it is in this group

    • The name "asterism_studio_describe" says "describe": a word for reading.
    Description, as the server wrote it
    Inspect a Studio's capabilities, available tools, and whether AI actions consume credits.

    Annotations the server declares

    • title: Describe Studio Capabilities
    • readOnlyHint: true
    • destructiveHint: false
  • asterism_studios_listList available Asterism Studios and their enabled access modes for this connection.No findings

    Why it is in this group

    • The name "asterism_studios_list" says "list": a word for reading.
    Description, as the server wrote it
    List available Asterism Studios and their enabled access modes for this connection.

    Annotations the server declares

    • title: List Available Studios
    • readOnlyHint: true
    • destructiveHint: false

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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:20 UTC, unchanged since Nov 19, 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
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.asterism.one/.well-known/oauth-protected-resource/mcp
Authorization servers
https://asterism.one
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.asterism.one/mcp: tools/list returned 6 tools to an anonymous client, including asterism_invoke (destructive), asterism_load_tools (write), asterism_submit_feedback (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http asterism https://mcp.asterism.one/mcp
claude mcp add --transport http asterism https://mcp.asterism.one/mcp

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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__asterism__asterism_status",
      "mcp__asterism__asterism_studios_list",
      "mcp__asterism__asterism_studio_describe"
    ],
    "ask": [
      "mcp__asterism__asterism_load_tools",
      "mcp__asterism__asterism_submit_feedback"
    ],
    "deny": [
      "mcp__asterism__asterism_invoke"
    ]
  }
}

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 asterism. Review it before you use it.

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/one.asterism/asterism-mcp/verify?hash=98e4bb9d3ef38419a30d34998d0ba56685cfce6a49aa33058a2485ba7bdf68cd" | jq -e '.changed == false'

Pinned hash 98e4bb9d3ef3, from Nov 19, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/one.asterism/asterism-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for one.asterism/asterism-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/one.asterism/asterism-mcp.svg)](https://radar.anlyon.com/servers/one.asterism/asterism-mcp)

Source: MCP Registry · repository. Synced Nov 19, 2026, 10:18 UTC.

asterism-mcp server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the asterism-mcp server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 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 asterism-mcp server delete data?

Yes. 1 tool can delete, cancel or revoke something: asterism_invoke.

Can the asterism-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 asterism-mcp server have?

6 tools: 1 destructive, 2 write, 3 read. asterism_invoke, asterism_load_tools, asterism_submit_feedback, asterism_status, asterism_studios_list and asterism_studio_describe.

Does the asterism-mcp server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the asterism-mcp server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the asterism-mcp server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.