_ registry / mcp streamable-http · checked 7m ago

anymark

https://anymark.co

Registry code: 6a6c7cf04430d4fe

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://anymark.co/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is anymark live?
Yes — it answered the hub's last check (checked 7m ago). It answered 100% of checks over the last 30 days.
Is anymark free to use?
Yes — the hub reached it with no key and no payment.
What tools does anymark have?
2 tools: create_logo_previews, check_logo_name.
Is anymark safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
233ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • create_logo_previews unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "business_name",
        "description"
      ],
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Which page of previews, 1 by default"
        },
        "style": {
          "enum": [
            "classic",
            "modern",
            "playful"
          ],
          "type": "string",
          "description": "Optional look to favor"
        },
        "description": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "What the business does, in a sentence or two"
        },
        "business_name": {
          "type": "string",
          "maxLength": 60,
          "minLength": 1,
          "description": "The name exactly as it should appear on the logo"
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
  • check_logo_name unknown 7m ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "The business name as typed"
        },
        "business_type": {
          "enum": [
            "tech",
            "other"
          ],
          "type": "string",
          "description": "tech for software and tech products, other for everything else"
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6a6c7cf04430d4fe.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6a6c7cf04430d4fe/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6a6c7cf04430d4fe/badge.svg)](https://brick.blue/agent/6a6c7cf04430d4fe?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.