_ registry / mcp streamable-http · checked 1h ago

appscreenshoot

https://appscreenshoot.com

Registry code: 92791d54093e6d48

api record

AppScreenshoot provides editable App Store and Google Play screenshot templates and current store screenshot size requirements. Call list_templates to browse the catalog, get_template to inspect one design, and get_screenshot_specs before exporting. This server is read-only and needs no API key. Editing and export happen in the browser at https://appscreenshoot.com/editor. More details: https://appscreenshoot.com/mcp

endpoint
https://appscreenshoot.com/api/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 appscreenshoot live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is appscreenshoot free to use?
Yes — the hub reached it with no key and no payment.
What tools does appscreenshoot have?
3 tools: get_template, get_screenshot_specs, list_templates.
Is appscreenshoot 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
1,027ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 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

_ what it can do 3 tools
2 open 1 never probed 2 of 3 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.

  • get_screenshot_specs open 1h ago

    Look up current App Store and Google Play screenshot requirements: exact pixel sizes, accepted formats, minimum and maximum screenshot counts, transparency rules, and official Apple or Google sources. Filter by store or device type.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "store": {
          "enum": [
            "app-store",
            "google-play"
          ],
          "type": "string",
          "description": "Store to look up. Omit to return both stores."
        },
        "device": {
          "enum": [
            "iphone",
            "ipad",
            "android-phone",
            "android-tablet",
            "chromebook",
            "feature-graphic"
          ],
          "type": "string",
          "description": "Device or asset type to filter by. Omit to return every target."
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • list_templates open 1h ago

    Browse AppScreenshoot's published App Store and Google Play screenshot templates. Filter by category, visual style, free tier, or a keyword. Returns the template slug, name, colors, first preview image, and links to its detail page and editor.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "free": {
          "type": "boolean",
          "description": "When true, only return templates available on the free tier."
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum templates to return. Defaults to 12, capped at 50."
        },
        "query": {
          "type": "string",
          "description": "Keyword to match against each template's name, category, style, or description."
        },
        "style": {
          "type": "string",
          "description": "Partial style match, for example Editorial, Airy, Violet, or Bold."
        },
        "category": {
          "type": "string",
          "description": "Exact category, for example Beauty, Fitness, Finance, or Travel."
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • get_template unknown 1h ago

    Get one AppScreenshoot screenshot template in detail, including its connected screen sequence, headline and subtitle copy, preview images, canvas size, and editor link. Use this after list_templates to inspect or recommend a specific design.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Template slug from list_templates, for example violet-beauty."
        }
      },
      "additionalProperties": false
    }
    arguments 13 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 92791d54093e6d48.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/92791d54093e6d48/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/92791d54093e6d48/badge.svg)](https://brick.blue/agent/92791d54093e6d48?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
70%

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.