_ registry / mcp streamable-http · checked 48m ago

saas-factory

https://factory.amjtech.om

Registry code: 930106e832b2d8ce

api record

AMJ Tools sells focused tools (images, documents, web pages, data) to agents, paid per call in USDC on Base with x402 v2. Call list_tools, then get_tool for the exact input schema and price, then run_tool. Without payment, run_tool returns HTTP 402 with payment_required (a base64 x402 PAYMENT-REQUIRED value); sign it with an x402 client and call run_tool again with payment_signature. Payment settles only if the call succeeds. Holders of a 30-day pass send api_key instead. File inputs take base64, a data: URL or an https URL; file outputs come back as { mime, bytes, base64 }.

endpoint
https://factory.amjtech.om:9443/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is saas-factory live?
Yes — it answered the hub's last check (checked 48m ago). It answered 100% of checks over the last 30 days.
Is saas-factory free to use?
Yes — the hub reached it with no key and no payment.
What tools does saas-factory have?
3 tools: run_tool, get_tool, list_tools.
Is saas-factory safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,016ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 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.

  • list_tools open 47m ago

    Every live tool with its slug, purpose, category, price per call (USDC) and endpoint.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • run_tool unknown never probed

    Run a tool on an input matching its input schema (see get_tool). Pay with payment_signature (x402 v2) or a pass api_key. Without either, returns HTTP 402 with payment_required describing the USDC payment.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug",
    "input"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "pattern": "^[a-z][a-z0-9-]{2,39}$",
      "description": "Tool slug from list_tools"
    },
    "input": {
      "type": "object",
      "description": "Request body matching the tool input schema.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "api_key": {
      "type": "string",
      "maxLength": 200,
      "description": "API key of a 30-day pass for this tool."
    },
    "payment_signature": {
      "type": "string",
      "maxLength": 20000,
      "description": "x402 v2 PAYMENT-SIGNATURE value for this call."
    }
  }
}
    arguments 33 lines
  • get_tool unknown 47m ago

    Input JSON Schema, output description, examples, limits and prices for one tool.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "pattern": "^[a-z][a-z0-9-]{2,39}$",
      "description": "Tool slug from list_tools"
    }
  }
}
    arguments 14 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, its README badge says «verified owner» with figures this hub measured, 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 930106e832b2d8ce.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/930106e832b2d8ce/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/930106e832b2d8ce/badge.svg)](https://brick.blue/agent/930106e832b2d8ce?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

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.