Skip to content

Anymark MCP server

co.anymark/anymarkanymark.costreamable-httpv1.0.1Scanned

Create logos from templates made by humans (no AI slop)

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • 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 Anymark MCP server can do

The Anymark MCP server is published by anymark.co, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: create_logo_previews and check_logo_name), but cannot delete data. None of its tools only reads.

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

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 9, 2026, version 1.0.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.

2 tools

Changes things 2Claude Code: ask
  • check_logo_nameChecks how a business name will read on a logo and suggests a shorter logo version when the name has a legal ending (Inc, LLC), a web address, a generic company word (Group, Soluti…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
    Checks how a business name will read on a logo and suggests a shorter logo version when the name has a legal ending (Inc, LLC), a web address, a generic company word (Group, Solutions) or a word for what the business sells. The rules come from a study of about 1,000 well-designed brand logos.

    Annotations the server declares

    • title: Check a name for a logo
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • create_logo_previewsShows 6 logo previews for a business, made from Anymark's designer templates with the business name set in each: icon logos picked for the business description, and letter logos bu…1 finding

    Why it is in this group

    • The name "create_logo_previews" says "create": 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 "create_logo_previews" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_logo_previews" says "create": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Shows 6 logo previews for a business, made from Anymark's designer templates with the business name set in each: icon logos picked for the business description, and letter logos built on the name's first letter, each with why it fits. Each preview links to the Anymark editor, where the logo can be customized. Previews are not licensed for use until the logo is bought on Anymark. `page` (1-5) shows further previews for the same business.

    Annotations the server declares

    • title: Create logo previews
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: 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 17, 2026, 15:23 UTC, unchanged since Oct 26, 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
2
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
  • WarnThe whole server

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

    Matched text

    https://anymark.co/mcp: tools/list returned 2 tools to an anonymous client, including create_logo_previews (write), check_logo_name (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "create_logo_previews" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_logo_previews" says "create": a word for a change.

    What this check looks for

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 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http anymark https://anymark.co/mcp
claude mcp add --transport http anymark https://anymark.co/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": [],
    "ask": [
      "mcp__anymark__create_logo_previews",
      "mcp__anymark__check_logo_name"
    ],
    "deny": []
  }
}

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 anymark. 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/co.anymark/anymark/verify?hash=aa481594593a8016bf2a1e0c99f4a6a74569ebf4b3a9b6db522f1841a31ac71f" | jq -e '.changed == false'

Pinned hash aa481594593a, from Nov 9, 2026, 08:18 UTC.

Watch

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

https://radar.anlyon.com/servers/co.anymark/anymark/changes.xml

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

Badge

Anlyon Radar badge for co.anymark/anymark
[![Anlyon Radar](https://radar.anlyon.com/badge/co.anymark/anymark.svg)](https://radar.anlyon.com/servers/co.anymark/anymark)

Source: MCP Registry. Synced Oct 26, 2026, 08:20 UTC.

Anymark MCP server: questions and answers

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

Is the Anymark MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Anymark MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Anymark 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 Anymark MCP server have?

2 tools: 2 write. create_logo_previews and check_logo_name.

Does the Anymark MCP server need sign-in or OAuth?

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

Does the Anymark MCP server send data to outside services?

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

Has the Anymark MCP server changed its tools?

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