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

Remove AI Meta

https://removeaimeta.com

Registry code: b4873150ce7ddf67

api record

Inspect or strip metadata from a JPEG, PNG, WebP, PDF, or Word DOCX. Pass file_url (public http or https) or file_base64. On an image, mode ai_only leaves camera EXIF and GPS in place. The same checks run in the browser at https://removeaimeta.com/.

endpoint
https://removeaimeta.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 Remove AI Meta live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Remove AI Meta free to use?
Not measured yet.
What tools does Remove AI Meta have?
2 tools: strip_metadata, inspect_metadata.
Is Remove AI Meta 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
507ms

last good check

priced tools
0

of 2 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 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.

  • strip_metadata unknown never probed

    Return a cleaned JPEG, PNG, WebP, PDF, or DOCX as base64, plus the fields that were removed. Image mode ai_only keeps camera EXIF and GPS. Mode all removes them too. PDF and Word files drop document properties in either mode.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "mode": {
      "enum": [
        "ai_only",
        "all"
      ],
      "type": "string",
      "description": "ai_only removes AI-generation and C2PA markers from an image and leaves camera EXIF and GPS. all also removes EXIF, GPS, XMP, and IPTC. PDF and Word files drop document properties in either mode. Default: all."
    },
    "file_url": {
      "type": "string",
      "description": "Public http or https URL of a JPEG, PNG, WebP, PDF, or DOCX file."
    },
    "filename": {
      "type": "string",
      "description": "Original file name, used in the report."
    },
    "file_base64": {
      "type": "string",
      "description": "Base64-encoded file bytes. A data URL is accepted."
    }
  }
}
    arguments 25 lines
  • inspect_metadata unknown 1h ago

    Read EXIF, XMP, IPTC, C2PA, and AI-generation markers from a JPEG, PNG, or WebP. Also reads a PDF info dictionary and XMP, or Word core and app properties. Pass a public file_url or file_base64.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "file_url": {
      "type": "string",
      "description": "Public http or https URL of a JPEG, PNG, WebP, PDF, or DOCX file."
    },
    "filename": {
      "type": "string",
      "description": "Original file name, used in the report."
    },
    "file_base64": {
      "type": "string",
      "description": "Base64-encoded file bytes. A data URL is accepted."
    }
  }
}
    arguments 17 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 b4873150ce7ddf67.

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