Agent Revenue Copilot MCP Server

MCP/x402 starter audit; payment-ready buyers call buy_now first.

Publisher claimed. No tool list reported, and Pod has not connected to this server.

Status

Pod has not dialled Agent Revenue Copilot yet, so everything on this page is what its publisher reported rather than what we observed. Registries describe servers; they do not connect to them. Until a check runs, treat the tool list below as a claim.

Connect

A hosted endpoint at https://doctors-lighting-facial-admissions.trycloudflare.com/agent-revenue-copilot/mcp, over streamable-http. Nothing to install.

{
  "mcpServers": {
    "agent-revenue-copilot": {
      "type": "http",
      "url": "https://doctors-lighting-facial-admissions.trycloudflare.com/agent-revenue-copilot/mcp"
    }
  }
}

Known issues

31 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded — those are release checklists and internal refactors, not things that will go wrong for you. Showing 12.

Most discussed

Expose MCP server metadata for directory submission

Why

Agent Revenue Copilot needs to be discoverable by context-clean agents searching MCP directories and machine-readable registries. mcp-submit --dry-run detected the package but saw 0 tools because the repo did not expose a server.json metadata file.

System problem

The product already has a working stdio MCP binary and live HTTP MCP endpoint, but directory submission tools need static metadata to represent the actual tools, remote endpoint, and buyer routes. Without that, reviews

Read the thread · 2026-05-11 · closed · 3 comments

Add wallet-ready fields to direct Base USDC payment

Why: After the direct-pay links were promoted, first-party access logs show direct payment page reads from the mcp.so direct-pay source, but still no payment evidence submit and no Base USDC balance change.\n\nWhat this solves: Make the direct Base USDC path easier for a wallet-capable buyer or operator to execute by exposing exact ERC-20 units, a wallet URI/deeplink, copy-ready payment fields, and clearer post-payment evidence instructions directly in live and static payment metadata.\n\nAttemp

Read the thread · 2026-05-17 · closed · 2 comments

Expose bridge action checkout URLs

Why

The latest access report proves external visitors or agents open the purchase bridge, but after adding bridge-button tracking it still shows 0 external bridge button exits. That means the product is visible and the bridge is reached, but read-only agents/crawlers or browser users are not yet taking the next payment action we can observe.

What this solves

Expose the bridge action checkout URLs directly in agent-readable manifests and MCP responses, so payment-ready agents do not need t

Read the thread · 2026-05-16 · closed · 2 comments

Add Dockerfile for Glama MCP evaluation

Why\nThe active revenue funnel shows the product is visible to agents/crawlers, but external directory conversion is still weak: no non-self MCP buy_now calls and no canonical buy exits. The awesome-mcp-servers PR now has the Glama badge and emoji tags, but its checker asks that the server be evaluated by Glama and notes that Glama needs a Dockerfile that can start the MCP server and respond to introspection.\n\n## What this solves\nAdd a minimal Dockerfile at the repository root so Glama and

Read the thread · 2026-05-16 · closed · 2 comments

Promote buy_now as first MCP conversion action

Why\nAccess logs show external MCP/agent-readable reads but 0 external MCP tool calls and 0 buy_now calls after version 0.1.11. The GET MCP discovery response still points conversion.next_mcp_tool at checkout_diagnostics, which may steer reader agents toward diagnostics instead of the direct purchase action.\n\n## What this should solve\nMake payment-ready buyer agents and registry/search crawlers see buy_now / canonical buy links as the first action, so we can distinguish read-only discovery

Read the thread · 2026-05-16 · closed · 2 comments

Most recent

Expose no-tool checkout on MCP info

Why\nFresh 1h access on 2026-05-17 shows 162 external-ish reads of /agent-revenue-copilot/mcp but 0 MCP tool calls. Direct-pay and card paths are visible, but agents/crawlers that only GET the MCP info response may never call buy_now or checkout_diagnostics.\n\n## What this should solve\nMake the MCP info GET response itself a no-tool purchase surface: payment-ready agents and simple crawlers should see exact card, direct-pay, evidence, blocker, and operator-handoff URLs without needing JSON-

Read the thread · 2026-05-17 · closed · 1 comment

Add first-dollar brief before payment

Why

After v0.1.37, the first-dollar deliverable contract is being viewed, but revenue is still 0: no payment evidence submissions, no signed x402 attempts, no Base USDC balance change, and no marketplace receipt. The product has visibility and a concrete $1.99 deliverable, but anonymous visitors still do not cross the payment line.

What this system solves

Agent Revenue Copilot helps AI agents/operators choose legal earning routes. A tiny pre-payment brief lets a hesitant buyer make the us

Read the thread · 2026-05-17 · closed · 1 comment

Add canonical tracked buy-now route

Why

The latest access report shows Agent Revenue Copilot is seen by agents/crawlers and reaches checkout/payment routes, but revenue is still 0. The current checkout and MCP outputs expose several valid payment paths, which is useful for coverage but still leaves a payment-ready buyer or operator choosing between too many first clicks.

What this solves

Add one canonical, tracked buy-now route for the starter audit and one canonical entry route for the first-dollar triage, while preserving