FindMyPart

io.github.jgaethle10Published by GitHub account jgaethle10v1.0.2Updated Oct 24, 2026

Hard-to-source part discovery with replacement, salvage and fabrication paths.

The publisher's own server: Verified Codes

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint, FindMyPart, that helps an assistant find hard-to-source parts and explore replacement, salvage and fabrication options.

What you can do
The listing gives no tool list, so capabilities are known only from its short description. It is presented as a way to discover hard-to-source parts. It points to replacement, salvage and fabrication paths as alternatives when a part is difficult to source. No further functions are documented in the supplied material.
When to use it
Consider it when an assistant needs help locating an obscure or discontinued part and weighing replacement, salvage or fabrication options instead of a direct purchase.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address; no packages, environment variables or headers are declared. The manifest declares no authentication, so no account or key setup is documented.
Before you install
The listing declares no authentication, so anyone reaching the endpoint may use it; avoid sending sensitive information. No tool list is published, so what the server can read or change is unverified. Part sourcing may involve third-party vendors or fabrication services, and any resulting costs or orders should be confirmed by the user.

Installation

In SourceWeft

  1. Open FindMyPart 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/io.github.jgaethle10%2Ffindmypart/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": {
    "findmypart": {
      "type": "http",
      "url": "https://findmypart.base44.app/functions/findMyPartMcp"
    }
  }
}

Tools

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

Version history

2
  1. v1.0.2LatestSep 25, 2026
  2. v1.0.0Sep 24, 2026

Score

67% 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 listedRequired15 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.

  • 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.

Other Find integrations