MCP servers › io.github.Dosidal › a2a-peptides
MCP server · registry snapshot 2026-11-15 · last tested 2026-11-15
a2a-peptides MCP server
Registry name io.github.Dosidal/a2a-peptides
by Dosidal · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗
Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for peptides. — the publisher's description
Summary
io.github.Dosidal/a2a-peptides is a remote MCP server listed in the official MCP registry at version 1.8.9, under the namespace of the GitHub account Dosidal. Its linked repository, github.com/Dosidal/A2A-Peptides, belongs to the same GitHub account. On 2026-11-15 ProtocolProbe connected to it in read-only mode and read its inventory: 20 tools, 0 resources and 0 prompts.
Record checks
4 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Repository
- public
- Tools
- 20
- Last tested
- 2026-11-15
Tool list size
4,539 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (20 tools). Counted with Anthropic's token counter on 2026-11-15, from the tool list we read on 2026-11-15. Median across 28,560 counted servers: 2,657 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-15 (mcp.peptidal.ai), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.8.9).
Observed fact
This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (create_order_intent). That is our reading of the names; we did not call it. Source: our connection, 2026-11-15.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-15
- Mode
- read-only (no tool calls)
- Latest version
- 1.8.9, published 2026-11-14 (registry, as of the 2026-11-15 snapshot)
- First listed version
- 2026-11-14 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-11-15
- Package and repository
- checked 2026-11-15
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-11-14, listed on 2026-11-15 with version 1.8.9 (published 2026-11-14).
Source: the official MCP Registry list on 2026-11-14 and on 2026-11-15.
What it is
What does this server offer?
Observed inventoryNone of its 20 tools are described as changing anything. For 20 the reading was uncertain, so no mark is shown.
- resolve_jurisdictionon 10 other servers
“Resolve a ship-to (e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
ship_tostringrequired
- resolve_actoron 5 other servers
“Resolve the actor class and channel.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
actor_classstringrequiredcredentialstring or null
- gate_transactionon 5 other servers
“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 chann…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 4 required
substancestringrequiredpathwaystringrequiredactor_classstringrequiredship_tostringrequiredchannelstring or nullcredentialstring or null
- get_substance_recordon 1 other server
“One molecule: identifiers (INN, UNII, CAS, sequence hash), sourced aliases, class, one pathway row per jurisdiction × pathway, enforcement events, safety references.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
substancestringrequired
- get_pathway_statuson 1 other server
“The status of a substance on one pathway in one jurisdiction (frozen vocabulary), with effective date, rule-set version and source page.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 3 required
substancestringrequiredjurisdictionstringrequiredpathwaystringrequired
- get_compounding_eligibilityon 1 other server
“Whether a substance may be lawfully compounded in a jurisdiction and under which list or standard (503A/503B, provincial, magistral, Specials), from the register.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 2 required
substancestringrequiredjurisdictionstringrequired
- get_label_and_indicationon 1 other server
“Label and indication pointers for a licensed presentation only (US package NDC, CA DIN, EU EMA number).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
presentation_idstringrequired
- get_enforcement_watchon 4 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
substancestring or nulljurisdictionstring or nullsincestring or null
- search_cleared_itemson 4 other servers
“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).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs, 2 required
querystringrequiredjurisdictionstringrequiredpathwaystringactor_classstringlimitintegerdecision_idstring or nullbannerstring or null
- get_itemon 62 other servers
“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,…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
presentation_idstringrequiredtenantstring or nulldecision_idstring or null
- compare_presentationson 1 other server
“Compare two or more authorised presentations side by side (ids as for get_item).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
presentation_idsarrayrequireddecision_idstring or null
- find_licensed_supplieron 1 other server
“Licensed parties for a presentation in a jurisdiction (tenant as a parameter).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 3 required
presentation_idstringrequiredjurisdictionstringrequireddecision_idstringrequiredtenantstring or null
Show 8 more tools
- get_availabilityon 89 other servers
“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 …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 2 required
presentation_idstringrequireddecision_idstringrequiredtenantstring or null
- get_priceon 61 other servers
“Price basis (list · contract · reimbursement) from a licensed party, once gate_transaction has answered allow or require_rx (decision_id).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 2 required
presentation_idstringrequireddecision_idstringrequiredtenantstring or null
- get_lot_coaon 1 other server
“Certificate of analysis for a lawful lot of a presentation, where the pathway permits (decision_id required).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 3 required
presentation_idstringrequiredlotstringrequireddecision_idstringrequired
- verify_serializationon 1 other server
“Verify a serialised pack (GTIN + serial + lot + expiry) against the serialisation regime of the jurisdiction (DSCSA · FMD · UK · KR; none-national elsewhere).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 3 required
jurisdictionstringrequiredgtinstringrequiredserialstringrequiredlotstring or nullexpirystring or null
- create_order_intenton 7 other servers
“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.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
5 inputs, 3 required
presentation_idstringrequiredquantityintegerrequireddecision_idstringrequiredtenantstring or nullship_tostring or null
- a2a_handoffon 5 other servers
“Hand off over Agent-to-Agent (A2A).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
5 inputs
intent_idstring or nulldecision_idstring or nullcounterparty_card_urlstring or nullpractice_scopestring or nulllimitinteger
- get_safety_labelon 2 other servers
“Safety label pointers for licensed products (label page and the pharmacovigilance scheme of the jurisdiction).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 2 required
substancestringrequiredjurisdictionstringrequired
- log_auditon 6 other servers
“Write the audit line for a gate decision or an order intent (returns the line id).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 2 required
kindstringrequiredreference_idstringrequirednotestring or null
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-15.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 0% of 64
- Tools with a description
- 100% of 20
- Typical description length
- 215 characters
The tool set
Counted from the listing
- Tools
- 20
- Size of the list
- about 3,616 tokens for an agent to load (characters ÷ 4)
- Naming
- 20 of 20 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 20 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://mcp.peptidal.ai/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"a2a-peptides": {
"url": "https://mcp.peptidal.ai/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"a2a-peptides": {
"type": "http",
"url": "https://mcp.peptidal.ai/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"a2a-peptides","type":"http","url":"https://mcp.peptidal.ai/mcp"}'Claude Code
claude mcp add --transport http a2a-peptides https://mcp.peptidal.ai/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"a2a-peptides": {
"type": "streamableHttp",
"url": "https://mcp.peptidal.ai/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"a2a-peptides": {
"httpUrl": "https://mcp.peptidal.ai/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.a2a-peptides] url = "https://mcp.peptidal.ai/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"a2a-peptides": {
"url": "https://mcp.peptidal.ai/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.peptidal.ai/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-15. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-15. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-15. Source: read 2026-11-15.
- Cline marketplace. Not in the Cline marketplace on 2026-11-15. Source: read 2026-11-15.
Own host
- security.txt. security.txt found at https://mcp.peptidal.ai/.well-known/security.txt (Contact given; expires 2027-09-17). security.txt found at https://mcp.a2a-peptides.ai/.well-known/security.txt (Contact given; expires 2027-09-17). security.txt found at https://peptidal.ai/.well-known/security.txt (Contact given; expires 2027-09-17). Source: mcp.peptidal.ai/.well-known/security.txt · read 2026-11-15.
- A2A agent card. No A2A agent card at https://mcp.peptidal.ai/.well-known/ (HTTP 404, 2026-11-15). No A2A agent card at https://mcp.a2a-peptides.ai/.well-known/ (HTTP 404, 2026-11-15). An A2A agent card is published at https://peptidal.ai/.well-known/agent-card.json (name, skills, url). Source: mcp.peptidal.ai/.well-known/agent-card.json · read 2026-11-15.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint mcp.peptidal.ai/mcp | Session opened | matches | our test · 2026-11-15 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-15 |
| Repository github.com/Dosidal/A2A-Peptides | Opens publicly | matches | api.github.com · 2026-11-15 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.Dosidal · 2 servers
- GitHub owner
- a personal account (Dosidal)
- Repository
- github.com/Dosidal/A2A-Peptides
- Stars
- 0
- Repository age
- 31–90 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-15; security policy read from GitHub · 2026-11-15.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Same tools as other registry entries
Tool lists read · names comparedIts 20 tools have exactly the same names as the tools of 1 other registry entry (published under 2 registry namespaces). Their tool descriptions are also word for word the same.
This can be one publisher's family of servers or one template reused under many names. It is a fact about the published tool lists, not a judgement of the publisher and not a safety finding; we compared tool names, not code.
Shared tool names (12 of 20 shown):
a2a_handoffcompare_presentationscreate_order_intentfind_licensed_suppliergate_transactionget_availabilityget_compounding_eligibilityget_enforcement_watchget_itemget_label_and_indicationget_lot_coaget_pathway_statusThe other entries
All groups of servers with identical tool lists
Source: our read-only reads of each server's tool list · 2026-11-15. No tool was called.
Choosing
Record checks
Public records · not a safety rating4 of 5 record checks met · 4 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-15 (security policy 2026-11-15). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.Dosidal/a2a-peptides
Answered from the data aboveWho publishes io.github.Dosidal/a2a-peptides?
The registry ties the namespace io.github.Dosidal to the GitHub account Dosidal; only its owner can publish under it. Its linked repository, github.com/Dosidal/A2A-Peptides, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.Dosidal/a2a-peptides safe to install?
We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does io.github.Dosidal/a2a-peptides need an API key or sign-in?
It opened a session without any credential on 2026-11-15. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.github.Dosidal/a2a-peptides been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.
Does io.github.Dosidal/a2a-peptides publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Where is the source code of io.github.Dosidal/a2a-peptides?
In github.com/Dosidal/A2A-Peptides, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-11-15, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 2,644 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 20 tools, 0 resources, 0 prompts.
- 6,243 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.Dosidal/a2a-peptides: MCP server record.” Data checked 2026-11-15. https://protocolprobe.com/mcp/servers/io.github.Dosidal/a2a-peptides
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.Dosidal/a2a-peptides)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology