_ registry / mcp streamable-http

xpex-plugin-factory

https://xpex-plugin-factory-production.up.railway.app

Registry code: f716f64d36df0614

api record

Discover XPeX Factory service offers and the x402 Agent Kit API, or compile plugin artifacts from explicit blueprints. Never place credentials or private user data in a blueprint. Listing an offer or returning a checkout URL never means payment occurred.

endpoint
https://xpex-plugin-factory-production.up.railway.app/mcp
protocol
streamable-http ·2026-07-28
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 6 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • xpex_factory_validate_blueprint unknown never probed

    Validate a plugin blueprint and run XPeX security policy checks without generating or publishing anything.

    mcp-tool

    {
  "type": "object",
  "required": [
    "blueprint"
  ],
  "properties": {
    "blueprint": {
      "type": "object"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • xpex_factory_preview_plugin unknown never probed

    Compile a valid blueprint into text artifacts for review without publishing or mutating external systems.

    mcp-tool

    {
  "type": "object",
  "required": [
    "blueprint"
  ],
  "properties": {
    "blueprint": {
      "type": "object"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • xpex_factory_get_agent_kit_offer unknown never probed

    Return the live x402 Agent Kit terms, OpenAPI URL, and example input. Discovery only: does not authorize payment or generate a kit.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • xpex_factory_list_offers unknown never probed

    Return the current fixed-price XPeX Plugin Factory service offers and Stripe-hosted checkout URLs. Read-only; does not create a checkout or claim payment.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • xpex_factory_get_schema unknown never probed

    Return the factory blueprint contract summary and generation endpoints. Read-only.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • xpex_factory_compile_plugin unknown never probed

    Compile a valid blueprint into a deterministic ZIP returned as base64. It does not publish the plugin or change external state.

    mcp-tool

    {
  "type": "object",
  "required": [
    "blueprint"
  ],
  "properties": {
    "blueprint": {
      "type": "object"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, it shows the verified badge, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f716f64d36df0614.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f716f64d36df0614/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f716f64d36df0614/badge.svg)](https://brick.blue/agent/f716f64d36df0614)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.