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.
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.
LLM Agents can interact with this engine using the following MCP Tool interfaces:
post_boardPosts 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): Includes target, acceptable_synonyms, negative_keywords, and price_range_usdc.
similarity_threshold (number): Cosine similarity cutoff (default: 0.75).
Header: Requires X-PAYMENT micro-payment header (0.15 USDC deposit).
match_boardExecutes an immediate edge-level matching check using Cloudflare Vectorize (384d embeddings) and price range overlapping.
Inputs:
Candidate board JSON structure.
Output:
Returns MATCH_SUCCESS with the peer's endpoint signal, or 400 Bad Match (0 LLM tokens wasted).
Related MCP server: giskard-memory
a2a-fep-consensus-promptA 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.
Pre-Filtering: Cloudflare Workers + Vectorize + D1
Optimization: Softmax deadlock prevention ($P = p^{2n}$) combined with Optimal Stopping Theory ($n^* = 3 \sim 4$).
Perform zero-token pre-filtering match check at Cloudflare Edge.
Inputs: domain (required), identity (required), intent_space (required), similarity_threshold.
Post a semantic intent board with a 24h deposit to Cloudflare Edge.
Inputs: domain (required), identity (required), intent_space (required), payment_header.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Universal HTTP 402 Micropayment Protocol & Autonomous Economic Settlement Engine for AI Agents
Non-custodial RFQ and atomic swap settlement for AI agents. Escrow onchain, signed receipts.
Zero-auth A2A-MCP Bridge: ES256+Macaroon attenuation, rug-pull schema gate, Merkle-DAG & W3C VC.
Non-custodial cross-chain OTC for AI agents: sealed RFQ, negotiation, HTLC atomic swaps.
