Embedfinder MCP server
com.embedfinder/embedfinderembedfinder.comstreamable-httpv1.1.1Scanned
Video page links to publish-ready metadata: title, thumbnail, tags and ranked embed players.
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 2
- No findings
Sign-in required, OAuth metadata published. 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.
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 Embedfinder MCP server can do
The Embedfinder MCP server is published by embedfinder.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: extract_video_metadata), but cannot delete data. 2 tools only read.
3 tools bring in text other people can write (extract_video_metadata, list_page_entries and get_quota); 2 tools can send data out of your system (extract_video_metadata and list_page_entries).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Nov 3, 2026, version 1.1.1.
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.
3 tools
Changes things 1Claude Code: ask
extract_video_metadataExtract publish-ready metadata from 1 to 8 video or web page URLs: title, description, thumbnail, tags, date, duration and the embeddable player URLs the page publishes, ranked bes…Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Extract publish-ready metadata from 1 to 8 video or web page URLs: title, description, thumbnail, tags, date, duration and the embeddable player URLs the page publishes, ranked best first. Works with YouTube, Vimeo, Dailymotion and any public page with Open Graph, JSON-LD (VideoObject) or WordPress markup. Each URL uses 1 extraction from the account quota. It never downloads or stores videos.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 2Show 2 read-only tools
get_quotaHow many extractions the account has left in the current period (day or month, depending on the plan).Reads text others writeNo findings
Why it is in this group
- The name "get_quota" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it How many extractions the account has left in the current period (day or month, depending on the plan). Free; it does not use quota.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_page_entriesGiven a category, archive, playlist or listing page, return the URLs of the individual entries it links to (in site order) and the next page if there is one.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "list_page_entries" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it Given a category, archive, playlist or listing page, return the URLs of the individual entries it links to (in site order) and the next page if there is one. Pass those URLs to extract_video_metadata. Uses 1 extraction. On the free plan it returns the first 10 entries and the total.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- 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 private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- 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.
Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://embedfinder.com/.well-known/oauth-protected-resource/api/mcp
- RFC 9728 protected resource metadata
- https://embedfinder.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://embedfinder.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
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.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http embedfinder https://embedfinder.com/api/mcpclaude mcp add --transport http embedfinder https://embedfinder.com/api/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__embedfinder__get_quota"
],
"ask": [
"mcp__embedfinder__extract_video_metadata",
"mcp__embedfinder__list_page_entries"
],
"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 embedfinder. Review it before you use it.
Capability tags behind 3 rules
- mcp__embedfinder__extract_video_metadata untrusted-input, outbound
- mcp__embedfinder__list_page_entries untrusted-input, outbound
- mcp__embedfinder__get_quota 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.embedfinder/embedfinder/verify?hash=f3a9dc7b890ef75e790926e6a44581ac9b87ab9653c16e99052b62eba1113240" | jq -e '.changed == false'Pinned hash f3a9dc7b890e, from Nov 3, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.embedfinder/embedfinder/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.embedfinder/embedfinder)Source: MCP Registry. Synced Nov 4, 2026, 12:17 UTC.
Embedfinder MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Embedfinder MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Embedfinder MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Embedfinder 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 Embedfinder MCP server have?
- 3 tools: 1 write, 2 read. extract_video_metadata, list_page_entries and get_quota.
Does the Embedfinder MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the Embedfinder MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): extract_video_metadata and list_page_entries.
Has the Embedfinder MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 3, 2026.