UpFork

Name: UpFork
Author: dev.upfork

MCP serverMCP

Search, view and install React + Tailwind CSS components and landing pages from UpFork.

by dev.upforkhomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"upfork","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability49/49 checks ok

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	78 ms	server upfork 1.1.0 · protocol 2025-06-18 · 15 tools
10 h ago	mcp initialize	ok	200	58 ms	server upfork 1.1.0 · protocol 2025-06-18 · 15 tools
16 h ago	mcp initialize	ok	200	56 ms	server upfork 1.1.0 · protocol 2025-06-18 · 15 tools
23 h ago	mcp initialize	ok	200	83 ms	server upfork 1.1.0 · protocol 2025-06-18 · 15 tools
29 h ago	mcp initialize	ok	200	52 ms	server upfork 1.1.0 · protocol 2025-06-18 · 15 tools
2 d ago	mcp initialize	ok	200	162 ms	server upfork 1.1.0 · protocol 2025-06-18 · 15 tools
2 d ago	mcp initialize	ok	200	87 ms	server upfork 1.1.0 · protocol 2025-06-18 · 15 tools
2 d ago	mcp initialize	ok	200	74 ms	server upfork 1.1.0 · protocol 2025-06-18 · 15 tools
3 d ago	mcp initialize	ok	200	101 ms	server upfork 1.1.0 · protocol 2025-06-18 · 15 tools
3 d ago	mcp initialize	ok	200	86 ms	server upfork 1.1.0 · protocol 2025-06-18 · 15 tools

Tools observed via MCP handshake

my_account — The caller's UpFork account: the plan they're on and until when, what's left of its limits today (downloads, AI prompts, demo tabs), and what they bought. The u
search_products — Search UpFork (upfork.dev), a marketplace of React + Tailwind CSS components (installed with the shadcn CLI), landing pages, full-stack projects, mobile (React
buy_link — The page on upfork.dev where the user buys a product or a plan. Nothing is bought here: give the user the link; they open it, sign in, and pay in USDT on TRON t
make_resume — Issues the user's PDF résumé from their developer profile, as Developer panel → PDF résumé does: A4, with UpFork's seal, a number and a QR code anyone can check
support_inbox — For UpFork's support staff only: the support inbox, as Admin → Support shows it, with what the admin hub lets this person see. Members get a refusal: they use m
get_prompt — The AI prompt of an UpFork component or landing page, as its page's copy button gives it: the whole code with instructions for bringing it into a project of any
update_profile — Changes the user's UpFork profile: only what's given, the rest stays. A list given (skills, languages, social links, experience, pinned products) replaces that
read_ticket — One support ticket and its whole conversation, by its number (UPF-10427). The user's own; for UpFork's support staff, any ticket, with its internal notes. Messa
view_product — One UpFork product by its slug (from search_products, or its address upfork.dev/products/<slug>): its description, price, license, and for components, landing p
reply_to_ticket — Sends a message on the user's own support ticket, in their name (replying reopens a resolved one for 14 days). Show the user the message and send it only when t
open_ticket — Opens a support ticket on UpFork in the user's name, as /support does: UpFork answers on the site and by e-mail. Show the user the subject and message and send
install_product — Get an UpFork component or landing page to put into the user's React + Tailwind CSS project: its files (with where each goes), the npm packages and shadcn/ui co
my_tickets — The user's support tickets on UpFork, the latest first: each one's number, subject and state (open: waiting for UpFork; answered: waiting for them; resolved; cl
answer_ticket — For UpFork's support staff only: answers a member's ticket as UpFork, which reaches them on the site and by e-mail. Read the ticket first (read_ticket), write t
my_profile — The user's UpFork profile as they edit it: name, headline, about, skills, languages, networks, experience, the products their page leads with. A developer's is

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrydev.upfork/upfork

first seen 14 d ago · fetched 25 h agoopen ↗

Field history (6 recent events)

14 d ago · declared · summary → "Search, view and install React + Tailwind CSS components and landing pages from UpFork."
14 d ago · declared · description → "Search, view and install React + Tailwind CSS components and landing pages from UpFork."
14 d ago · declared · publisherName → "dev.upfork"
14 d ago · declared · homepageUrl → "https://upfork.dev/docs/mcp"
14 d ago · declared · version → "1.0.0"
14 d ago · declared · protocols → ["mcp"]

UpFork

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from