The fourth and final batch of the submission backlog is profiled and published — eight providers, 222 new artifacts. One number stands out: six of the eight ship a hosted MCP server alongside their REST API.
Not one of these is a large company. They are small, single-purpose utilities — the long tail of the API economy — and MCP is now simply part of what they ship.
| Provider | What it does | MCP |
|---|---|---|
| CycleCalcs | Positional-astronomy engine — sun and moon rise/set, twilight, moon phase | Yes |
| 1Lookup | 40+ data verification and enrichment products behind one REST API and one credit balance | Yes |
| rtcStats | Troubleshooting and monitoring for WebRTC applications from uploaded or streamed stats dumps | Yes |
| legal.ge | Georgia’s legal marketplace — keyless API matching a natural-language legal problem to counsel | Yes |
| Infoway | Real-time and historical market data across US, Hong Kong, China A-shares, Japan, Korea and India equities, forex and crypto | Yes |
| ByKaranteli | Crypto-derivatives market structure — funding rates and arbitrage signals, free and keyless | Yes |
| LinkPeek | ~92 endpoints of URL intelligence, QR generation, and DNS/WHOIS/SSL checks | — |
| FaturaPDF | Turns a JSON payload into a Brazilian invoice or receipt PDF, with mod-11 validated CPF/CNPJ | — |
The utility API grew a second interface
For twenty years the small utility API had exactly one shape: a REST endpoint and a docs page. What this batch shows is a second interface arriving as a default rather than a project — an astronomy calculator and a crypto funding-rate feed both ship MCP, and neither is a company with a platform team to spare.
That is what a standard looks like when it stops being a strategy and becomes a checkbox. The providers most likely to adopt quickly are not the largest ones; they are the ones small enough that adding an interface is an afternoon rather than a quarter.
Worth noting what MCP is being bolted onto here. FaturaPDF validates Brazilian CPF/CNPJ tax identifiers with mod-11 checksums. legal.ge matches a plain-language legal problem to counsel in Georgia, keyless. These are narrow, jurisdictional, deeply unglamorous services — exactly the kind an agent cannot invent and has to call.
Where the backlog ended up
Across four batches: 38 providers profiled, 1,286 artifacts, zero failed runs. Two were removed rather than published — a duplicate submission of a provider already in the catalog, and a profile that had been deliberately retracted and that the pipeline correctly refused to resurrect.
A third produced an honest zero: no developer program, nothing machine-readable but an llms.txt, every documented path a 404 — including an apis.json its submission had cited. We published the evidence instead of modelling an API that was not there.
As always, every artifact carries its provenance — searched, probed, generated or derived — and every provider owns their record and can correct it. Write to us, or add your API.