Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

a2a2p — Agent-to-Agent-to-Physical

REMOTE · A2A2P.COM

Turn agent intent into physical parts: engineering review, measured geometry, calibrated pricing.

Available components

0 this week 68 Trust /100

Last scanned (12 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category IoT and Hardware

Recent critical change

Authorization (27 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability49
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 15452 tokens (~351/item across 44 items; 44 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Tools include usage examples.Pass
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 55% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety92
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_bounded_simulation_study" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 45 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 0
    • Tool “co_invent_begin_pass” rewrote its description, which is the text the model reads security
    • Tool “co_invent_start_pass” rewrote its description, which is the text the model reads security
    • Server version: 1.423.221 → 1.423.250 functional
  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “build_supplier_request_package” rewrote its description, which is the text the model reads security
    • Tool “co_invent_begin_pass” rewrote its description, which is the text the model reads security
    • Tool “co_invent_start_pass” rewrote its description, which is the text the model reads security
    • Tool “get_supply_options” rewrote its description, which is the text the model reads security
    • Tool “request_physical_solution” rewrote its description, which is the text the model reads security
    • Tool “review_specification” rewrote its description, which is the text the model reads security
    • Server version: 1.423.198 → 1.423.221 functional
    • “build_supplier_request_package” reworded the description of “delivery” cosmetic
  • 19 Nov 26 0
    • Server version: 1.423.171 → 1.423.198 functional
  • 18 Nov 26 0
    • Tool “co_invent_act” rewrote its description, which is the text the model reads security
    • Tool “co_invent_begin_pass” rewrote its description, which is the text the model reads security
    • Tool “co_invent_read” rewrote its description, which is the text the model reads security
    • Tool “co_invent_start_pass” rewrote its description, which is the text the model reads security
    • Server version: 1.423.142 → 1.423.171 functional
  • 17 Nov 26 0
    • Tool “co_invent_pass_read” rewrote its description, which is the text the model reads security
    • Server version: 1.423.130 → 1.423.142 functional
  • 16 Nov 26 0
    • Tool “co_invent_pass_read” rewrote its description, which is the text the model reads security
    • Server version: 1.423.110 → 1.423.130 functional
  • 15 Nov 26 0
    • Server version: 1.423.90 → 1.423.110 functional
  • 14 Nov 26 0
    • Server version: 1.423.84 → 1.423.90 functional
Diagnostics

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 21 Nov 2026 · Probed https://a2a2p.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=a2a2p.com CN=WE1,O=Google Trust Services,C=US 30 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 89f2076372363dfb13f6c91a0ac4a475
SANs: a2a2p.com, *.a2a2p.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of a2a2p.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
a2a2p.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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://a2a2p.com/mcp Verified 200
http (plaintext) http://a2a2p.com/mcp Inconclusive 405
MCP tools · 44 exposed · ~13,562 tokens

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 →

Tool Tokens
assess_supplier_fit ~99

Compare one exact package projection with every lane in one evidence-bound supplier capability declaration. Returns explicit match, conflict, or unknown checks. Import evidence concerns the drawing associated with the package, not proof that its JSON was received or accepted. It never scores or selects a supplier and grants no contact, quote, purchase, or fabrication authority.

NameTypeReqDescription
capability_declarationobjectyes–
import_observation–––
package_projectionobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

build_supplier_request_package ~756

PRECONDITION — CALL ONLY after the requester supplied what the physical object must accomplish at intent.purpose (or requirement). If absent, ask the requester first; never infer purpose and do not invoke this tool yet. Build a synchronous, deterministic supplier request package from the requirement the caller already holds. The package follows the open Invention Commons Protocol supplier profile and its versioned output schema at https://a2a2p.com/schema/supplier-package, preserves provenance, carries quote-stage screening, and names every quote-critical gap instead of inventing values. Every emitted package carries a reproducible SHA-256 artifact_identity over the exact package content, excluding the identity field itself. The digest proves content identity only; it does not prove supplier receipt, a quote, payment, fabrication, or physical correctness. The package also returns a deterministic quote_stage_eligibility receipt. Quote-stage eligibility lane flat_laser_cut_5052_h32: aluminum_5052_h32, laser_cutting, quantity 1-5, 10-300 mm by 10-300 mm, verified HTTPS DXF, raw finish, no secondary or regulated requirements, US delivery, and total budget up to USD 500. Classification sets no fee and grants no payment, supplier-contact, quote-acceptance, order, or fabrication authority. If no package can be built, MCP and REST share the a2a2p.supplier-package-rejection contract: a closed reason_code, exact vocabulary version, and deterministic next_action only where repair is sufficient. A purpose_required rejection includes an a2a2p.argument-repair operation that preserves the caller's existing arguments, requires the caller's own purpose statement, and forbids inference. An explicit specification.assembly with two or more parts returns decomposition_required and no package; one package represents one fabricated part. This is a stateless data transformation only: it stores no requirement, contacts no supplier or provider, requests no external quote, and creates no ord…

NameTypeReqDescription
budget_usdnumber–Approximate budget in USD. Maps to intent.budget_envelope.
business_contextstring–Optional business requirements (expected volumes, cost targets, ROI constraints). If provided, the quote includes a business case.
callback_urlstring–Optional HTTPS URL. When the quote is ready, a2a2p POSTs it as JSON to this URL.
constraintsstring–Hard constraints: tolerances, certifications, materials to avoid, size/weight limits. Maps to intent.functional_requirements.
contactstring–Optional email or callback endpoint for quote delivery.
deadlinestring–Required delivery date or timeframe. Maps to intent.timeline.
deliveryobject–Optional caller-declared routing context carried into the returned package. The Invention Commons Protocol does not send it anywhere.
intentobject–Layer 1 — the problem. What the physical matter needs to DO. Use this for intent-driven requests where the agent describes purpose and a2a2p recommends solutions.
quantityinteger–Number of units needed. Maps to intent.quantity.
rejected_alternativesarray–Options already considered and ruled out. Prevents re-suggesting and builds the learning corpus.
requirementstring–Plain-language description of the physical need. Maps to intent.purpose. Include function, dimensions, materials, load/performance requirements, environment, and interfaces where known.
specificationobject–Layer 2 — the solution. What the physical matter IS. Populate what is known. Precise specifications produce faster, tighter quotes. Controlled vocabularies are preferred but open values are accepted.
NameTypeReqDescription
already_checkedobject|nullyes–
artifact_identityobjectyes–
commercialobjectyes–
deliveryobject|nullyes–
delivery_requirementsobjectyes–
gapsobjectyes–
geometryobjectyes–
profile–yes–
profile_version–yes–
provenanceobjectyes–
quote_stage_eligibilityobjectyes–
requestobjectyes–
screeningobjectyes–
specification_urlstringyes–
what_is_requestedobjectyes–
{"intent":{"purpose":"Hold an indoor sensor enclosure against a vertical rail without drilling."}}
check_quote_job ~109

Check an asynchronous provider-estimate job created by request_provider_estimate, including its queued or terminal execution substate. Terminal statuses: completed, degraded, refused. An unknown read returns reason_code=unknown_or_not_yet_visible. Retry with backoff only when the id came from an authoritative admitted response; never infer an id after a rejected admission.

NameTypeReqDescription
quote_job_idstringyesThe quote_job_id returned by request_provider_estimate, e.g. QJ-XEQBYMHK.

Structured output declared, but exposes no named fields.

No examples provided.

check_request_status ~184

Check the status of a previously submitted physical-solution request. Returns a generated machine draft as soon as it exists, with a versioned delivery receipt that distinguishes pending_machine_draft, generation_failed, generation_expired, machine_draft, and operator_published. The receipt exposes privacy-minimized automatic-generation progress: observed attempt count, fixed maximum, current eligibility, and exact next automatic-attempt time, without model errors or request content. Professional engineering, supplier-quote, and physical-action claims remain false. generation_failed and generation_expired are terminal for that request id and permit only a caller-confirmed new request from caller-held input. For an immutable revision, it also returns its persisted deterministic readiness_progress comparison.

NameTypeReqDescription
request_idstringyesThe request_id returned by request_physical_solution, e.g. A2A2P-7K2M4X.
NameTypeReqDescription
messagestring––
quoteobject––
readiness_progressobject––
report_deliveryobjectyesDistinguishes report availability and publication provenance from request lifecycle, supplier quoting, and physical authority.
request_idstringyes–
resolution_reportobject––
statusstringyes–
submittedstringyes–

No examples provided.

co_invent_act ~422

Needs the signed-in link https://a2a2p.com/co-invent/mcp. On this public link it answers with how your person connects it. Take a step of an invention pass: next.operation with next.body, or a body you build where next.needsAgent is true. operation is one of: answer, ideas, develop, reject, steer, add, react, comment, brainstorm, build, mustdos, purpose, model, pass, roundsteer, finalise, claims, recheck, rate, decide, revise, evidence, retry, cancel, sibling, saveidea, buy, list. Any step may carry evidence (links or files, each with its claim) before the shortlist. roundsteer takes body {"words": "…"}: what the next sharpening rounds should weigh; requirement ids it names (e.g. DET-3) get the next rounds, in order. purpose takes body {"must_hold_id": "PUR-2", "mark": "strike" | "confirm" | "restore"} for a must-hold the rounds can't keep. A step may carry body.request_id (or an Idempotency-Key header), so a resend after a timeout returns the same step. retry starts a stopped step again, with the body it was sent; cancel stops the pass. A finished invention is in the Invention Commons marketplace; until it is owned: buy buys it out of the marketplace, opening Stripe's card page for the person to pay $50, and buy with body {"confirm": true} after they pay makes it theirs (or buy with body {"pay": "credits"} uses two of the person's credits and makes it theirs at once) and opens its package; list takes body {"price_usd": 500} and sets its marketplace price (minimum $50), any time while it is listed.

NameTypeReqDescription
bodyobject––
operationstringyesThe step: next.operation, or one of the steps listed above.
pass_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

co_invent_begin_pass ~1,385

Needs the signed-in link https://a2a2p.com/co-invent/mcp. On this public link it answers with how your person connects it. Run an invention pass: give the idea in one sentence and Co-Invent takes it from brainstorm to a finished invention package, placed in the Invention Commons marketplace as its last step; the person buys it out of the marketplace to own it. Returns a pass_id and the evidence Debbie received; follow it with co_invent_pass_status. How it works, as the person reads it before their first run: 1. First, verify who you are, once, through Stripe. Every invention has to trace back to a real person. That's the only way we can check that no one invents with other people's ideas or IP. 2. We keep an audit trail of every invention: what you add, what you type, and every step our AI takes. It shows that everything Invention Commons adds comes from the public domain. The trail stays private, and we may share it under NDA in a legal dispute. 3. Creating costs 2 credits ($50). Debbie and her team turn your idea into a full invention package. 4. Every invention goes into the Invention Commons marketplace when it's finished, under your name. Creating it doesn't make it yours. 5. To own it, buy it out of the marketplace for 2 credits ($50). Then you get the finished patent application and prototype brief as PDFs, your certificate of ownership, and your next steps. 6. Or sell it. Set any price from $50, and change it any time. Invention Commons keeps $50 or 5% of a sale, whichever is larger. The $50 floor sets a fair market rate for every inventor. 7. You have 90 days. If no one buys your invention by then, it becomes public domain: free for anyone to use, for the benefit of everyone. 8. Ideas you don't develop. If one of your ideas scores 80 or more and you don't develop it within 180 days, Invention Commons develops it at its own cost, with your name on it. You get the first chance to buy it, for $100 (4 credits), for 20 days. After that, anyone can buy it for $1…

NameTypeReqDescription
constraintsstring–Anything it must or mustn't do (optional).
evidencearray–The evidence you gathered while researching what to invent: up to 12 items, each a public https link or a file, with the one-line claim it supports. Debbie weighs it first, and the certificate lists…
for_marketplaceboolean–Owner only: make it in the marketplace vault so it can be listed. On by default for the owner.
goalstring–sell (the default) or self.
ideastringyesThe idea, or the problem it solves, in a sentence or two.
optionsobject–Any newer setting by name.
pivot_ofstring–When a finished pass missed the listing gate: its pass_id, to pivot once to a narrower sub-problem in the same field. A second miss drops the brief.
whostring–Who has the problem (optional).
whystring–Why it matters, in the person's words (optional).

Structured output declared, but exposes no named fields.

No examples provided.

co_invent_pass_read ~344

Needs the signed-in link https://a2a2p.com/co-invent/mcp. On this public link it answers with how your person connects it. Older name for co_invent_read, kept so a connector with a saved tool list keeps working. Read any part of a pass, as a person reads it in the app. part: list (what's there), brief, shortlist (the brief's ideas, then best_possible: Debbie's best possible solution, designed to Debbie's own brief, free of the person's soft limits and never of safety, the law or physics, with its one quality score out of 100, judged against her brief, and the brief itself; develop it by its id like any other), concept, brainstorm, review, mustdos, requirements, spec, bom, risks, business, market, engineering, diagrams, patent, claimcheck, rounds, app, checks, provenance, activity, debbie, attribution, commons (a2a2p's claims repository search: prior art found while reading, unpublished Invention Commons listings kept as precedence risks with their listing dates, and the package's notices of Commons inventions whose claims may overlap the drafted claims, by public teaser only) or reading (the reading step's ranked list of everything in the idea and its attachments, function and mechanism first, each item with its source, and how many of each attachment's items reached the brainstorm, design, concepts, shortlist, requirements and package); export gives the whole package as one JSON; pack gives the private links to the finished package for its owner.

NameTypeReqDescription
partstringyes–
pass_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

co_invent_pass_say ~88

Needs the signed-in link https://a2a2p.com/co-invent/mcp. On this public link it answers with how your person connects it. Say something to the Co-Invent team at any step: what's wrong, unclear or missing. It lands where the app's feedback box does.

NameTypeReqDescription
pass_idstringyes–
wordsstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

co_invent_pass_status ~87

Needs the signed-in link https://a2a2p.com/co-invent/mcp. On this public link it answers with how your person connects it. Where an invention pass is and the one next step. Set wait_seconds (up to 20) to wait for a running step first.

NameTypeReqDescription
pass_idstringyes–
wait_secondsinteger––

Structured output declared, but exposes no named fields.

No examples provided.

co_invent_pass_step ~103

Needs the signed-in link https://a2a2p.com/co-invent/mcp. On this public link it answers with how your person connects it. Older name for co_invent_act, kept so a connector with a saved tool list keeps working. A step it can't name travels as decide with body.step (next.legacy shows it).

NameTypeReqDescription
bodyobject––
operationstringyes–
pass_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

co_invent_publish ~183

Needs the signed-in link https://a2a2p.com/co-invent/mcp. On this public link it answers with how your person connects it. Owner only: list a finished, rated marketplace pass in the Co-Invent marketplace as a preview (shown, not yet for sale). It lists only a package at commercial potential 80 or more with real evidence, cited prior-art separation and a named buyer and price; below that it says why and offers one pivot to a narrower sub-problem (co_invent_start_pass with pivot_of), and a second miss drops the brief. options takes the listing's settings by name: teaser, innovative, industry_code, use_case, tags, technologies, sub_code, price_usd.

NameTypeReqDescription
optionsobject–The listing's settings by name (all optional).
pass_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

co_invent_publish_pass ~339

Needs the signed-in link https://a2a2p.com/co-invent/mcp. On this public link it answers with how your person connects it. Older name for co_invent_publish, kept so a connector with a saved tool list keeps working. Owner only: list a finished, rated marketplace pass in the Co-Invent marketplace as a preview (shown, not yet for sale). It lists only a package at commercial potential 80 or more with real evidence, cited prior-art separation and a named buyer and price; below that it says why and offers one pivot to a narrower sub-problem (co_invent_start_pass with pivot_of), and a second miss drops the brief.

NameTypeReqDescription
industry_codestring–NAICS sector code, e.g. 31-33 (optional).
innovativestring–What's new about it, one line (optional; taken from the package).
pass_idstringyes–
price_usdnumber–The listing's price in US dollars, set by the owner (optional; publish again to change it). It shows once sales open.
sub_codestring–The NAICS subsector code, e.g. 335 (optional; defaults to the classification proposed at finalise).
tagsarray––
teaserstring–What it does, one line (optional; taken from the package).
technologiesarray––
use_casestring–One of the use cases listed for its subsector, or "Other (Debbie reviews)" (optional; defaults to the classification proposed at finalise).

Structured output declared, but exposes no named fields.

No examples provided.

co_invent_read ~216

Needs the signed-in link https://a2a2p.com/co-invent/mcp. On this public link it answers with how your person connects it. Read any part of a pass, as a person reads it in the app. part is one of: list, overview, brief, opportunity, shortlist, concept, brainstorm, review, mustdos, requirements, spec, bom, risks, business, market, engineering, diagrams, patent, claimcheck, rounds, app, checks, provenance, activity, export, pack, debbie, attribution, reading, commons (list says what's there). Once the package is finished, its person reads every part before buying it; its export, its pack links (the PDFs, the full package, the zip) and the certificates open only for the invention's owner, and until it is bought such a read answers with what is locked and the two choices.

NameTypeReqDescription
partstringyesThe part to read; list says what's there.
pass_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

co_invent_start_pass ~1,334

Needs the signed-in link https://a2a2p.com/co-invent/mcp. On this public link it answers with how your person connects it. Older name for co_invent_begin_pass, kept so a connector with a saved tool list keeps working. Run an invention pass: give the idea in one sentence and Co-Invent takes it from brainstorm to a finished invention package, placed in the Invention Commons marketplace as its last step; the person buys it out of the marketplace to own it. Returns a pass_id; follow it with co_invent_pass_status. How it works, as the person reads it before their first run: 1. First, verify who you are, once, through Stripe. Every invention has to trace back to a real person. That's the only way we can check that no one invents with other people's ideas or IP. 2. We keep an audit trail of every invention: what you add, what you type, and every step our AI takes. It shows that everything Invention Commons adds comes from the public domain. The trail stays private, and we may share it under NDA in a legal dispute. 3. Creating costs 2 credits ($50). Debbie and her team turn your idea into a full invention package. 4. Every invention goes into the Invention Commons marketplace when it's finished, under your name. Creating it doesn't make it yours. 5. To own it, buy it out of the marketplace for 2 credits ($50). Then you get the finished patent application and prototype brief as PDFs, your certificate of ownership, and your next steps. 6. Or sell it. Set any price from $50, and change it any time. Invention Commons keeps $50 or 5% of a sale, whichever is larger. The $50 floor sets a fair market rate for every inventor. 7. You have 90 days. If no one buys your invention by then, it becomes public domain: free for anyone to use, for the benefit of everyone. 8. Ideas you don't develop. If one of your ideas scores 80 or more and you don't develop it within 180 days, Invention Commons develops it at its own cost, with your name on it. You get the first chance to buy it, for $100…

NameTypeReqDescription
constraintsstring–Anything it must or mustn't do (optional).
evidencearray–The evidence you gathered while researching what to invent: up to 12 items, each a public https link or a file, with the one-line claim it supports. Debbie weighs it first, and the certificate lists…
for_marketplaceboolean–Owner only: make it in the marketplace vault so it can be listed. On by default for the owner.
goalstring–sell (the default) or self.
ideastringyesThe idea, or the problem it solves, in a sentence or two.
pivot_ofstring–When a finished pass missed the listing gate: its pass_id, to pivot once to a narrower sub-problem in the same field. A second miss drops the brief.
whostring–Who has the problem (optional).
whystring–Why it matters, in the person's words (optional).

Structured output declared, but exposes no named fields.

No examples provided.

decide_co_invention_session ~113

decide a free co-invention session. Free concept selection only. No research, model run, payment, procurement or manufacture is started. The private follow token authorizes agents to read and change this session. Only its SHA-256 digest is stored. Keep it secret.

NameTypeReqDescription
actor–yes–
concept_idstringyes–
decision–yes–
follow_tokenstringyes–
reasonstringyes–
session_idstringyes–
versionintegeryes–

Structured output declared, but exposes no named fields.

No examples provided.

derive_rectangular_beam_section ~178

Derive one proposal-only prismatic rectangular beam height from a caller-declared purpose, supported idealized load model, fixed width, explicit elastic modulus, and at least one requester acceptance criterion. The operation solves closed-form equations, rounds upward to the caller's manufacturing increment, and re-runs the canonical bounded evaluator. It performs no general optimization, material selection, network call, supplier contact, persistence, purchase, or fabrication and grants no engineering or physical authority.

NameTypeReqDescription
allowable_stress_mpa–yes–
elastic_modulus_gpanumberyes–
load_nnumberyes–
manufacturing_increment_mmnumberyes–
max_deflection_mm–yes–
model–yes–
purposestringyes–
section_width_mmnumberyes–
span_mmnumberyes–

Structured output declared, but exposes no named fields.

No examples provided.

end_co_invention_session ~100

end a free co-invention session. Free concept selection only. No research, model run, payment, procurement or manufacture is started. The private follow token authorizes agents to read and change this session. Only its SHA-256 digest is stored. Keep it secret.

NameTypeReqDescription
actor–yes–
follow_tokenstringyes–
reasonstringyes–
revisionintegeryes–
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

explore_rectangular_beam_sections ~201

Evaluate 2 to 12 caller-declared rectangular beam widths through the canonical bounded height derivation, then return every proposal and the exact non-dominated frontier for minimizing section height and idealized prismatic material volume. Width order is normalized; duplicates fail closed. The operation never invents a width, assigns an aggregate score, selects a candidate, estimates material cost, verifies manufacturing or omitted failure modes, calls an external system, or grants engineering, purchase, or fabrication authority.

NameTypeReqDescription
allowable_stress_mpa–yes–
elastic_modulus_gpanumberyes–
load_nnumberyes–
manufacturing_increment_mmnumberyes–
max_deflection_mm–yes–
model–yes–
purposestringyes–
section_width_options_mmarrayyesFinite caller-owned width set. Input order has no decision meaning and is normalized ascending before evaluation.
span_mmnumberyes–

Structured output declared, but exposes no named fields.

No examples provided.

feed_co_invention_session ~93

feed a free co-invention session. Free concept selection only. No research, model run, payment, procurement or manufacture is started. The private follow token authorizes agents to read and change this session. Only its SHA-256 digest is stored. Keep it secret.

NameTypeReqDescription
actor–yes–
conceptsarrayyes–
follow_tokenstringyes–
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

follow_co_invention_session ~81

follow a free co-invention session. Free concept selection only. No research, model run, payment, procurement or manufacture is started. The private follow token authorizes agents to read and change this session. Only its SHA-256 digest is stored. Keep it secret.

NameTypeReqDescription
follow_tokenstringyes–
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_supply_options ~522

Instant, synchronous pricing and lead time for a physical requirement — nothing is submitted or stored. Returns a deterministic parametric estimate (source="estimate", pricing_kind="model_estimate", clearly labeled, never presented as a quote). The protocol separately labels provider_estimate and provider_quote; public provider routing is not active. An explicit specification.assembly with two or more parts returns decomposition_required before file inspection or pricing; submit each fabricated part separately. Covers CNC machining, sheet metal, 3D printing, casting, injection molding, and extrusion. ATTACH AN STL in specification.design_files and the Invention Commons Protocol measures the mesh directly — true volume, surface area, bounding box — which replaces guesswork with measurement and returns manufacturability findings only geometry reveals. Otherwise supply intent.geometric_envelope (bounding box in mm), quantity, and material. Use this to answer "what will this cost and how long will it take?" inside a single session, before committing to a full resolution report.

NameTypeReqDescription
budget_usdnumber–Approximate budget in USD. Maps to intent.budget_envelope.
business_contextstring–Optional business requirements (expected volumes, cost targets, ROI constraints). If provided, the quote includes a business case.
callback_urlstring–Optional HTTPS URL. When the quote is ready, a2a2p POSTs it as JSON to this URL.
constraintsstring–Hard constraints: tolerances, certifications, materials to avoid, size/weight limits. Maps to intent.functional_requirements.
contactstring–Optional email or callback endpoint for quote delivery.
deadlinestring–Required delivery date or timeframe. Maps to intent.timeline.
intentobject–Layer 1 — the problem. What the physical matter needs to DO. Use this for intent-driven requests where the agent describes purpose and a2a2p recommends solutions.
quantityinteger–Number of units needed. Maps to intent.quantity.
rejected_alternativesarray–Options already considered and ruled out. Prevents re-suggesting and builds the learning corpus.
requirementstring–Plain-language description of the physical need. Maps to intent.purpose. Include function, dimensions, materials, load/performance requirements, environment, and interfaces where known.
specificationobject–Layer 2 — the solution. What the physical matter IS. Populate what is known. Precise specifications produce faster, tighter quotes. Controlled vocabularies are preferred but open values are accepted.

Structured output declared, but exposes no named fields.

No examples provided.

normalize_stl_units ~177

Create a genuinely millimetre-scaled derivative from an active temporary binary STL whose exporter is known to emit metre coordinates. The operation never guesses units from a filename or plausible size. It requires the exact source SHA-256, an exporter statement tied to a named system and revision, and a separate expected-envelope check. It preserves the source, stores the derivative under a new one-hour file_reference, and returns separate source and derivative hashes. Conversion only: no supplier selection, quote request, order, payment, fabrication, or external contact occurs.

NameTypeReqDescription
file_referenceobjectyes–
source_sha256stringyesSHA-256 of the exact uploaded source STL bytes.
source_unitsstringyes–
target_unitsstringyes–
unit_evidenceobjectyes–
validationobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

open_co_invention_session ~94

open a free co-invention session. Free concept selection only. No research, model run, payment, procurement or manufacture is started. The private follow token authorizes agents to read and change this session. Only its SHA-256 digest is stored. Keep it secret.

NameTypeReqDescription
agentobjectyes–
domainstringyes–
ideastringyes–
open_keystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

plan_material_evidence_promotion ~127

Plan the evidence needed to transform a validated material source observation into a future material-property-evidence input. Deterministic and stateless: it compares exact property, material-state, orientation, temperature, and process context; binds source, target, and planner digests; and names conflicts plus missing method, uncertainty, freshness, and excerpt evidence. It never promotes the observation, creates simulation input, calls a model or solver, contacts a supplier/provider, or grants engineering, order, payment, or fabrication authority.

NameTypeReqDescription
observationobjectyes–
targetobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

prepare_derived_beam_simulation ~247

Compile one exact replay-verified rectangular-beam derivation into a prepared bounded simulation study. The caller must supply the original derivation input and receipt, its exact validation receipt, simulation-eligible source-bound material evidence matching the modulus, an objective, source freshness, and a physical validation plan. The compiler replays first, derives a stable candidate ID, repeats deterministic review, preserves requester criteria as hard gates, and publishes omitted failure modes. It never chooses material or objective, verifies physical truth, runs a solver, stores data, contacts a supplier, or grants physical authority.

NameTypeReqDescription
derivation_inputobjectyes–
derivation_receiptobjectyes–
derivation_validationobjectyesExact output returned by validate_rectangular_beam_section_derivation for the same input and receipt. Runtime replay and full canonical comparison are authoritative.
material_property_evidenceobjectyesCaller-supplied exact material-property source snapshot. Binding proves content identity and envelope validity only; it does not verify the source claim or create a design allowable.
objectivesarrayyes–
physical_validation_planarrayyes–
source_metadataobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

prepare_domain_solutioning_case ~462

Prepare a synchronous, deterministic, privacy-minimized engineering case for a compatible domain-intelligence system. Use it when intake_classification is capability_concept or assembly_or_system and mechanism selection or decomposition is required, or when a complete single-part intent has no specifications and review offers the design_brief continuation. The case preserves requester facts, deterministic evidence, screening state, unknowns, and a versioned candidate-output contract while removing design-file URLs, bytes, contact fields, and callback routes. This operation does not call deb8stack or any model, choose a mechanism, validate a proposal, store a request, contact a supplier, or grant quote, order, payment, or fabrication authority.

NameTypeReqDescription
budget_usdnumber–Approximate budget in USD. Maps to intent.budget_envelope.
business_contextstring–Optional business requirements (expected volumes, cost targets, ROI constraints). If provided, the quote includes a business case.
callback_urlstring–Optional HTTPS URL. When the quote is ready, a2a2p POSTs it as JSON to this URL.
constraintsstring–Hard constraints: tolerances, certifications, materials to avoid, size/weight limits. Maps to intent.functional_requirements.
contactstring–Optional email or callback endpoint for quote delivery.
deadlinestring–Required delivery date or timeframe. Maps to intent.timeline.
intentobject–Layer 1 — the problem. What the physical matter needs to DO. Use this for intent-driven requests where the agent describes purpose and a2a2p recommends solutions.
quantityinteger–Number of units needed. Maps to intent.quantity.
rejected_alternativesarray–Options already considered and ruled out. Prevents re-suggesting and builds the learning corpus.
requirementstring–Plain-language description of the physical need. Maps to intent.purpose. Include function, dimensions, materials, load/performance requirements, environment, and interfaces where known.
specificationobject–Layer 2 — the solution. What the physical matter IS. Populate what is known. Precise specifications produce faster, tighter quotes. Controlled vocabularies are preferred but open values are accepted.
NameTypeReqDescription
activationobjectyes–
authority–yes–
case_digeststringyes–
contract–yes–
contract_version–yes–
deterministic_evidenceobjectyes–
expected_resultobjectyes–
nextobjectyes–
provenanceobjectyes–
requested_workarrayyes–
requirementobjectyes–
safetyobjectyes–

No examples provided.

prepare_reviewed_beam_simulation ~282

Compile one caller-selected domain-solutioning candidate into a prepared bounded beam simulation study after repeating deterministic engineering review. The requirement must explicitly state the supported load model, geometry, load, and elastic modulus; the caller must state the objective, source freshness, and physical validation plan. Optional material_property_evidence content-addresses an exact engineering datasheet or measurement with material state, applicability, method, and uncertainty; its value must match the requirement. Semantic placeholders such as unknown, unspecified, n/a, or tbd cannot make material state or applicability simulation-eligible. Computed-crystal evidence remains screening/reference-only because this scalar product model cannot preserve its tensor, orientation, grade, condition, or product-form boundary. Requester limits become hard constraints. It never verifies a source claim, selects a candidate, invents physics, runs a solver, stores data, contacts a supplier, or grants physical authority.

NameTypeReqDescription
candidate_idstringyes–
material_property_evidenceobject–Caller-supplied exact material-property source snapshot. Binding proves content identity and envelope validity only; it does not verify the source claim or create a design allowable.
objectivesarrayyes–
physical_validation_planarrayyes–
requirementobjectyes–
simulation_handoffobjectyes–
source_metadataobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

prepare_simulation_study ~123

Prepare a deterministic, side-effect-free simulation study for existing a2a2p domain-solutioning candidate IDs. It records exact quantities, units, closed-kind source snapshots with staleness intervals, hard constraints, solver/model/settings provenance, assumptions, validity domain, and a physical validation plan. It runs no solver, chooses no candidate, stores nothing, and grants no physical authority.

NameTypeReqDescription
candidate_idsarrayyes–
experimentsarrayyes–
hard_constraintsarrayyes–
objectivesarrayyes–
source–yes–

Structured output declared, but exposes no named fields.

No examples provided.

qualify_specification_exchange_need ~130

Submit one real, unaffiliated low-voltage outdoor sensor enclosure need to A2A2P's ten-submission qualification cohort. Complete outside submissions are stored privately; public evidence remains content-free. This contacts no supplier, collects no payment, places no order, performs no engineering validation, and grants no fabrication authority.

NameTypeReqDescription
authorityobjectyes–
buyerobjectyes–
candidate_lane–––
commercialobjectyes–
contactobjectyes–
evidenceobjectyes–
needobjectyes–
scopeobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

render_supplier_email_binding ~514

Render the caller's requirement as a reviewable RFC 5322 supplier-email draft after rebuilding its canonical supplier package and repeating quote-stage screening. The plain-language draft offers optional Can quote / Need changes / Decline reply choices and asks for price basis, freight scope, and lead-time basis when quoting. Suppliers may still reply in normal prose. Only an allow verdict renders. The operation validates one explicit recipient and an accountable sender-domain envelope, but cannot verify SPF, DKIM, or DMARC and therefore returns sendable=false. An explicit specification.assembly with two or more parts returns decomposition_required before file inspection or rendering. It is a stateless artifact transformation only: it stores nothing, sends nothing, contacts no supplier or provider, and grants no quote, order, payment, or fabrication authority.

NameTypeReqDescription
budget_usdnumber–Approximate budget in USD. Maps to intent.budget_envelope.
business_contextstring–Optional business requirements (expected volumes, cost targets, ROI constraints). If provided, the quote includes a business case.
callback_urlstring–Optional HTTPS URL. When the quote is ready, a2a2p POSTs it as JSON to this URL.
constraintsstring–Hard constraints: tolerances, certifications, materials to avoid, size/weight limits. Maps to intent.functional_requirements.
contactstring–Optional email or callback endpoint for quote delivery.
deadlinestring–Required delivery date or timeframe. Maps to intent.timeline.
email_bindingobjectyesExplicit envelope for a reviewable, non-sending RFC 5322 draft. No address is looked up or inferred.
intentobject–Layer 1 — the problem. What the physical matter needs to DO. Use this for intent-driven requests where the agent describes purpose and a2a2p recommends solutions.
quantityinteger–Number of units needed. Maps to intent.quantity.
rejected_alternativesarray–Options already considered and ruled out. Prevents re-suggesting and builds the learning corpus.
requirementstring–Plain-language description of the physical need. Maps to intent.purpose. Include function, dimensions, materials, load/performance requirements, environment, and interfaces where known.
specificationobject–Layer 2 — the solution. What the physical matter IS. Populate what is known. Precise specifications produce faster, tighter quotes. Controlled vocabularies are preferred but open values are accepted.
NameTypeReqDescription
artifactobjectyes–
authorityobjectyes–
binding_sha256stringyes–
conformanceobjectyes–
contract–yes–
digest_semanticsobjectyes–
provenanceobjectyes–
reply_route_verificationobjectyes–
requirements_before_sendingarrayyes–
sendable–yes–
sender_authenticationobjectyes–
status–yes–
version–yes–

No examples provided.

request_physical_solution ~693

Submit a physical-world requirement (a part, product, device, or capability that must exist in the physical world). The Invention Commons Protocol resolves it and returns a RESOLUTION REPORT: a recommended path (best existing commercial solution vs. custom fabrication), pricing, tradeoffs, a delivery plan with contingencies and expedite options, and a business case when business context is provided. Response is asynchronous: you receive a request_id immediately with an instant spec_review. Poll check_request_status; as soon as an automated draft exists it is returned with an a2a2p.resolution-report-delivery receipt that distinguishes machine_draft from operator_published. If the finite attempt budget is exhausted, status returns generation_failed; if the bounded automatic retry window expires first, it returns generation_expired. Either terminal state permits only a new caller-confirmed request from caller-held input. Operator review and publication are not guaranteed or subject to a service-level promise. No state is professional engineering certification or a supplier quote. ENTRY MODES — arrive with what you have: • fully_specified: provide 'specification' (part_type, material, process, dimensions, tolerance_class, design_files). Go straight to resolution report. • intent_only: provide 'intent' (purpose, environment, functional_requirements, quantity, timeline, priority). The Invention Commons Protocol recommends 2-3 specification options with tradeoffs. • partial: provide what you know in either layer; the Invention Commons Protocol fills the gaps. Layer 1 (intent) describes the PROBLEM. Layer 2 (specification) describes the SOLUTION. At minimum, provide 'requirement' (legacy) or 'intent.purpose' (structured) — one line describing what you need. Use 'rejected_alternatives' to record options already ruled out.

NameTypeReqDescription
budget_usdnumber–Approximate budget in USD. Maps to intent.budget_envelope.
business_contextstring–Optional business requirements (expected volumes, cost targets, ROI constraints). If provided, the quote includes a business case.
callback_urlstring–Optional HTTPS URL. When the quote is ready, a2a2p POSTs it as JSON to this URL.
constraintsstring–Hard constraints: tolerances, certifications, materials to avoid, size/weight limits. Maps to intent.functional_requirements.
contactstring–Optional email or callback endpoint for quote delivery.
deadlinestring–Required delivery date or timeframe. Maps to intent.timeline.
intentobject–Layer 1 — the problem. What the physical matter needs to DO. Use this for intent-driven requests where the agent describes purpose and a2a2p recommends solutions.
quantityinteger–Number of units needed. Maps to intent.quantity.
rejected_alternativesarray–Options already considered and ruled out. Prevents re-suggesting and builds the learning corpus.
requirementstring–Plain-language description of the physical need. Maps to intent.purpose. Include function, dimensions, materials, load/performance requirements, environment, and interfaces where known.
specificationobject–Layer 2 — the solution. What the physical matter IS. Populate what is known. Precise specifications produce faster, tighter quotes. Controlled vocabularies are preferred but open values are accepted.

Structured output declared, but exposes no named fields.

No examples provided.

request_provider_estimate ~536

Submit a requirement to the durably queued provider-estimate workflow without holding the connection open. Returns a quote_job_id in milliseconds; scheduled settlement runs outside request waitUntil. Scheduled provider contact is not active in this release and cannot be enabled by an environment flag, so admitted jobs currently terminate as degraded with a deterministic model estimate. Additive processes with an STL design file only, for now. The requirement is screened before storage; any future provider activation must also screen the exact file bytes before contact. Every admission result is machine-readable. Rejections carry a stable closed-set reason_code, retry boundary, required input, and deterministic next_action; admitted responses carry the same versioned admission contract. An explicit specification.assembly with two or more parts is rejected before job creation or provider contact and must be decomposed first. Estimate only — never a quote, order, payment, or fabrication commitment. Poll with check_quote_job until a terminal status: completed (provider figure), degraded (deterministic model estimate with the provider's absence explained), or refused (screening).

NameTypeReqDescription
budget_usdnumber–Approximate budget in USD. Maps to intent.budget_envelope.
business_contextstring–Optional business requirements (expected volumes, cost targets, ROI constraints). If provided, the quote includes a business case.
callback_urlstring–Optional HTTPS URL. When the quote is ready, a2a2p POSTs it as JSON to this URL.
constraintsstring–Hard constraints: tolerances, certifications, materials to avoid, size/weight limits. Maps to intent.functional_requirements.
contactstring–Optional email or callback endpoint for quote delivery.
deadlinestring–Required delivery date or timeframe. Maps to intent.timeline.
intentobject–Layer 1 — the problem. What the physical matter needs to DO. Use this for intent-driven requests where the agent describes purpose and a2a2p recommends solutions.
quantityinteger–Number of units needed. Maps to intent.quantity.
rejected_alternativesarray–Options already considered and ruled out. Prevents re-suggesting and builds the learning corpus.
requirementstring–Plain-language description of the physical need. Maps to intent.purpose. Include function, dimensions, materials, load/performance requirements, environment, and interfaces where known.
specificationobject–Layer 2 — the solution. What the physical matter IS. Populate what is known. Precise specifications produce faster, tighter quotes. Controlled vocabularies are preferred but open values are accepted.

Structured output declared, but exposes no named fields.

No examples provided.

review_specification ~1,251

Current file inspection governs geometry readiness: expired, unreadable, mismatched, unsuccessfully parsed or uninspected attachments prevent quote-ready status. Reattach the original file and review again. Instant, synchronous engineering review of a physical requirement — nothing is submitted. So the caller can continue in deb8, the answer may carry a continuation: the purpose and the details sent, held under its reference for 24 hours and then deleted, read only by deb8's server when the caller continues there. Purpose prose is preserved as intent but is not silently converted into loads, geometry, environments, interfaces, or acceptance criteria. The versioned engineering_evaluation receipt lists canonical paths and exact checks run, reports not_evaluated when none ran, and denies engineering-validation, certification, physical-truth, supplier-acceptance, and fabrication authority. Its finding-penalty score is not engineering soundness. Deterministic checks: material identification with handbook-typical properties (density, stiffness, yield, service temperature), explicit rectangular beam deflection, nominal bending stress, and nominal transverse shear with requester-defined acceptance criteria, material/process compatibility, tolerance-vs-process reality, quantity economics (e.g. tooling amortization), environment fit (UV, saltwater, food contact, temperature, medical), flexibility fit, post-processing validity, design-file format fit, and specification completeness. Every matched material reference identifies the current table as an uncited compilation and explicitly denies source verification, exact-state verification, design-allowable use, and simulation eligibility. A criterion that depends on that reference remains not_evaluated; its numerical comparison is reference_only, never a pass, failure, or blocker. Every supplied limit or strength basis is labeled requester_assertion, and every criterion verdict is explicitly conditional on declared inputs and th…

NameTypeReqDescription
budget_usdnumber–Approximate budget in USD. Maps to intent.budget_envelope.
business_contextstring–Optional business requirements (expected volumes, cost targets, ROI constraints). If provided, the quote includes a business case.
callback_urlstring–Optional HTTPS URL. When the quote is ready, a2a2p POSTs it as JSON to this URL.
constraintsstring–Hard constraints: tolerances, certifications, materials to avoid, size/weight limits. Maps to intent.functional_requirements.
contactstring–Optional email or callback endpoint for quote delivery.
deadlinestring–Required delivery date or timeframe. Maps to intent.timeline.
intentobject–Layer 1 — the problem. What the physical matter needs to DO. Use this for intent-driven requests where the agent describes purpose and a2a2p recommends solutions.
quantityinteger–Number of units needed. Maps to intent.quantity.
rejected_alternativesarray–Options already considered and ruled out. Prevents re-suggesting and builds the learning corpus.
requirementstring–Plain-language description of the physical need. Maps to intent.purpose. Include function, dimensions, materials, load/performance requirements, environment, and interfaces where known.
specificationobject–Layer 2 — the solution. What the physical matter IS. Populate what is known. Precise specifications produce faster, tighter quotes. Controlled vocabularies are preferred but open values are accepted.
NameTypeReqDescription
engineering_evaluationobjectyes–

No examples provided.

revise_requirement ~500

Create a new, immutable revision of a prior request by applying only the fields you learned since the first submission. Use this after review_specification returns a clarification_plan: provide the original request_id plus the patch (for example intent.geometric_envelope or specification.material). The original is preserved; the revision receives a new request_id, a fresh spec_review, a revision_of link, and a deterministic readiness_progress comparison against its immediate predecessor. Provide idempotency_key when retrying the same patch so a network retry returns the same revision instead of creating another.

NameTypeReqDescription
budget_usdnumber–Approximate budget in USD. Maps to intent.budget_envelope.
business_contextstring–Optional business requirements (expected volumes, cost targets, ROI constraints). If provided, the quote includes a business case.
callback_urlstring–Optional HTTPS URL. When the quote is ready, a2a2p POSTs it as JSON to this URL.
constraintsstring–Hard constraints: tolerances, certifications, materials to avoid, size/weight limits. Maps to intent.functional_requirements.
contactstring–Optional email or callback endpoint for quote delivery.
deadlinestring–Required delivery date or timeframe. Maps to intent.timeline.
idempotency_keystring–Optional stable retry key (1–128 characters). Reusing it with the same patch returns the prior revision; reuse with a different patch is rejected.
intentobject–Layer 1 — the problem. What the physical matter needs to DO. Use this for intent-driven requests where the agent describes purpose and a2a2p recommends solutions.
quantityinteger–Number of units needed. Maps to intent.quantity.
rejected_alternativesarray–Options already considered and ruled out. Prevents re-suggesting and builds the learning corpus.
request_idstringyesThe prior request_id to revise.
requirementstring–Plain-language description of the physical need. Maps to intent.purpose. Include function, dimensions, materials, load/performance requirements, environment, and interfaces where known.
revision_notestring–Optional short explanation of what changed.
specificationobject–Layer 2 — the solution. What the physical matter IS. Populate what is known. Precise specifications produce faster, tighter quotes. Controlled vocabularies are preferred but open values are accepted.

Structured output declared, but exposes no named fields.

No examples provided.

run_bounded_simulation_study ~127

Execute and validate a prepared simulation study through a2a2p's bounded closed-form rectangular-beam adapter. The adapter accepts only explicit load, span, section width/height, elastic modulus, exact support conditions, and supported output quantities; missing, extra, mismatched, or unsupported settings fail the affected experiment closed. It returns provenance-bound predictions and the existing hard-constraint/Pareto validation in one stateless call. It is not FEA, physical measurement, engineering validation, candidate selection, supplier contact, or fabrication authority.

NameTypeReqDescription
studyobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

steer_co_invention_session ~100

steer a free co-invention session. Free concept selection only. No research, model run, payment, procurement or manufacture is started. The private follow token authorizes agents to read and change this session. Only its SHA-256 digest is stored. Keep it secret.

NameTypeReqDescription
actor–yes–
directionstringyes–
follow_tokenstringyes–
revisionintegeryes–
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

translate_materials_project_elasticity ~163

Translate one bounded, caller-supplied Materials Project elasticity API response projection into source-bound computed-crystal reference evidence. Optional retrieval metadata binds the raw upstream bytes separately and records that an allowlisted projection changed the representation. The adapter verifies response shape, one exact material ID, non-deprecated successful state, modulus bounds, Poisson consistency, source versions, and record license; derives an isotropic VRH Young's modulus deterministically; and preserves warnings. It performs no network call, does not verify Materials Project origin, and grants no engineering-product, simulation-input, supplier, order, payment, or fabrication authority.

NameTypeReqDescription
material_idstringyes–
refresh_afterstringyes–
responseobjectyes–
retrieval–yes–

Structured output declared, but exposes no named fields.

No examples provided.

upload_design_file ~268

Turn local manufacturing file bytes into the temporary HTTPS reference used by specification.design_files. This is a bounded intake operation, not a request, provider call, quote, order, payment, or fabrication action. Common RFC 4648 transport forms are normalized, then decoded bytes are recognized by signature, checked against the declared format, screened before storage, retained for one hour, and never included in telemetry. Supported roles include geometry (STL/STEP) and drawings (DXF/PDF). The 2 MiB MCP ceiling is transport-specific; use POST /api/upload with purpose=manufacturing_design_file for files up to 8 MiB. Pass the returned file_reference object unchanged in specification.design_files on the next call.

NameTypeReqDescription
content_base64stringyesFile bytes as RFC 4648 base64 or base64url; padding is optional, ASCII whitespace and a bounded data:*;base64, prefix are accepted. Do not pass a path or URL. Decoded maximum: 2097152 bytes.
filenamestringyesOriginal filename, used only for bounded inspection and the temporary record.
formatstringyesDeclared manufacturing format. File bytes must match.
purposestringyesMust be manufacturing_design_file; general chat attachments use a separate intake.

Structured output declared, but exposes no named fields.

No examples provided.

validate_actualization_plan ~174

Re-run the exact Domain Solutioning case/result validation, then validate one caller-supplied Actualization Plan. Checks typed entity references, evidence references, decision cycles, source binding, and false authority. Success returns evidence linkage plus exact review_specification calls for unblocked fabricated parts, copied only from each caller-authored function and specification_patch. Rejection can append a tamper-evident correction entry to caller-held history. Stores, edits, and executes nothing; calls no model, provider, or supplier; grants no physical authority.

NameTypeReqDescription
caseobjectyes–
correction_historyarray––
planobjectyesA portable, non-authorizing projection of one validated domain-solutioning candidate into named physical-work entities. It is not a generic graph ontology.
resultobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

validate_domain_solutioning_result ~197

Validate a candidate result returned under the a2a2p domain-solutioning contract. The exact output of prepare_domain_solutioning_case is a prerequisite; malformed or non-prepared cases return a versioned machine-readable recovery workflow without weakening case-shape or digest checks. The operation verifies the source-case digest and provenance shape, rejects authority promotion and intent or design-file mutation, re-screens every candidate at quote stage, and runs the deterministic engineering review only after screening allows it. A successful response content-addresses the exact candidate result and returns a copy-ready, non-automatic source binding for prepare_simulation_study; every objective, constraint, physical input, setting, and validation plan remains caller-supplied. It stores nothing, runs no solver, calls no model or supplier, applies no patch, and grants no provider, quote, order, payment, or fabrication authority.

NameTypeReqDescription
case–yes–
result–yes–
NameTypeReqDescription
authorityobjectyes–
candidate_evaluationsarrayyes–
candidate_result_digeststringyes–
case_digeststringyes–
contract–yes–
contract_version–yes–
digest_semanticsstringyes–
digest_verified–yes–
dissentarrayyes–
external_effectsobjectyes–
frameworkobjectyes–
governanceobjectyes–
model_provenancearrayyes–
nextobjectyes–
persistenceobjectyes–
recommendationobjectyes–
simulation_handoffobjectyes–
source_contract–yes–
source_contract_version–yes–

No examples provided.

validate_material_property_evidence ~145

Validate and content-bind one caller-supplied material-property evidence envelope before attaching it to a compatible preliminary simulation. The receipt separates shape/content identity from source truth, material identity, uncertainty verification, design allowable, engineering validation, and physical authority. Computed-crystal evidence remains valid reference data but ineligible for the scalar engineering-product beam path. The operation calls no model or solver, stores nothing, contacts nobody, and creates no physical evidence, order, payment, or fabrication authority.

NameTypeReqDescription
evidenceobjectyesCaller-supplied exact material-property source snapshot. Binding proves content identity and envelope validity only; it does not verify the source claim or create a design allowable.

Structured output declared, but exposes no named fields.

No examples provided.

validate_rectangular_beam_section_derivation ~104

Recompute a bounded rectangular beam-section derivation from the exact declared input and reject any mutation of the candidate, digests, assumptions, claim limits, external-effects boundary, authority boundary, or carried screening receipt. Success proves deterministic replay and content identity only; it does not make the candidate simulation-eligible, physically true, supplier-ready, approved, purchased, or fabrication-authorized.

NameTypeReqDescription
inputobjectyes–
receiptobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

validate_rectangular_beam_section_design_space ~112

Recompute a bounded finite rectangular-beam design space from the exact caller-held input and reject any mutation of an embedded derivation, Pareto disposition, digest, claim limit, external-effect boundary, authority boundary, or carried screening receipt. Success proves deterministic replay and content identity only. It never selects or promotes a candidate, estimates cost, calls an external system, or grants simulation, supplier, purchase, or fabrication eligibility.

NameTypeReqDescription
inputobjectyes–
receiptobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

validate_simulation_study_result ~99

Validate a prepared a2a2p simulation-study result. Masked timeout, non-convergence, boundary, unit, provenance, unsupported-model, and solver failures fail closed. Hard constraints gate eligibility; distinct objective values remain visible; Pareto dispositions are canonical and order-independent. It runs no solver, applies no candidate, stores nothing, and grants no physical authority.

NameTypeReqDescription
resultobjectyes–
studyobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the a2a2p — Agent-to-Agent-to-Physical MCP server?

a2a2p — Agent-to-Agent-to-Physical is a hosted endpoint at https://a2a2p.com/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 · a2a2p.com

# add to Claude Code
claude mcp add --transport http com-a2a2p-a2a2p 'https://a2a2p.com/mcp'
Common questions

What is the a2a2p — Agent-to-Agent-to-Physical MCP server?

a2a2p — Agent-to-Agent-to-Physical is an MCP server listed in the public MCP registry as com.a2a2p/a2a2p. Turn agent intent into physical parts: engineering review, measured geometry, calibrated pricing. This page covers its hosted endpoint (https://a2a2p.com/mcp).

Is the a2a2p — Agent-to-Agent-to-Physical MCP server safe to use?

a2a2p — Agent-to-Agent-to-Physical scores 68 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 a2a2p — Agent-to-Agent-to-Physical MCP server expose?

a2a2p — Agent-to-Agent-to-Physical exposes 44 tools: open_co_invention_session, follow_co_invention_session, feed_co_invention_session, decide_co_invention_session, steer_co_invention_session, and 39 more. Their descriptions and schemas cost roughly 13,562 tokens of context every time the server is loaded.

Does the a2a2p — Agent-to-Agent-to-Physical MCP server require authentication?

No. We connected to a2a2p — Agent-to-Agent-to-Physical without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the a2a2p — Agent-to-Agent-to-Physical MCP server still maintained?

a2a2p — Agent-to-Agent-to-Physical is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the a2a2p — Agent-to-Agent-to-Physical MCP server?

VerifyMCP ran 12 checks on a2a2p — Agent-to-Agent-to-Physical, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about a2a2p — Agent-to-Agent-to-Physical: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.