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

saferesize

https://saferesize.com

Registry code: a014548bbb88003e

api record

SafeResize knows the official passport and visa photo rules for 110 documents in 60 countries and regions (checked 28 Sep 2026). Use find_photo_requirements, then get_photo_requirements, when someone asks about photo size, pixels, KB limits or background for a passport, visa or ID application. Use interpret_upload_rules for any website's file upload rules. Each answer names its official source. When the user wants to make the photo or fix the file, the make_it_here or tool_url address opens SafeResize's free tool for it, which runs in the user's browser.

endpoint
https://saferesize.com/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 saferesize live?
Yes — it answered the hub's last check (checked 4h ago). It answered 98% of checks over the last 30 days.
Is saferesize free to use?
Yes — the hub reached it with no key and no payment.
What tools does saferesize have?
4 tools: interpret_upload_rules, check_file_numbers, get_photo_requirements, find_photo_requirements.
Is saferesize 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
97.9%

90 days 98.8%· all time 98.8%

latency
201ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 257 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
government & legal public records & government
used for
  • find passport photo requirements
  • check a photo file against upload rules
  • interpret website upload rules
takes → gives
text, data → data
tools
4 reads
_ 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 4 tools
1 open 3 never probed 1 of 4 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.

  • find_photo_requirements reads open 21h ago

    Search SafeResize's verified list of 110 passport and visa photo documents (60 countries and regions) by country, document or form name, e.g. "US visa", "DS-160", "Schengen", "India OCI", "Dubai". Returns matching documents with their document_id.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Maximum results (default 8)"
    },
    "query": {
      "type": "string",
      "description": "Country, document or form, e.g. \"UK passport\" or \"DS-160\""
    }
  }
}
    arguments 18 lines
  • interpret_upload_rules reads unknown never probed

    Turn the upload rules a website shows (e.g. "JPG only, 10 KB to 50 KB, 200 x 230 pixels" or "PDF not more than 1 MB") into exact numbers: KB limits, a byte range that passes whether the site counts 1 KB as 1,000 or 1,024 bytes, pixels, file type, and the SafeResize tool that fixes the file.

    mcp-tool

    {
  "type": "object",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "The rules exactly as the website writes them"
    }
  }
}
    arguments 12 lines
  • check_file_numbers reads unknown never probed

    Check a file's size in bytes, pixels and type against a website's upload rules, without sending the file. Use when you already know the numbers (e.g. from the file's properties).

    mcp-tool

    {
  "type": "object",
  "required": [
    "rules_text"
  ],
  "properties": {
    "width": {
      "type": "integer"
    },
    "format": {
      "type": "string",
      "description": "jpg, png, webp or pdf"
    },
    "height": {
      "type": "integer"
    },
    "rules_text": {
      "type": "string",
      "description": "The website's rules as written"
    },
    "file_size_bytes": {
      "type": "integer",
      "description": "Exact size in bytes"
    }
  }
}
    arguments 26 lines
  • get_photo_requirements reads unknown 21h ago

    Official photo rules for one document: printed size, pixel rule, file size in KB, file type, background, head size, other rules, whether a self-made photo is accepted, the official source URL and the date SafeResize checked it, plus a link to make the photo free at saferesize.com.

    mcp-tool

    {
  "type": "object",
  "required": [
    "document_id"
  ],
  "properties": {
    "document_id": {
      "type": "string",
      "description": "From find_photo_requirements, e.g. \"us-visa\", \"uk-passport\", \"schengen-visa\", \"in-oci\""
    }
  }
}
    arguments 12 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 a014548bbb88003e.

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

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.