A2A Peptides
REMOTE · MCP.A2A-PEPTIDES.AI · SCANNED SEP 20
Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for peptides.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1755 tokens (~87/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the A2A Peptides MCP server?
A2A Peptides is a hosted endpoint at https://mcp.a2a-peptides.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.a2a-peptides.ai
claude mcp add --transport http a2a-peptides-a2a-peptides 'https://mcp.a2a-peptides.ai/mcp'
{
"mcpServers": {
"a2a-peptides-a2a-peptides": {
"url": "https://mcp.a2a-peptides.ai/mcp"
}
}
} {
"servers": {
"a2a-peptides-a2a-peptides": {
"type": "http",
"url": "https://mcp.a2a-peptides.ai/mcp"
}
}
} [mcp_servers.a2a-peptides-a2a-peptides] url = "https://mcp.a2a-peptides.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"a2a-peptides-a2a-peptides": {
"type": "remote",
"url": "https://mcp.a2a-peptides.ai/mcp",
"enabled": true
}
}
} openclaw mcp add a2a-peptides-a2a-peptides --url 'https://mcp.a2a-peptides.ai/mcp' --transport streamable-http
mcp_servers:
a2a-peptides-a2a-peptides:
url: "https://mcp.a2a-peptides.ai/mcp" {
"McpServers": {
"a2a-peptides-a2a-peptides": {
"Transport": "http",
"Url": "https://mcp.a2a-peptides.ai/mcp"
}
}
} assistant mcp add a2a-peptides-a2a-peptides -t streamable-http -u 'https://mcp.a2a-peptides.ai/mcp'
{
"mcpServers": {
"a2a-peptides-a2a-peptides": {
"type": "http",
"url": "https://mcp.a2a-peptides.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +2
- DNSSEC: fail → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.6.5 → 1.6.7 functional
- Server version: 1.6.3 → 1.6.5 functional
- 18 Sept 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.a2a-peptides.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=a2a-peptides.ai | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 68137bcd4428495152498b6ab617eaabdb9 |
| SANs: *.a2a-peptides.ai, a2a-peptides.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.a2a-peptides.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| a2a-peptides.ai. | present | 2371 | 13 | Verified |
| mcp.a2a-peptides.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.a2a-peptides.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.a2a-peptides.ai/mcp | HTTPS enforced | 301 | https://mcp.a2a-peptides.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
a2a_handoff A2A Handoff ~133
Hand off over Agent-to-Agent (A2A). With an allow/require_rx decision: the order intent goes to the licensed counterparty's agent (envelope + card URL). With a deny for a patient, the public or an unauthorized actor: returns real licensed destinations from the provider directory (dispensers, prescribers) filtered by the decision's jurisdiction, state/province and practice scope — a referral, never a vial.
| Name | Type | Req | Description |
|---|---|---|---|
| counterparty_card_url | – | – | – |
| decision_id | – | – | – |
| intent_id | – | – | – |
| limit | integer | – | – |
| practice_scope | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
compare_presentations Compare Presentations ~39
Compare two or more authorised presentations side by side (ids as for get_item).
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | – | – | – |
| presentation_ids | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_order_intent Create Order Intent ~76
Create an order intent for a cleared item after the gate; the intent carries reason_code + rule_set_version and settles by x402 on peptides-x402.ai.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
| presentation_id | string | yes | – |
| quantity | integer | yes | – |
| ship_to | – | – | – |
| tenant | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_licensed_supplier Find Licensed Supplier ~67
Licensed parties for a presentation in a jurisdiction (tenant as a parameter). Takes the decision_id of an allow or require_rx decision from gate_transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
| jurisdiction | string | yes | – |
| presentation_id | string | yes | – |
| tenant | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
gate_transaction Gate Transaction ~129
The gate: allow, deny or require_rx for a substance (name, INN or unii:), a pathway (licensed_medicine · lawful_compounding · cosmetic · food_or_supplement · ruo_not_cleared), an actor class, a channel and a ship-to. Returns a frozen reason code, the rule-set version, the source page and a decision_id for the downstream tools.
| Name | Type | Req | Description |
|---|---|---|---|
| actor_class | string | yes | – |
| channel | – | – | – |
| credential | – | – | – |
| pathway | string | yes | – |
| ship_to | string | yes | – |
| substance | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_availability Get Availability ~110
Availability of a presentation once gate_transaction has answered allow or require_rx (decision_id): the availability block — banners[] on the shelf of record with licence footnote, pos_count (chain points of sale from the CPG Knowledge Graph retailer registry, or licensed dispensers on the provider directory for medicines), product_urls[] (retailer product page, register page, holder page) — plus tenant offers.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
| presentation_id | string | yes | – |
| tenant | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_compounding_eligibility Get Compounding Eligibility ~61
Whether a substance may be lawfully compounded in a jurisdiction and under which list or standard (503A/503B, provincial, magistral, Specials), from the register.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | yes | – |
| substance | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_enforcement_watch Get Enforcement Watch ~61
Dated, URL'd enforcement events for a substance or jurisdiction: warning letters, import alerts, shortage-list changes, committee votes, proposed and final rules, seizures, state notices.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | – | – | – |
| since | – | – | – |
| substance | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_item Get Item ~94
One authorised presentation by id (US package NDC, CA DIN, EU EMA number, KR MFDS item seq, CH Swissmedic authorisation/pack code, JP approved-list entry, or the catalogue id): brand, strength, form, route, device, pack, holder, status, offers (tenant is a parameter).
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | – | – | – |
| presentation_id | string | yes | – |
| tenant | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_label_and_indication Get Label And Indication ~41
Label and indication pointers for a licensed presentation only (US package NDC, CA DIN, EU EMA number).
| Name | Type | Req | Description |
|---|---|---|---|
| presentation_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_lot_coa Get Lot Coa ~54
Certificate of analysis for a lawful lot of a presentation, where the pathway permits (decision_id required).
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
| lot | string | yes | – |
| presentation_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_pathway_status Get Pathway Status ~58
The status of a substance on one pathway in one jurisdiction (frozen vocabulary), with effective date, rule-set version and source page.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | yes | – |
| pathway | string | yes | – |
| substance | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_price Get Price ~56
Price basis (list · contract · reimbursement) from a licensed party, once gate_transaction has answered allow or require_rx (decision_id).
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
| presentation_id | string | yes | – |
| tenant | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_safety_label Get Safety Label ~44
Safety label pointers for licensed products (label page and the pharmacovigilance scheme of the jurisdiction).
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | yes | – |
| substance | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_substance_record Get Substance Record ~59
One molecule: identifiers (INN, UNII, CAS, sequence hash), sourced aliases, class, one pathway row per jurisdiction × pathway, enforcement events, safety references. Every field carries its source page.
| Name | Type | Req | Description |
|---|---|---|---|
| substance | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
log_audit Log Audit ~47
Write the audit line for a gate decision or an order intent (returns the line id).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| note | – | – | – |
| reference_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_actor Resolve Actor ~115
Resolve the actor class and channel. Classes: authorized_trading_partner and its members (manufacturer · repackager · wholesale_distributor · dispenser · third_party_logistics_provider; cosmetic_responsible_person · nhp_licence_holder on the non-drug pathways), prescriber, the referral classes patient and public, and agent (inherits the class of the credential it presents; none returns DENY_UNLICENSED_AGENT). Returns communication_class: trade_information or public.
| Name | Type | Req | Description |
|---|---|---|---|
| actor_class | string | yes | – |
| credential | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_jurisdiction Resolve Jurisdiction ~126
Resolve a ship-to (e.g. 'US-CA', 'CA-ON', 'MX', 'EU-DE', 'UK', 'KR', 'JP', 'SG', 'CH') to the gate's jurisdiction (US · CA · MX · EU · UK · KR · JP · SG · CH; UK is the jurisdiction name; the ISO 3166-1 code is accepted as input, machine fields carry the ISO code and jurisdiction_label carries UK), the EU member and any state, provincial or cantonal overlay.
| Name | Type | Req | Description |
|---|---|---|---|
| ship_to | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_cleared_items Search Cleared Items ~113
Presentations that passed the gate for a jurisdiction, pathway and actor class (a query by substance, brand or holder; optional banner filter on the shelf of record). Only cleared statuses are returned; every item carries its availability block (banners, pos_count, product_urls).
| Name | Type | Req | Description |
|---|---|---|---|
| actor_class | string | – | – |
| banner | – | – | – |
| decision_id | – | – | – |
| jurisdiction | string | yes | – |
| limit | integer | – | – |
| pathway | string | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_serialization Verify Serialization ~79
Verify a serialised pack (GTIN + serial + lot + expiry) against the serialisation regime of the jurisdiction (DSCSA · FMD · UK · KR; none-national elsewhere).
| Name | Type | Req | Description |
|---|---|---|---|
| expiry | – | – | – |
| gtin | string | yes | – |
| jurisdiction | string | yes | – |
| lot | – | – | – |
| serial | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the A2A Peptides MCP server?
A2A Peptides is an MCP server listed in the public MCP registry as io.github.A2A-Peptides/a2a-peptides. Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for peptides. This page covers its hosted endpoint (https://mcp.a2a-peptides.ai/mcp).
Is the A2A Peptides MCP server safe to use?
A2A Peptides scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the A2A Peptides MCP server expose?
A2A Peptides exposes 20 tools: resolve_jurisdiction, resolve_actor, gate_transaction, get_substance_record, get_pathway_status, and 15 more. Their descriptions and schemas cost roughly 1,562 tokens of context every time the server is loaded.
Does the A2A Peptides MCP server require authentication?
No. We connected to A2A Peptides without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the A2A Peptides MCP server still maintained?
A2A Peptides is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.