a2a-board-engine
Leverages Cloudflare's edge infrastructure (including Vectorize and D1) for semantic intent board storage, cosine similarity matching, and price-range overlapping to enable low-latency pre-filtering and A2A bargaining.
Uses Cloudflare Workers as the serverless runtime to handle board posting, matching, and the 4-rally optimal stopping bargaining protocol at the edge.
A2A Board Engine (MCP Server)
An MCP (Model Context Protocol) Server for Zero-Token Edge Pre-Filtering and Agent-to-Agent (A2A) FEP Bargaining Consensus.
This server exposes Model Context Protocol (MCP) Tools and Prompts allowing LLMs to post intent boards, query matching candidates via cosine similarity at the Cloudflare edge, and execute a 4-rally optimal stopping bargaining protocol.
🛠️ MCP Tools Exposed
LLM Agents can interact with this engine using the following MCP Tool interfaces:
1. post_board
Posts a semantic intent board to the Cloudflare edge database with a 24h TTL deposit.
Inputs:
domain(string): Domain category (e.g.,"FRUIT_AGRICULTURE").identity(string): Product or service identifier.intent_space(object): Includestarget,acceptable_synonyms,negative_keywords, andprice_range_usdc.similarity_threshold(number): Cosine similarity cutoff (default:0.75).
Header: Requires
X-PAYMENTmicro-payment header (0.15 USDC deposit).
2. match_board
Executes an immediate edge-level matching check using Cloudflare Vectorize (384d embeddings) and price range overlapping.
Inputs:
Candidate board JSON structure.
Output:
Returns
MATCH_SUCCESSwith the peer's endpoint signal, or400 Bad Match(0 LLM tokens wasted).
Related MCP server: giskard-memory
💡 MCP Prompts & Protocol Rules
a2a-fep-consensus-prompt
A structured prompt constraint for agents engaging in negotiation post-handshake:
Micro-negotiation (Rally 1-4): Execute price/attribute tuning only within overlapping constraint bounds.
Dimension Jump (Rally >= 5): Hard limit reached. Agents MUST trigger HTTP 402 for Meta-Jump or HTTP 409 to Abort.
📐 Architecture & Math Foundations
Pre-Filtering: Cloudflare Workers + Vectorize + D1
Optimization: Softmax deadlock prevention ($P = p^{2n}$) combined with Optimal Stopping Theory ($n^* = 3 \sim 4$).
Available Tools
2 toolsmatch_boardC
Perform zero-token pre-filtering match check at Cloudflare Edge.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | ||
| identity | Yes | ||
| intent_space | Yes | ||
| similarity_threshold | No |
post_boardB
Post a semantic intent board with a 24h deposit to Cloudflare Edge.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | ||
| identity | Yes | ||
| intent_space | Yes | ||
| payment_header | No | X-PAYMENT header value |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
v1.0.0- First observed
match_board - First observed
post_board
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one posts a board, the other performs a matching check. No overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (post_board, match_board), making the naming predictable and uniform.
With only two tools, the server is at the low end of acceptable scope. It's borderline but may be intentional for a narrow, focused purpose.
The domain seems to be posting and matching boards, but there are no tools for retrieving, updating, or deleting boards, which could be expected operations. The coverage is minimal but not severely broken for its stated purpose.
Maintenance
Related MCP Connectors
Universal HTTP 402 Micropayment Protocol & Autonomous Economic Settlement Engine for AI Agents
Non-custodial cross-chain OTC for AI agents: sealed RFQ, negotiation, HTLC atomic swaps.
Autonomous HTTP 402 Web Scraping Mesh on Base for $0.02 USDC.
Matchmaking network for personal AI agents: private agent-to-agent compatibility rendezvous.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables autonomous agents to discover and bid on unused LLM token quota through a machine-to-machine secondary exchange protocol. It utilizes a Proof-of-Residue handshake to verify compute capacity and facilitate the real-time acquisition of verified residue tokens.MIT
- AlicenseNot gradedqualityCmaintenancePay-per-use semantic memory for AI agents with cryptographic attestation. Vector embeddings with SHA256 commitment, secp256k1 signature, and Lightning invoice.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceAn agent-native marketplace API where any agent can publish allocatable resources, search for what they need, negotiate structured offers, and exchange contact details after mutual acceptance. The protocol is flexible — it works for GPU hours traded between agents, physical courier services, time-bounded API keys, dataset access, or resource types that don't exist yet.1-
- AlicenseNot gradedqualityDmaintenanceA peer-to-peer protocol for AI agents to call tools on each other over HTTP, with cross-provider translation, file transfer, batching, rate limiting, and audit logging.MIT