dev.upfork/upfork

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services; files and code on the machine it runs on.

6 of 15 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

• my_accounton 13 other serversreads or searches

  “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.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• search_productson 241 other serversreads or searches

  “Search UpFork (upfork.dev), a marketplace of React + Tailwind CSS components (installed with the shadcn CLI), landing pages, full-stack projects, mobile (React Native) components and desktop software.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  7 inputs

  • querystring or null“What to look for, in plain words.”
  • kindstring or null“Only this kind: component, landing_page, fullstack, mobile, desktop or script.”
  • tagstring or null“Only products with this tag, e.g.”
  • pricestring or null“"free" or "paid".”
  • sortstring or null“relevance (a search's default), featured, newest, popular, price-low or price-high.”
  • pageinteger“Page number, from 1.”
  • pageSizeinteger“Products per page, 1 to 20.”
• buy_linkon 1 other server

  “The page on upfork.dev where the user buys a product or a plan.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs

  • productstring or null“A product's slug.”
  • planstring or null“A plan's slug: pro, studio, agency (see upfork.dev/pricing).”
  • cyclestring or null“For a plan: "month" (the default) or "year".”
• make_resumegenerates contentdescribed as changing data

  “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 at upfork.dev/verify.”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  4 inputs

  • accentstring or null“Its colour: ink (the default), blue, green or plum.”
  • photoboolean“Put the profile's photo on it.”
  • phoneboolean“Put the phone on it (only if their phone isn't kept to themselves).”
  • productsarray or null“Up to 6 of their own products to show, by slug, in order; leave out for the ones their page leads with.”
• support_inboxreads or searches

  “For UpFork's support staff only: the support inbox, as Admin → Support shows it, with what the admin hub lets this person see.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs

  • viewstring or null“waiting (members waiting for an answer, the default), unassigned, mine or all.”
  • querystring or null“Words to find in tickets: a number, a subject, a member's name or e-mail.”
  • pageinteger“Page number, from 1 (20 a page).”
• get_prompton 19 other serversreads or searches

  “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 setup.”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • slugstringrequired“The product's slug.”
• update_profileon 45 other serverscreates or changes datadescribed as changing data

  “Changes the user's UpFork profile: only what's given, the rest stays.”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

  13 inputs

  • displayNamestring or null“The name shown (a developer's products are sold under it).”
  • headlinestring or null“One line under the name, up to 100 characters.”
  • biostring or null“About them, up to 2,000 characters ("" clears it).”
  • locationstring or null“Where they are, e.g.”
  • availabilitystring or null“"open" (open to work), "freelance", "busy", or "" to say nothing.”
  • yearsExperienceinteger or null“Years of experience, 0 to 60.”
  • clearYearsExperienceboolean“true to remove the years of experience.”
  • contactEmailstring or null“An e-mail shown for contact ("" for none).”
  • skillsarray or null“All their skills (replaces the list), up to 30.”
  • languagesarray or null“All the languages they speak (replaces the list), up to 8.”
  • socialLinksarray or null“All their networks (replaces the list).”
  • experiencearray or null“All their work and studies (replaces the list), up to 12.”
  • pinnedProductsarray or null“Up to 4 of their own products their page leads with, by slug, in order (replaces the list).”
• read_ticketreads or searches

  “One support ticket and its whole conversation, by its number (UPF-10427).”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • ticketstringrequired“The ticket's number, like UPF-10427.”
• view_productreads or searches

  “One UpFork product by its slug (from search_products, or its address upfork.dev/products/<slug>): its description, price, license, and for components, landing pages and mobile components its code, fi…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • slugstringrequired“The product's slug, e.g.”
• reply_to_ticketon 3 other serverssends messagesdescribed as changing data

  “Sends a message on the user's own support ticket, in their name (replying reopens a resolved one for 14 days).”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  2 inputs, 2 required

  • ticketstringrequired“The ticket's number, like UPF-10427.”
  • messagestringrequired“The message, up to 10,000 characters.”
• open_ticketon 2 other serversdescribed as changing data

  “Opens a support ticket on UpFork in the user's name, as /support does: UpFork answers on the site and by e-mail.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  4 inputs, 3 required

  • topicstringrequired“orders, account, selling, product (a product they have), broken (something on UpFork doesn't work) or other.”
  • subjectstringrequired“A short subject, 3 to 140 characters.”
  • messagestringrequired“What happened and what they need, up to 10,000 characters.”
  • productstring or null“The product it's about, by slug (from search_products or its page's address), if any.”
• install_productdescribed as changing data

  “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 components it needs, the CSS for the glob…”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • slugstringrequired“The product's slug, from search_products or its address upfork.dev/products/<slug>.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.