FindMeTool

com.findmetoolPublished by findmetool.comOfficial publisherv1.0.0Updated Oct 24, 2026

Look up a FindMeTool page URL. Tool input stays in the browser.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant look up a FindMeTool page URL, with tool input staying in the browser.

What you can do
This remote MCP server exposes a lookup capability for FindMeTool page URLs. According to the registry description, an assistant can look up a FindMeTool page URL, and the tool input stays in the browser. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when you need an assistant to resolve or look up FindMeTool page URLs as part of a workflow. Because the manifest lists no tools and no README is available, verify the actual behavior before relying on it.
Requirements
It runs as a remote endpoint at findmetool.com over streamable HTTP. The manifest declares no authentication, no environment variables, and no headers, and no packages are needed locally. Network access to the endpoint is required.
Before you install
The description states that tool input stays in the browser, but no README or tool list is available to confirm what data is sent to the remote service or what the lookup does. Treat the endpoint as third-party and avoid passing sensitive information until its behavior is verified.

Installation

In SourceWeft

  1. Open FindMeTool in the dashboard and add it to a workspace.
  2. 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.findmetool%2Flookup/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.

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

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.