_ registry / mcp streamable-http · checked 5h ago

skillforge-render

https://render.skillforge99.com

Registry code: 582676e2e42a35a8

api record

Screenshot, PDF, and OG-image rendering over MCP. Bearer key or per-call x402 USDC.

from a public catalogue that lists it, not from the operator

endpoint
https://render.skillforge99.com/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 skillforge-render live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is skillforge-render free to use?
Yes — the hub reached it with no key and no payment.
What tools does skillforge-render have?
4 tools: screenshot_url, render_og, extract_page, render_pdf.
Is skillforge-render 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 99.6%· all time 99.6%

latency
346ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 282 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • screenshot a web page
  • render a page or html to pdf
  • render an open graph image from html
  • extract page content as markdown or json
takes → gives
web pages, text → images, documents, text, data
tools
4 reads
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • screenshot_url reads unknown 5h ago

    Capture a screenshot image of a public web page or an inline HTML snippet, rendered in a real headless browser (JS, CSS, and web fonts execute). Returns a PNG/JPEG/WEBP image. Use this to visually preview a page, generate a thumbnail, or archive how a URL looked at a point in time.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "url": {
          "type": "string",
          "description": "Public http(s) URL to screenshot (exactly one of url/html)"
        },
        "html": {
          "type": "string",
          "description": "Raw HTML to render (exactly one of url/html, max 1MB)"
        },
        "width": {
          "type": "number",
          "description": "Viewport width in pixels, 320-1920 (default 1280)"
        },
        "format": {
          "enum": [
            "png",
            "jpeg",
            "webp"
          ],
          "type": "string",
          "description": "Output image format (default png)"
        },
        "height": {
          "type": "number",
          "description": "Viewport height in pixels, 240-1080 (default 800)"
        },
        "fullPage": {
          "type": "boolean",
          "description": "Capture the full scrollable page instead of just the viewport (costs 2 units instead of 1)"
        }
      }
    }
    arguments 34 lines
  • render_og reads unknown 5h ago

    Render an inline HTML snippet to a social-share (Open Graph) image sized for link previews, defaulting to the standard 1200x630 OG dimensions. Use this to generate og:image assets for blog posts, products, or share cards without hand-designing an image.

    mcp-tool

    {
      "type": "object",
      "required": [
        "html"
      ],
      "properties": {
        "html": {
          "type": "string",
          "description": "Raw HTML to render into the OG image (required, max 100KB)"
        },
        "width": {
          "type": "number",
          "description": "Viewport width in pixels, 320-1920 (default 1200)"
        },
        "height": {
          "type": "number",
          "description": "Viewport height in pixels, 240-1080 (default 630)"
        }
      }
    }
    arguments 20 lines
  • extract_page reads unknown 12h ago

    Fetch a public web page and extract its content as either clean, readable markdown (the default) or as structured JSON fields matched against a caller-supplied schema. Use markdown mode to summarize or quote a page's text; use structured mode to pull specific named fields (e.g. price, title, author) out of a page's content.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public http(s) URL to extract (required)"
        },
        "mode": {
          "enum": [
            "markdown",
            "structured"
          ],
          "type": "string",
          "description": "Extraction mode: 'markdown' (default, 2 units) returns cleaned page text as markdown; 'structured' (8 units, requires schema) returns JSON matched to the caller's field schema"
        },
        "schema": {
          "type": "object",
          "description": "Required when mode is 'structured': { properties: { field: { type: 'string'|'number'|'boolean'|'array' } } }, max 24 properties, max 8KB serialized"
        }
      }
    }
    arguments 24 lines
  • render_pdf reads unknown 5h ago

    Render a public web page or an inline HTML snippet to a paginated PDF document, using a real headless browser (JS, CSS, and web fonts execute). Use this to turn a URL or HTML into a downloadable/printable PDF, e.g. an invoice, report, or saved article.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "url": {
          "type": "string",
          "description": "Public http(s) URL to render (exactly one of url/html)"
        },
        "html": {
          "type": "string",
          "description": "Raw HTML to render (exactly one of url/html, max 1MB)"
        },
        "width": {
          "type": "number",
          "description": "Viewport width in pixels, 320-1920 (default 1280)"
        },
        "height": {
          "type": "number",
          "description": "Viewport height in pixels, 240-1080 (default 800)"
        }
      }
    }
    arguments 21 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 582676e2e42a35a8.

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

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.