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

unmarking

https://api.unmark.ing

Registry code: 42f80c828e08e7f9

api record

This hosted server only reads files from public URLs. For a file on the user's machine, either install the local server (claude mcp add unmarking -- npx -y unmarking-mcp), which takes paths and writes the cleaned copy next to the original, or upload the file to the HTTP API from a shell: curl -F file=@<path> https://api.unmark.ing/api/strip -o <output>

endpoint
https://api.unmark.ing/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 unmarking live?
Yes — it answered the hub's last check (checked 11h ago). It answered 99% of checks over the last 30 days.
Is unmarking free to use?
Not measured yet.
What tools does unmarking have?
2 tools: inspect_file, strip_file.
Is unmarking 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
98.9%

90 days 98.8%· all time 98.8%

latency
583ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 241 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
documents & files
used for
  • read c2pa credentials from a file
  • remove c2pa credentials from a file
takes → gives
images, video, audio → data, images
tools
2 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 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.

  • inspect_file reads unknown never probed

    Reads the C2PA content credential embedded in a file and reports its signer, including whether the file was made with Claude. Nothing is modified.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri",
      "description": "Publicly reachable http(s) URL of an image, video or audio file. Local paths do not work with this hosted server."
    }
  }
}
    arguments 14 lines
  • strip_file reads unknown never probed

    Removes the C2PA content credential from a file and returns a download link for the cleaned copy. Pixels, frames and samples stay untouched.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri",
      "description": "Publicly reachable http(s) URL of an image, video or audio file. Local paths do not work with this hosted server."
    }
  }
}
    arguments 14 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 42f80c828e08e7f9.

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