Skip to content

Remove AI Meta MCP server

com.removeaimeta/removeaimetaremoveaimeta.comstreamable-httpv1.0.0Scanned

Inspect and strip EXIF, XMP, IPTC, C2PA, PDF info, and Word properties.

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 2
  • Reads text others write · 2
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Remove AI Meta MCP server can do

The Remove AI Meta MCP server is published by removeaimeta.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: strip_metadata), but cannot delete data. 1 tool only reads.

2 tools read private data (inspect_metadata and strip_metadata); 2 tools bring in text other people can write (inspect_metadata and strip_metadata).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • strip_metadataReturn a cleaned JPEG, PNG, WebP, PDF, or DOCX as base64, plus the fields that were removed.Reads private dataReads text others write1 finding

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe input names a file (input.file_url), and the tool reads: it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "return" and "web": it reads web pages, which anyone can write.

    Findings

    • Warn

      The server marks "strip_metadata" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "return": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • inspect_metadataRead EXIF, XMP, IPTC, C2PA, and AI-generation markers from a JPEG, PNG, or WebP.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "inspect_metadata" says "inspect": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.file_url), and the tool reads: it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://removeaimeta.com/mcp: tools/list returned 2 tools to an anonymous client, including strip_metadata (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "strip_metadata" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "return": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http removeaimeta https://removeaimeta.com/mcp
claude mcp add --transport http removeaimeta https://removeaimeta.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__removeaimeta__inspect_metadata"
    ],
    "ask": [
      "mcp__removeaimeta__strip_metadata"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as removeaimeta. Review it before you use it.

Capability tags behind 2 rules
  • mcp__removeaimeta__inspect_metadata private-data, untrusted-input
  • mcp__removeaimeta__strip_metadata private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.removeaimeta/removeaimeta/verify?hash=317969b9d36ca83ae9640bdba43e6c9b87cce4e041501bf41838e6aa436ce7cd" | jq -e '.changed == false'

Pinned hash 317969b9d36c, from Nov 14, 2026, 05:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.removeaimeta/removeaimeta/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.removeaimeta/removeaimeta
[![Anlyon Radar](https://radar.anlyon.com/badge/com.removeaimeta/removeaimeta.svg)](https://radar.anlyon.com/servers/com.removeaimeta/removeaimeta)

Source: MCP Registry. Synced Oct 21, 2026, 18:01 UTC.

Remove AI Meta MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Remove AI Meta MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Remove AI Meta MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Remove AI Meta MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Remove AI Meta MCP server have?

2 tools: 1 write, 1 read. strip_metadata and inspect_metadata.

Does the Remove AI Meta MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Remove AI Meta MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Remove AI Meta MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.