MARKET MONITOR / CATALOGUE Services 130,986 MCP listed 40,656 x402 90,397 Rails Base / Solana / Polygon / Arbitrum Imported 2026-10-29 · 3 sources
← All services

Daily transfers, volume and coverage →

Openapi mcp

x402 resource x402 REST

47-85-47-24.sslip.io · 47-85-47-24.sslip.io · Dev & Code

Generate a runnable TypeScript MCP stdio server from a built-in OpenAPI 3.x contract using the stable Model Context Protocol SDK v1

Price per call 0.001 USDC per call published unit: per call
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 Attribution blocked confidence: low · read 2026-10-29

Where you can pay

1 route from the provider's payment requirements
Payment networks and amounts published for Openapi mcp.
Network Scheme Amount Asset
Base exact 0.001 USDC

“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 1000 = 0.001 USDC per call on Base.

What you can call

access: payment per call (x402)

endpoint https://47-85-47-24.sslip.io/v1/openapi-mcp

Request

{
    "type": "http",
    "method": "GET",
    "queryParams": {
        "scenario": "orders-api-mcp-server"
    }
}

Response

{
    "type": "json",
    "example": {
        "files": {
            "README.md": "# Orders MCP Server\n",
            "package.json": "{\n  \"dependencies\": {\"@modelcontextprotocol/sdk\": \"1.29.0\"}\n}\n",
            "src/index.ts": "import { McpServer } from \"@modelcontextprotocol/sdk/server/mcp.js\";\nimport { StdioServerTransport } from \"@modelcontextprotocol/sdk/server/stdio.js\";\n",
            "tsconfig.json": "{\n  \"compilerOptions\": {\"strict\": true}\n}\n",
            "mcp-config.json": "{\n  \"mcpServers\": {}\n}\n"
        },
        "format": "typescript-mcp-stdio-server",
        "warnings": [
            "Generated tools can call network APIs; review base URLs, credentials, and scopes before use."
        ],
        "operations": [
            {
                "path": "/orders/{id}",
                "title": "Call GET /orders/{id}",
                "method": "GET",
                "base_url": "https://api.example.com",
                "tool_name": "get_orders_id",
                "input_fields": [
                    "id"
                ],
                "write_operation": false
            }
        ],
        "server_name": "Orders MCP Server",
        "generator_id": "mcpforge-27618b0597e2a0a3",
        "source_sha256": "0000000000000000000000000000000000000000000000000000000000000000",
        "mcp_sdk_version": "1.29.0",
        "operations_count": 1,
        "write_operations": 0,
        "generator_version": "mcpforge-openapi-typescript-stdio/1.0"
    }
}

Examples are the provider's own, not a call we made.

Observed inflows · last 30 days

No inflow observed in this window

The payout address is also published by 10 other service(s); the volume cannot be attributed to one of them.

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

Daily history → · what a transfer does and does not prove

Opportunity insights

2 findings from measured data
  • Payment attribution is blocked

    The payout address is shared with 10 other service(s). That is normal for facilitator and platform addresses, and it is why this profile shows no inflow figure. The volume exists — it just cannot be split without inventing a rule.

    How attribution works →
  • Category benchmark

    27 of 3,156 services (0.9%) in Dev & Code have attributable inflows; 903 have a source-measured call count. Median measured calls: 2.

    Rank this category by observed inflows →

What the provider says

Generate a runnable TypeScript MCP stdio server from a built-in OpenAPI 3.x contract using the stable Model Context Protocol SDK v1

Quoted from PayAI · source record · read 2026-10-29


Facts and where they come from

Price
0.001 USDC per call Provider claim
Recorded value: 0.001 USDC per call.
Unit
per call
Protocol
x402, REST · transport: HTTP Provider claim
Auth
x402
Source
PayAI · Public discovery API (provider-published records)
Last checked
Not checked by us yet — the data is as the source published it
First seen
2026-10-26

Money, and what it actually proves

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

Attribution blocked · confidence low
The payout address is also published by 10 other service(s); the volume cannot be attributed to one of them.

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. The payout address is also published by 10 other service(s); the volume cannot be attributed to one of them.

Daily market statistics — the ledger view, day by day

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

Payment rails

Base · exact · USDC
0xFe8b1298727706A6D9737C5afbC7AF8e76842B91
0.001 USDC
From source record

A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it. See evidence levels.

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
Endpoint Provider claim
https://47-85-47-24.sslip.io/v1/openapi-mcp
Evidence

Als Resource-URL im Bazaar-Eintrag geführt.

facilitator.payai.network 2026-10-29
Input output Provider claim
Request/response examples published with the listing
Evidence

Beispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters.

facilitator.payai.network 2026-10-29
Payment Provider claim
1 rail: Base · payee 0xFe8b1298727706A6D9737C5afbC7AF8e76842B91
Evidence

Aus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt.

facilitator.payai.network 2026-10-29
Pricing Provider claim
0.001 USDC per call
Evidence

Atomic amount 1000 = 0.001 USDC per call on Base. Netzwerk: Base.

facilitator.payai.network 2026-10-29
Protocol Provider claim
x402 (HTTP 402 payment challenge)
Evidence

Im x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http).

facilitator.payai.network 2026-10-29
Provider Provider claim
47-85-47-24.sslip.io
Evidence

Die Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter.

facilitator.payai.network 2026-10-29

Endpoint checks

We have not called this endpoint yet. Until we do, everything above is what the source published — no more.

Tags


Competitors & category benchmark

Rank the whole category →
Closest competitors Dev & Code

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 3,156 services in this category
With a measured call count 903 (28.6 %)
With a published price 1,105 (35.0 %)
With attributable inflows 27 (0.9 %)
Observed inflows · 30d $135.44
Median measured calls 2
Median price per call $0.01

Similar services

All of Dev & Code →

GitHub Repo & User Data x402 REST usage

GitHub data. Repository stats, user profiles, and code-search results (stars, forks, language, topics, issues) via the GitHub REST API.

api.kadec0.xyz Dev & Code 129 calls / 30d checked 2026-10-29
0.02 USDC per call per call

Read contract x402 REST usage

Call a read-only (view/pure) function on any deployed contract via eth_call and get the decoded result. Give the contract address and a human-readable signature (e.g. 'balanceOf(address) view returns (uint256)') plus arg...

chain.openverbs.com Dev & Code 72 calls / 30d checked 2026-10-29
0.006 USDC per call per call

VIN decoder (NHTSA) x402 REST usage

Decode a vehicle VIN via the US NHTSA vPIC database: make, model, year, trim, body class, engine, fuel type, plant and vehicle type. Accepts full or partial VINs. Use it when an agent holds a VIN and needs the vehicle's...

agent402.tools Dev & Code 66 calls / 30d checked 2026-10-29
0.004 USDC per call per call

Decode x402 REST usage

Normalized NHTSA vPIC VIN decode (?vin=) — make/model/year/engine/body/… with fetch provenance, plus ORIGINAL factory new-vehicle warranty terms (basic/powertrain/corrosion/roadside/EV battery) keyed off make + model-yea...

api.vindexapi.dev Dev & Code 65 calls / 30d checked 2026-10-29
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.