Other · Remote MCP server
Source Parts
Electronic component sourcing, BOM management, and PCB design workflows.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.SourceParts/parts-mcp- Version
- 0.5.3
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- PyPI
- Published
- 2026-08-16
- Updated
- 2026-08-16
- Publisher
- SourceParts (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/SourceParts) · how
- Website
- source.parts
- Repository
- github.com/SourceParts/parts-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.source.parts/ | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | parts-mcp | 0.5.3 | stdio |
How to connect Source Parts
Source Parts is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.source.parts/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Python package published to PyPI: parts-mcp version 0.5.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx parts-mcp.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"parts-mcp": {
"command": "uvx",
"args": [
"parts-mcp"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| SoundCreation Catalog52,000 musical instruments: prices, deals, bundles, open-box, alternatives, accessories, guides. | Remote · HTTPLive check: ✓ handshake |
| SoundGTMAI-native PRM: track partner pipeline, deals, and commissions, and manage partner outreach. | Remote · HTTPLive check: sign-in required |
| SoundingSounding checks proposed decisions and returns structured proceed, revise, or pause assessments. | Remote · HTTPLive check: sign-in required |
| Source Claim ProofVerify whether a supplied public source currently supports one atomic factual claim. | Remote · HTTPLive check: ✓ handshake |
| SOURCE/80 DiscoveryRead SOURCE/80 continuity status and invite-gated encrypted handoff contracts. | Remote · HTTPLive check: ✓ handshake |
| SourcerightReference verification MCP server for CSL bibliographies, evidence, and audited writes. | Local · stdio |
| SourceyFind and compare startup credits and deals with eligibility checks and exact evidence. | Remote · HTTPLive check: ✓ handshake |
| SourceyStdio bridge to Sourcey startup offers and Agent Readiness report cards. | Local · stdio |