agentmarketindex.
About the index ↗
MARKET MONITOR / CATALOGUE Services 133,139 MCP listed 40,873 x402 92,348 Rails Base / Solana / Polygon / Arbitrum Imported 2026-10-31 · 3 sources
← All services

Daily transfers, volume and coverage →

Context Keeper (remote)

MCP server MCP

jarmstrong158 · github.com/jarmstrong158 · Infrastructure

Provider site ↗

Cloudflare Worker remote backend for context-keeper (D1). MCP 2026-07-28, dual-era.

Price — no price published
Calls · 30d — not reported by any source
Payers · 30d — not reported by any source
Observed inflows · 30d — not attributable
Inflow growth · 7d — not comparable (baseline under $1 or window incomplete)
Payment evidence No payment evidence confidence: none · checked 2026-10-24

Observed inflows · last 30 days

No inflow observed in this window

No payout address is published, so nothing can be observed.

Observed inflows by window for Context Keeper (remote).
Window Observed Transfers
Last complete day (2026-10-30) — —
Last 7 days — —
Last 30 days — —
Growth, 7d against the 7 before not comparable
Source: on-chain transfer scan (USDC on Base) Window: 2026-10-01 → 2026-10-30 Scanned: 30/30 days Sample: 0 days with a measurement First seen: never Last update: 2026-10-30

Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.

Competitors & category benchmark

Rank the whole category →
Closest competitors Infrastructure

Sorted by source-measured calls, not by our opinion. The right-hand figure is observed inflow, which stays empty for peers whose address is shared.

Category benchmark 6,048 services in this category
With a measured call count 961 (15.9 %)
With a published price 1,107 (18.3 %)
With attributable inflows 20 (0.3 %)
Observed inflows · 30d $70.01
Median measured calls 2
Median price per call $0.01

Similar services

All of Infrastructure →

Events x402 REST usage

Query Ethereum contract event logs via eth_getLogs - filter by contract, topic, and block range

api.onesource.io Infrastructure 230 calls / 30d checked 2026-10-31
0.005 USDC per call per call

Agent Web Tools x402 REST usage

Check if a URL is up: status, latency, redirects, title.

agent-web-tools.agent-web-tools.workers.dev Infrastructure 71 calls / 30d checked 2026-10-31
0.001 USDC per call per call

Pulse x402 REST usage

China pulse, cheap enough to POLL: what China is talking about RIGHT NOW and what is NEW since your last call - built for agents that monitor continuously. Returns `consensus` (phrases trending on 2+ of Weibo/Baidu/Douyi...

stockwaves.net Infrastructure 62 calls / 30d checked 2026-10-30
0.003 USDC per call per call

StableStudio x402 REST usage

Get a client token for direct upload to Vercel Blob

stablestudio.dev Infrastructure 59 calls / 30d checked 2026-10-31
0.01 USDC per call per call

Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.

Service details, payment routes and source evidence

What you can call

endpoint https://context-keeper-remote.{account}.workers.dev/mcp/{token}

Opportunity insights

1 finding from measured data

What the provider says

Cloudflare Worker remote backend for context-keeper (D1). MCP 2026-07-28, dual-era.

Quoted from Official MCP Registry · source record · read 2026-10-26

Facts and where they come from

Price
Price not published Not found
Unit
Not stated by the provider
Protocol
MCP · transport: streamable-http Provider claim
Auth
Not stated
Endpoint
https://context-keeper-remote.{account}.workers.dev/mcp/{token}
Source code
https://github.com/jarmstrong158/context-keeper-remote
Source
Official MCP Registry · Provider-published registry data
Last checked
Endpoint called 2026-10-24
First seen
2026-10-24

Money, and what it actually proves

Verified revenue · 30d Unknown
Observed inflows · 30d —
Attribution None
Receipt ledger Not connected

No payment evidence · confidence none
Neither a price nor a payout address is published.

Why revenue is “unknown”. A revenue figure needs a receipt: an amount a buyer actually paid for this service. We hold none for this entry, and we hold no funds at all. What we have instead is nothing measurable: no price, no attributable address, no receipt. No payout address is published, so nothing can be observed.

Daily market statistics — the ledger view, day by day

No daily history has been archived for this service yet. Open the full daily history →

MCP server

Registry name
io.github.jarmstrong158/context-keeper-remote
Version
0.2.0
Protocol check
Provider claim Listed in the official MCP Registry. We have not run an MCP handshake against it yet.

Provenance

One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.

Statement Status What we found Source Checked
Docs Provider claim
https://github.com/jarmstrong158/context-keeper-remote
Evidence

Repository im Registereintrag hinterlegt; Installation und Nutzung sind dort beschrieben.

 registry.modelcontextprotocol.io 2026-10-26
Endpoint Provider claim
https://context-keeper-remote.{account}.workers.dev/mcp/{token}
Evidence

Als Remote-Endpunkt im Registereintrag genannt.

 registry.modelcontextprotocol.io 2026-10-26
Pricing Not found
Evidence

Das MCP-Register nennt keinen Preis. Wir haben am 2026-10-26 im Registereintrag und, soweit vorhanden, im Repository nach einer Preisangabe gesucht und keine gefunden. Das heißt nicht, dass die Nutzung kostenlos ist.

 registry.modelcontextprotocol.io 2026-10-26
Protocol Provider claim
MCP (streamable-http)
Evidence

Das Register führt den Eintrag als MCP-Server, Version 0.2.0. Transport: streamable-http.

 registry.modelcontextprotocol.io 2026-10-26
Provider Provider claim
jarmstrong158
Evidence

Im official MCP Registry unter dem Namen "io.github.jarmstrong158/context-keeper-remote" veröffentlicht; der Eintrag ist die Selbstauskunft des Anbieters, nicht unsere Prüfung.

 registry.modelcontextprotocol.io 2026-10-26

Endpoint checks

When URL Answer Latency Payment challenge
2026-10-24 https://context-keeper-remote.{account}.worker... No response
cURL error 6: Could not resolve host: context-keeper-remote..workers.dev (see ht...
 2 ms —

We call the documented URL once, unauthenticated and without paying. We never retry a payment challenge and never sign in.

Compare this Claim this listing Report an error