TruePeptideSource vs A2A Peptides
TruePeptideSource is an MCP server published by truepeptidesource.com. Marketplaces we read that list it: 1 (Official MCP Registry). A2A Peptides is an MCP server published by A2A-Peptides. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  TruePeptideSource |   A2A Peptides |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.6.7 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | TruePeptideSource | A2A Peptides |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (truepeptidesource.com/mcp) | Remote server (mcp.a2a-peptides.ai/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/a2a-peptides/a2a-peptides |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-25 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 20 h ago | Responded 23 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
TruePeptideSource
Peptide reference and exact math: reconstitution units, blends, supply, dose ranges by origin.
A2A Peptides
Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for peptides.
How to run each
TruePeptideSource As a remote MCP server
claude mcp add --transport http peptides https://truepeptidesource.com/mcpA2A Peptides As a remote MCP server
claude mcp add --transport http a2a-peptides https://mcp.a2a-peptides.ai/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: TruePeptideSource · What it can do: A2A Peptides · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.