_ registry / mcp http-sse · checked 11h ago

morfran

https://api.morfran.com

Registry code: fbf18eb6e7174db6

api record

AI photo effects and face swap: apply effects, swap and detect faces, check credits.

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

endpoint
https://api.morfran.com/mcp
protocol
http-sse ·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 morfran live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is morfran free to use?
Yes — the hub reached it with no key and no payment.
What tools does morfran have?
7 tools: apply_effect, get_face_swap_result, get_effect_task, face_swap, get_credit_balance, detect_faces, list_effects.
Is morfran 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
277ms

last good check

priced tools
0

of 7 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 7 tools
1 open 6 never probed 1 of 7 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.

  • list_effects open 11h ago

    List the available AI photo effects (slug, name, category, description, cover image, credit cost). Free.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • apply_effect unknown never probed

    Apply an AI photo effect to a photo and return the result image URL. Waits up to about 60 seconds. Costs 11 credits (standard) or 29 credits (pro); failed jobs are refunded. The photo must show a real person who agreed to the edit.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug",
        "image_url"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Effect slug from list_effects, e.g. 80s-yearbook"
        },
        "quality": {
          "type": "string",
          "default": "standard",
          "description": "standard or pro"
        },
        "image_url": {
          "type": "string",
          "description": "Public URL of the input photo (JPEG, PNG or WebP)"
        }
      }
    }
    arguments 22 lines
  • get_face_swap_result unknown never probed

    Get the status and result URL of a face swap task.

    mcp-tool

    {
      "type": "object",
      "required": [
        "task_id"
      ],
      "properties": {
        "task_id": {
          "type": "string",
          "description": "TaskId returned by face_swap"
        }
      }
    }
    arguments 12 lines
  • get_effect_task unknown 11h ago

    Get the status and result URL of a photo effect task (for long-running or async jobs).

    mcp-tool

    {
      "type": "object",
      "required": [
        "task_id"
      ],
      "properties": {
        "task_id": {
          "type": "string",
          "description": "task_id returned by apply_effect"
        }
      }
    }
    arguments 12 lines
  • face_swap unknown never probed

    Put the face from the source photo onto the largest face in the target photo and return the result image URL. Costs 5 credits; failed jobs are refunded. Only use photos of people who consented.

    mcp-tool

    {
      "type": "object",
      "required": [
        "source_image_url",
        "target_image_url"
      ],
      "properties": {
        "source_image_url": {
          "type": "string",
          "description": "Public URL of the photo with the face to use"
        },
        "target_image_url": {
          "type": "string",
          "description": "Public URL of the photo to put the face on"
        }
      }
    }
    arguments 17 lines
  • get_credit_balance unknown never probed

    Return the caller's current Morfran credit balance. Free.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • detect_faces unknown 11h ago

    Detect faces in a photo with bounding boxes, age range and gender. Costs 1 credit.

    mcp-tool

    {
      "type": "object",
      "required": [
        "image_url"
      ],
      "properties": {
        "image_url": {
          "type": "string",
          "description": "Public URL of the photo"
        }
      }
    }
    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 fbf18eb6e7174db6.

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

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.