Embedfinder

com.embedfinderPublished by embedfinder.comOfficial publisherv1.1.1Updated Nov 4, 2026

Video page links to publish-ready metadata: title, thumbnail, tags and ranked embed players.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP server that turns a video page link into publish-ready metadata: title, thumbnail, tags and ranked embed players.

What you can do
  • Given a video page link, return publish-ready metadata for it.
  • Get a title, thumbnail and tags for the video.
  • Get ranked embed players for the video.
  • No individual tools are listed in the manifest, so exact operations are not documented.
When to use it
Useful when an assistant needs to prepare or enrich video content for publishing, such as drafting titles, tags and thumbnails, or choosing an embed player for a video page link.
Requirements
A remote endpoint at embedfinder.com over streamable HTTP; no local package or runtime. Authentication is required: either an OAuth sign-in or an API key sent in the Authorization header. An Embedfinder account is needed, and a free plan is mentioned.
Before you install
The server requires credentials: an API key in the Authorization header or an OAuth sign-in. The video page links you submit are sent to a third-party service, so avoid sharing private or unlisted URLs you do not want processed externally.

Installation

In SourceWeft

  1. Open Embedfinder in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.embedfinder%2Fembedfinder/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "embedfinder": {
      "type": "http",
      "url": "https://embedfinder.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.1LatestNov 4, 2026
  2. v1.1.0Nov 3, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.