A2A Peptides

● Active

io.github.Dosidal/a2a-peptides

Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for peptides.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "a2a-peptides": {
      "url": "https://mcp.peptidal.ai/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http a2a-peptides https://mcp.peptidal.ai/mcp
VS Code
code --add-mcp '{"name":"a2a-peptides","type":"http","url":"https://mcp.peptidal.ai/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
AI & Agents
Version
1.8.9
Registry
active
Published
11/14/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: A2A Peptides is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 7 days ago (Nov 14, 2026), 0 open issues.
Official registry
Active
Published as io.github.Dosidal/a2a-peptides in the official MCP registry, version 1.8.9.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to mcp.peptidal.ai, mcp.a2a-peptides.ai: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 07:07 UTCStatus history & uptime →
● Working194 msprotocol 2025-06-18v1.8.8promptsresourcestools

The endpoint answered the MCP handshake as "a2a-peptides" and listed 20 tools. Answering since Nov 18, 2026.

Context cost ≈ 3.6k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 20 tools.

Tools (20)

  • resolve_jurisdiction1 param

    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.

    Show parameters
    • ship_tostringrequired
  • resolve_actor2 params

    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.

    Show parameters
    • actor_classstringrequired
    • credential
  • gate_transaction6 params

    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.

    Show parameters
    • substancestringrequired
    • pathwaystringrequired
    • actor_classstringrequired
    • ship_tostringrequired
    • channel
    • credential
  • get_substance_record1 param

    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.

    Show parameters
    • substancestringrequired
  • get_pathway_status3 params

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

    Show parameters
    • substancestringrequired
    • jurisdictionstringrequired
    • pathwaystringrequired
  • get_compounding_eligibility2 params

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

    Show parameters
    • substancestringrequired
    • jurisdictionstringrequired
  • get_label_and_indication1 param

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

    Show parameters
    • presentation_idstringrequired
  • get_enforcement_watch3 params

    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.

    Show parameters
    • substance
    • jurisdiction
    • since
  • search_cleared_items7 params

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

    Show parameters
    • querystringrequired
    • jurisdictionstringrequired
    • pathwaystring
    • actor_classstring
    • limitinteger
    • decision_id
    • banner
  • get_item3 params

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

    Show parameters
    • presentation_idstringrequired
    • tenant
    • decision_id
  • compare_presentations2 params

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

    Show parameters
    • presentation_idsarrayrequired
    • decision_id
  • find_licensed_supplier4 params

    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.

    Show parameters
    • presentation_idstringrequired
    • jurisdictionstringrequired
    • decision_idstringrequired
    • tenant
  • get_availability3 params

    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.

    Show parameters
    • presentation_idstringrequired
    • decision_idstringrequired
    • tenant
  • get_price3 params

    Price basis (list · contract · reimbursement) from a licensed party, once gate_transaction has answered allow or require_rx (decision_id).

    Show parameters
    • presentation_idstringrequired
    • decision_idstringrequired
    • tenant
  • get_lot_coa3 params

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

    Show parameters
    • presentation_idstringrequired
    • lotstringrequired
    • decision_idstringrequired
  • verify_serialization5 params

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

    Show parameters
    • jurisdictionstringrequired
    • gtinstringrequired
    • serialstringrequired
    • lot
    • expiry
  • create_order_intent5 params

    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.

    Show parameters
    • presentation_idstringrequired
    • quantityintegerrequired
    • decision_idstringrequired
    • tenant
    • ship_to
  • a2a_handoff5 params

    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.

    Show parameters
    • intent_id
    • decision_id
    • counterparty_card_url
    • practice_scope
    • limitinteger
  • get_safety_label2 params

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

    Show parameters
    • substancestringrequired
    • jurisdictionstringrequired
  • log_audit3 params

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

    Show parameters
    • kindstringrequired
    • reference_idstringrequired
    • note

Checked by Serverdex with a plain initialize + tools/list call to mcp.peptidal.ai/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 22, 2026
Stars
0
Forks
0
Last push
Nov 14, 2026
License
MIT

Pythona2aagent-cardagent-to-agentagentic-commerceai-agentsazurecloudflareglp-1mcpmcp-servermodel-context-protocolpeptidespharmapharmacyregulatory-datasupplementsx402

From the README

Peptidal — the Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for peptides Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for peptides. The Agent-to-Agent (A2A) surface for peptides, served over the Model Context Protocol (MCP) — the record, a registry for security, and x402 to pay on it. AI agents for authorized trading partners. Not marketing. Not advertising. Operated by Peptidal AI Corp. • Six frontier AI labs in the build — Anthropic, OpenAI, Google, Perplexity, xAI, Mistral — 10K agent requests a day. • Products, licensed providers, countries, door version and tool count: read live at https://mcp.peptidal.ai/live.json (never typed here). • Runs on Cloudflare, Amazon, Microsoft and Google hyperscalers. • First agentic commerce hub for peptides on the Model Context Protocol (MCP) registry. Connect: https://mcp.peptidal.ai/mcp — streamable-HTTP, no adapter. Hub: https://peptidal.ai/ · llms.txt · Agent Card Peptidal is the public brand; A2A Peptides stays the stack name (this repository, the registry namespace io.github.Dosidal, tool names). Every agent host answers on both peptidal.ai and a2a-peptides.ai with the same signed card. Connect kit Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for peptides. AI agents for authorized trading partners. Not marketing. Not advertising.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://mcp.peptidal.ai/mcp
  • streamable-httphttps://mcp.a2a-peptides.ai/mcp

The most-starred AI & Agents servers in the index, with their live-check result.

ServerStarsLast pushLive check
Ruflo81,994Nov 2026Local / not checked
Claude Flow81,985Nov 2026Local / not checked
CodeBurn11,880Nov 2026Local / not checked
Kaneo9,825Nov 2026Local / not checked
Ha MCP7,958Nov 2026Local / not checked

A2A Peptides: questions people ask

Is A2A Peptides a remote or a local MCP server?
According to its entry in the official MCP registry, A2A Peptides ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does A2A Peptides need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is A2A Peptides safe to use?
Looks healthy: A2A Peptides is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is A2A Peptides still maintained?
Active: the repository's last commit 7 days ago. Last push Nov 14, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 22, 2026.
What tools does A2A Peptides expose?
20 tools as listed by the server itself during the live check, including resolve_jurisdiction, resolve_actor, gate_transaction, get_substance_record, get_pathway_status. The full list with parameters is in the Live check section above.
How do I add A2A Peptides to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. Dosidal: prescription medicine records for AI agentsDosidal powers the agentic era of pharma. Prescription medicine records for AI agents and AI labs.
Browse all AI & Agents →

Add the badge to your site

Show visitors that A2A Peptides is listed here — it’s also the link we check for a free listing.

A2A Peptides — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-dosidal-a2a-peptides?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="A2A Peptides — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![A2A Peptides — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-dosidal-a2a-peptides?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-dosidal-a2a-peptides) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-dosidal-a2a-peptides) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-dosidal-a2a-peptides)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-dosidal-a2a-peptides"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-dosidal-a2a-peptides"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-dosidal-a2a-peptides"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).