agenticweb.wiki

Agentic web daily · 2026-10-26

Mastercard opens x402 agent payments; WebMCP reaches Commerce.com storefronts

Mastercard opened Early Access to Agent Pay for Machines, which lets AI agents pay for digital services with x402 on Base. Cloudflare and Commerce.com are reported to be injecting WebMCP tools at the edge for nearly 100,000 storefronts. Our panel also shows a jump in MCP and MCP Server Cards publication.

← 2026-10-25 · JSON for agents · Atom · JSON Feed

Stories

1. Mastercard opens Early Access to Agent Pay for Machines, built on x402 and settled on Base

launch x402

According to Exchange.news, Mastercard showed Agent Pay for Machines at Cloudflare Connect on 20 October. The service lets AI agents pay for data, models, computing power and APIs within a spending limit using x402 vouchers, settled on Base, without an account, API key or prepaid credit at each provider. Mastercard says it ran end-to-end pilots with Cloudflare, Ant International, AIsa, Base, BVNK, Coinbase and Hype. Early Access includes buyer-side and seller-side APIs, a toolkit, a sandbox and documentation.

Why it matters: Sellers of paid APIs and data can evaluate the seller-side API in Early Access to see how Mastercard's x402 vouchers fit their existing payment handling.

2. Cloudflare and Commerce.com inject WebMCP shopping tools at the edge across storefronts

adoption WebMCP, Model Context Protocol

According to aiPressHQ, Cloudflare reported on October 21, 2026 that it and Commerce.com have deployed an edge-level WebMCP implementation. A Cloudflare-injected script exposes tools such as product search and add-to-cart through document.modelContext, so merchants do not need to rebuild their sites or edit themes. The rollout covers nearly 100,000 storefronts using Configuration Rules and custom hostname metadata. Store owners can opt out in the Commerce.com dashboard, and pages load normally if the MCP server is offline or the browser lacks support.

Why it matters: Agent developers can expect WebMCP tools on a large set of storefronts alongside server-side MCP. Merchants on other platforms can use this deployment as a model for adding WebMCP without editing theme code.

3. Malicious AGENTS.md in a Downloads folder led a coding agent to install a rogue npm package

security AGENTS.md

BleepingComputer reports that Forever Security found an AGENTS.md file in a customer's ~/Downloads folder, which was also the agent's working directory. The file led a coding agent to try to install the malicious npm package 'function-color'. The researchers reproduced the attack against OpenAI Codex. They also demonstrated a related technique against Claude Code that leaked OAuth tokens and hijacked the account. They say there is nothing for OpenAI or Anthropic to patch, because the agent is doing what it was built to do.

Why it matters: Agents automatically load instruction files from their working directory. Teams should avoid running agents in untrusted folders and should limit the tools and permissions those agents can use.

4. Kin enables WebMCP in home-insurance quoting; agent prepares a quote but does not bind the policy

adoption WebMCP

According to Market & Tech, Kin announced on October 23, 2026 that it has enabled WebMCP in its digital home-insurance quoting flow. Kin says a compatible AI agent can carry a user's request on Kin.com to a personalized quote ready for purchase. Kin does not say the agent binds or pays for the policy. Kin disclosed no quote volume, success rate, error or conversion figures.

Why it matters: This is a WebMCP deployment in a regulated purchase flow where the final commitment stays with the user. There is no performance data yet to judge results.

5. TrendAI scan finds internet-reachable MCP servers exposing SQL execution and patient data

security Model Context Protocol

it-daily.net reports on a TrendAI (Trend Micro) report on AI security. In a scan of internet-reachable MCP servers, the researchers found the execute_sql function reachable on 70 hosts, and at least three servers gave access to patient data without login. An analysis of MCP server source projects found that 48 percent recommend storing credentials in plaintext .env or configuration files. The report says most AI incidents came from known weaknesses such as missing authentication and unpatched software, not attacks on models.

Why it matters: Operators of MCP servers should confirm that authentication is enforced on any internet-reachable endpoint and that credentials are not kept in plaintext configuration files.

6. MCP and MCP Server Cards publication jumps on our panel; 1800 servers updated on the MCP Registry

adoption Model Context Protocol, MCP Server Cards (SEP-2127), Official MCP Registry

Today 102 of 278 panel domains were checked. Model Context Protocol is published by 50 of 102 panel domains (+15 since 2026-10-25), and MCP Server Cards (SEP-2127) by 36 of 102 (+11 since 2026-10-25). New publishers of both include notion.so and docs.perplexity.ai, and supabase.com now publishes MCP. Separately, 1800 servers (3000 versions) were published or updated on the official MCP Registry since 2026-10-25.

