← Registry

General Tools

a2a-peptides.ai

Provides general-purpose tools through the Model Context Protocol.

1 endpoint20 known toolsFirst detected September 18, 2026Last detected September 18, 2026

ENDPOINT 1

https://mcp.a2a-peptides.ai/mcp

No auth detected

MCP server metadata

Name
a2a-peptides
Version
1.4.0
Capabilities
loggingprompts.listChangedresources.listChangedtools.listChanged
Server instructions

Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for peptides. A B2B agentic toolset for the parties authorized to handle those products (GreenCore Solutions Corp.). Call resolve_jurisdiction, then resolve_actor, then gate_transaction before any price, availability, order or handoff tool; those tools refuse without an allow or require_rx decision. Every record field carries its source page. Every response carries notice; every presentation carries bsfrdp_d (Brand, Strength, Form, Route, Device, Pack + disclaimer). Product-level information is trade information for authorized trading partners; the public gets status, class-level information and referral. Research-use stock is not listed and not sold (DENY_RUO). Artificial intelligence makes mistakes. A2A Peptides is an information source, not a recommendation. Rules differ by jurisdiction — refer to the regulator in your jurisdiction for the information that applies to you.

Known tools 20

resolve_jurisdiction

Resolve a ship-to (e.

Inferred read-only
resolve_actor

Resolve the actor class and channel.

Inferred read-only
gate_transaction

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.

Inferred read-only
get_substance_record

One molecule: identifiers (INN, UNII, CAS, sequence hash), sourced aliases, class, one pathway row per jurisdiction × pathway, enforcement events, safety references.

Inferred read-only
get_pathway_status

The status of a substance on one pathway in one jurisdiction (frozen vocabulary), with effective date, rule-set version and source page.

Inferred read-only
get_compounding_eligibility

Whether a substance may be lawfully compounded in a jurisdiction and under which list or standard (503A/503B, provincial, magistral, Specials), from the register.

Inferred read-only
get_label_and_indication

Label and indication pointers for a licensed presentation only (US package NDC, CA DIN, EU EMA number).

Inferred read-only
get_enforcement_watch

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.

Inferred read-only
search_cleared_items

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

Inferred read-only
get_item

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

Inferred read-only
compare_presentations

Compare two or more authorised presentations side by side (ids as for get_item).

Inferred read-only
find_licensed_supplier

Licensed parties for a presentation in a jurisdiction (tenant as a parameter).

Inferred read-only
get_availability

Availability of a presentation after the gate (decision_id required): 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.

Inferred read-only
get_price

Price basis (list · contract · reimbursement) from a licensed party, after the gate (decision_id required).

Inferred read-only
get_lot_coa

Certificate of analysis for a lawful lot of a presentation, where the pathway permits (decision_id required).

Inferred read-only
verify_serialization

Verify a serialised pack (GTIN + serial + lot + expiry) against the serialisation regime of the jurisdiction (DSCSA · FMD · UK · KR; none-national elsewhere).

Inferred read-only
create_order_intent

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.

Potential side effects
a2a_handoff

Hand off over Agent-to-Agent (A2A).

Inferred read-only
get_safety_label

Safety label pointers for licensed products (label page and the pharmacovigilance scheme of the jurisdiction).

Inferred read-only
log_audit

Write the audit line for a gate decision or an order intent (returns the line id).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.a2a-peptides]
url = "https://mcp.a2a-peptides.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "a2a-peptides": {
      "type": "http",
      "url": "https://mcp.a2a-peptides.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: a2a-peptides
Remote MCP URL: https://mcp.a2a-peptides.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "a2a-peptides": {
      "url": "https://mcp.a2a-peptides.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "a2a-peptides": {
      "type": "http",
      "url": "https://mcp.a2a-peptides.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "a2a-peptides",
  "transport": "streamable-http",
  "url": "https://mcp.a2a-peptides.ai/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.