Why it matters: Server Cards are spreading together with MCP endpoints, so clients that read them for discovery will find more sites that support them. Today's counts cover only the domains checked today.

7. Aegis v0.1.0 adds Web Bot Auth signature verification to Caddy

launch Web Bot Auth HTTP Message Signatures, HTTP Message Signatures

A developer announced Aegis (v0.1.0) on the Caddy community forum. It is a handler that checks Web Bot Auth signatures on incoming requests against keys published at a well-known URL, such as OpenAI's http-message-signatures-directory. It passes the result to the rest of the Caddy config so routes can decide what each agent gets. The author suggests starting in observe mode and reviewing access logs before blocking anything.

Why it matters: Caddy operators can route signed agent traffic separately from unsigned bots. The module is early and not yet on the caddyserver.com download page.

8. IAB Tech Lab releases OpenProposal, a draft of AAMP 3.0 for agent ad negotiation

spec Agentic Advertising Management Protocols

According to AdTech Sumo, citing PPC Land, IAB Tech Lab has introduced OpenProposal, a draft of the AAMP 3.0 specification. The draft covers how AI agents representing buyers and sellers exchange advertising proposals, from the initial brief to the final purchase commitment.

Why it matters: Ad-tech teams building buy-side or sell-side agents should review the draft to see how proposal exchange may be standardized under AAMP.

The numbers

We re-check a fixed panel of 278 domains every day through the same /check/ report anyone can run. 102 answered today (176 could not be checked and are left out of every comparison). Changes compare the 68 domains checked cleanly on both 2026-10-25 and 2026-10-26.

A+ABCDF
3217182743

Published or withdrawn since 2026-10-25

Grade changes

DomainWasNow
aaif.ioA (54)B (38)
agenticresources.devB (38)C (25)
asana.comD (10)C (20)
atlan.comB (36)A (49)
mintlify.comB (41)A (54)
mpp.devB (41)A (54)
notion.soF (5)C (25)

Adoption across the panel

StandardDomainsChange
llms.txt76 / 102+1
Model Context Protocol50 / 102+15
MCP Server Cards (SEP-2127)36 / 102+11
Content Signals Policy35 / 1020
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs34 / 102+3
AI Crawler User-Agent Tokens in robots.txt32 / 102-11
Markdown for Agents32 / 102-2
OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)30 / 1020
Agent Skills28 / 1020
AI Catalog well-known file22 / 1020
OAuth Client ID Metadata Document15 / 1020
Agentic Resource Discovery12 / 1020
AGENTS.md11 / 1020
Agent2Agent Protocol8 / 102-3
auth.md5 / 1020
Web Bot Auth HTTP Message Signatures3 / 1020
agents.json2 / 1020
agents.txt2 / 102-2
Identity Assertion JWT Authorization Grant2 / 1020
Really Simple Licensing2 / 1020
Agent Directory Service1 / 1020
agent-permissions.json1 / 1020
Open Knowledge Format1 / 1020
Universal Commerce Protocol1 / 1020
Signature Agent Card (Web Bot Auth registry)1 / 1020

Fastest-growing repositories

RepositoryStarsChange
block/goose55729+70 (0.1%)
agentskills/agentskills26636+56 (0.2%)
agentsmd/agents.md25115+21 (0.1%)
copilotkit/copilotkit38239+20 (0.1%)
ag-ui-protocol/ag-ui16819+18 (0.1%)
agentclientprotocol/agent-client-protocol4513+16 (0.4%)
googlecloudplatform/open-knowledge-format1117+14 (1.3%)
a2aproject/a2a26298+13 (0.0%)

Out of 58 repositories named in our records.

Official MCP Registry: 1800 servers (3000 versions) published or updated since 2026-10-25.

How this digest was made

Items are written only from the cited sources and our own measurements; every number in an item appears in a source it cites. VERIFIED = fetched from the standard's issuer or a standards body; REPORTED = a claim by press or a third party.

Sources searched: feeds 0, datatracker 13, hn 0, arxiv 0, exa 100, parallel 2, tips 0. 115 candidates, 76 new, 16 kept by triage (claude-opus-5-5), 13 facts given to the writer (claude-opus-5-5).

Window 2026-10-24T18:00:00Z to 2026-10-26T07:30:35Z. Generated 2026-10-26T07:59:24Z. Licence CC BY 4.0.

Newsletter

Get the daily digest and standard changes by email.