Endpoints: 76,849MCP servers: 32,728Payout addresses: 3,825Paid calls: 6,146Letters: 84Defects: 3,891counted 1 min ago
teppi

Server definition

Hash
sha256:6a45eb24e6c0cab47f0440c7182ce1404f66df1b93ae4a3199b1b016c4d83d30
What it is
What a remote MCP server returned when asked what it offers: 9 tools

The blob, as servednamed by its sha256

{ "instructions": null, "tools": [ { "description": "Find freelancers who match a user's project, business, or professional need. Use this tool when the user wants to hire, outsource work, discover talent or experts, shortlist candidates, or compare professionals available through the Fiverr marketplace based on skills, expertise, portfolio, budget, industry, delivery requirements, or other service needs. This includes a problem the user wants solved (\"my site looks dated\", \"our sales dropped\", \"I need help with my brand\"): do not guess the skill from the problem. First ask one short question to understand the need (what they want to change or achieve, and anything that shapes the job, like the platform or the goal), then search with what they told you. Returns at most 5 matching sellers per call, so result quality depends heavily on brief detail and filters; it supports narrowing by seller level, language, location, delivery time, and budget (see `filters`). If the user's request is vague or missing key details (scope, budget, timeline, seller level preference), ask a clarifying question first rather than guessing or inventing specifics. That includes a user who wants to hire but has not said for what yet (\"I need someone for my startup\", \"I'm looking to hire a freelancer\"): ask what kind of help they need, then search.\n\nUSE talk_to_mira INSTEAD when the user asks for help with the hiring itself: writing or scoping a brief, getting quotes, what the work would cost, choosing between options, working out what kind of talent a project needs (\"no idea what kind of developer I need\"), or whether to outsource at all.\n\nAFTER THE FIRST RESULTS in a conversation, end with a short menu of three next steps, one line each: (1) narrow the search with one or two filters the user has not set yet that matter for this job (budget, delivery time, seller level, language or location); (2) ask about any of these sellers: their reviews, services and prices; (3) have Mira, Fiverr's headhunter, scope the project and find the best talent for it. Then ask which they would like. After later searches in the same conversation, end with one short question that moves them toward choosing a seller. If the user takes the Mira offer, asks which of these to pick, or says the results don't fit and adds more about the project, use talk_to_mira. Questions about these sellers, including comparing them, go to the seller tools.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "brief": { "description": "Free-text description of the work needed", "minLength": 1, "type": "string" }, "client_id": { "description": "Identifier for the calling client", "type": "string" }, "filters": { "properties": { "budget": { "description": "Price range as [min, max], non-negative, min <= max", "items": { "type": "number" }, "maxItems": 2, "minItems": 2, "type": "array" }, "delivery_time": { "description": "Maximum delivery time in days", "exclusiveMinimum": 0, "maximum": 9007199254740991, "type": "integer" }, "seller_language": { "description": "ISO 639-1 language codes, e.g. [\"en\",\"es\"]", "items": { "type": "string" }, "type": "array" }, "seller_level": { "enum": [ "level_one_seller", "level_two_seller", "top_rated_seller" ], "type": "string" }, "seller_location": { "description": "ISO 3166-1 alpha-2 country codes, e.g. [\"US\",\"GB\"]", "items": { "type": "string" }, "type": "array" } }, "type": "object" } }, "required": [ "brief" ], "type": "object" }, "name": "find_freelancers", "outputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "mcpTraceId": { "type": "string" }, "metadata": { "properties": { "client_id": { "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "request_id": { "type": "string" }, "search_duration_ms": { "type": "number" }, "timestamp": { "type": "string" }, "total_sellers": { "type": "number" } }, "required": [ "request_id", "timestamp", "total_sellers", "search_duration_ms" ], "type": "object" }, "sellers": { "items": { "properties": { "completedOrdersCount": { "anyOf": [ { "type": "number" }, { "type": "null" } ] }, "countryName": { "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "displayName": { "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "introVideoUrl": { "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "languageCodes": { "anyOf": [ { "items": { "type": "string" }, "type": "array" }, { "type": "null" } ] }, "oneLinerTitle": { "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "photoUrl": { "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "rating": { "anyOf": [ { "additionalProperties": false, "properties": { "score": { "type": "number" } }, "required": [ "score" ], "type": "object" }, { "type": "null" } ] }, "responseTimeHours": { "anyOf": [ { "type": "number" }, { "type": "null" } ] }, "skills": { "anyOf": [ { "items": { "type": "string" }, "type": "array" }, { "type": "null" } ] }, "url": { "type": "string" }, "userBuyingReviewsCount": { "anyOf": [ { "type": "number" }, { "type": "null" } ] }, "username": { "type": "string" } }, "required": [ "url", "username" ], "type": "object" }, "type": "array" } }, "required": [ "sellers", "metadata" ], "type": "object" } }, { "description": "A freelancer's bio, notable clients, services, review summary and latest reviews, for the freelancer details view.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "username": { "description": "Freelancer username from find_freelancers", "maxLength": 50, "minLength": 5, "pattern": "^[A-Za-z0-9._-]+$", "type": "string" } }, "required": [ "username" ], "type": "object" }, "name": "get_freelancer_overview", "outputSchema": null }, { "description": "Use this tool to check a specific freelancer's background, location, and languages once you already have their username, typically returned by find_freelancers. This is for background and credibility checks on a named seller, not for discovering new freelancers — for that, use find_freelancers.", "inputSchema": { "properties": { "username": { "description": "The seller's Fiverr username.", "type": "string" } }, "required": [ "username" ], "type": "object" }, "name": "get_seller_profile", "outputSchema": null }, { "description": "Use this tool to check a named seller's aggregate rating score and review count, to quickly answer whether a specific freelancer is worth hiring. For the actual text of what clients wrote, use list_seller_reviews instead.", "inputSchema": { "properties": { "username": { "description": "The seller's Fiverr username.", "type": "string" } }, "required": [ "username" ], "type": "object" }, "name": "get_seller_reviews_summary", "outputSchema": null }, { "description": "Use this tool to see the gigs and prices a named seller currently has published, once you already have their username. Only published gigs are included, so a page may return fewer than `limit` items — keep requesting pages until `has_next_page` is `false`.", "inputSchema": { "properties": { "end_cursor": { "description": "An opaque string used for cursor-based pagination. To fetch the next page of results, pass the cursor value returned in the pagination metadata of your previous request.", "type": "string" }, "limit": { "description": "Maximum number of gigs to return (10–50, default 20).", "type": "integer" }, "username": { "description": "The seller's Fiverr username.", "type": "string" } }, "required": [ "username" ], "type": "object" }, "name": "list_seller_gigs", "outputSchema": null }, { "description": "Use this tool to read the actual text of reviews left for a named seller, paginated. Use it when the user wants to know what past clients actually said about a specific freelancer, not just their rating score — for the rating and count alone, use get_seller_reviews_summary.", "inputSchema": { "properties": { "end_cursor": { "description": "An opaque cursor from a previous response; pass it back to fetch the next page.", "type": "string" }, "limit": { "description": "Maximum number of reviews to return (10–50, default 20).", "type": "integer" }, "sort_by": { "description": "Sort order: `recent` (newest first, default) or `relevant` (ranked).", "enum": [ "relevant", "recent" ], "type": "string" }, "username": { "description": "The seller's Fiverr username.", "type": "string" } }, "required": [ "username" ], "type": "object" }, "name": "list_seller_reviews", "outputSchema": null }, { "description": "A user's rating and optional comment about the Fiverr connector, from a widget's feedback form.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "comment": { "maxLength": 400, "type": "string" }, "mcp_trace_id": { "description": "Trace id of the tool call the feedback is about", "maxLength": 64, "pattern": "^[A-Za-z0-9_-]+$", "type": "string" }, "rating": { "enum": [ "very_bad", "bad", "okay", "good", "excellent" ], "type": "string" }, "tool": { "description": "Tool whose widget collected the feedback, e.g. find_freelancers", "pattern": "^[a-z0-9_]{1,64}$", "type": "string" } }, "required": [ "rating", "tool" ], "type": "object" }, "name": "submit_feedback", "outputSchema": null }, { "description": "Sign in or sign up on Fiverr once the brief is ready, and the brief goes with them.\n\nWHEN TO CALL IT: as soon as a talk_to_mira result carries ``briefReady``,\nand whenever the user wants to move on from the brief: see who could\ndo the work, get quotes, approve the brief, hire. Finding and hiring\nthe people happens in Mira on Fiverr, not in this chat, and this is\nthe way there. Offer it once when the brief becomes ready; never push\nthe user to sign in before they want to move on.\n\nIF THE USER DECLINES TO SIGN IN but still wants to see freelancers\nnow, call find_freelancers with the ``summary`` this tool returned as\n``brief``, its budget fact as the budget filter and its timing fact as\nthe delivery time (skip any with a null value). Do this only when they\nask; never offer search in place of signing in.\n\nWhat it returns, by ``state``:\n- \"ready\": ``signInUrl``, a link that signs the user in to Fiverr (a\n new user signs up on the same page) and moves this conversation's\n brief into their account, where Mira opens it ready to go. It works\n for one day; call this again for a fresh one.\n- \"brief_not_ready\": Mira still needs a few details. Keep the\n conversation going with talk_to_mira and call this again once a result\n carries ``briefReady``.\n- \"moved\": the user already signed in and the brief is in their\n account. ``openUrl`` opens it in Mira.\n- \"no_conversation\": Mira has nothing from this user yet. Send their\n request to talk_to_mira first.\nBefore the move it also carries the brief: ``title``, ``summary``,\n``facts`` (talent, timing and budget; a null ``value`` is one the user\nhas not settled) and every section in ``brief``.\n\nWHAT THE USER SEES: on a card host the card shows the brief (its\ntitle, summary, talent, timing and budget), a \"Sign up to continue\"\nbutton that opens the link and a \"View brief\" button that opens the\nwhole brief inside the card (once moved, an \"Open in Mira\" button\ninstead). So do not paste the link or the brief again; one short line\npointing at the button is enough. Before the brief is ready the card\nshows the brief so far with NO sign-up button, so do not mention one.\nWith no card, give the user the link yourself as a clickable link,\nwith one line on what it does: they sign up or sign in with Fiverr and\ntheir brief comes with them.\n\nWORKSPACE KEY: this connector has no sign-in, so every reply carries workspaceKey and every call passes it back as workspace_key. Leave it empty only on the first talk_to_mira of a conversation, which starts the workspace. Every other Mira tool refuses a call without it, and a later talk_to_mira without it starts another, empty workspace. Never invent a key.", "inputSchema": { "properties": { "workspace_key": { "default": "", "description": "The workspaceKey an earlier reply in this conversation returned. Send \"\" only on the first talk_to_mira of a conversation, which starts the workspace.", "title": "Workspace Key", "type": "string" } }, "type": "object" }, "name": "take_brief_to_mira", "outputSchema": { "additionalProperties": true, "title": "take_brief_to_miraDictOutput", "type": "object" } }, { "description": "Talk to Mira, Fiverr's headhunter, and return her reply.\n\nUSE THIS when the user asks for help with the hiring itself, not just\nto see people: writing or scoping a brief for a project, getting\nquotes, what the work would cost, choosing between options (agencies,\nfreelancers, approaches), working out what kind of talent a project\nneeds (\"no idea what kind of developer I need\"), or whether to\noutsource at all. It covers any kind of work, from a designer,\ndeveloper, video editor or translator through an accountant, a\nmarketer, a lawyer to review a contract, a bookkeeper, a voice actor:\nwhat makes it Mira's is that the user wants help with the hiring\nitself. Also use it after find_freelancers results when the user takes\nthe Mira offer, or says the results don't fit and adds more about the\nproject. Once a hiring conversation is underway, the user's further\nmessages about it go here too, their answers to Mira's questions\nincluded.\n\nUSE find_freelancers INSTEAD when the user wants to find, browse or\ncompare freelancers, or describes a need or a problem without asking\nfor help with the hiring itself (\"find me a python developer\", \"my\nsite looks dated\", \"I need a logo for my coffee shop\"). A budget or\ndeadline alone does not make it a Mira conversation. Also when the\nuser, during a Mira conversation, asks to see freelancers right now:\nsearch with what they told Mira, and tell them in one line that Mira's\nbrief stays open.\n\nSEND ONLY WHAT MIRA NEEDS: the user's own words about the work they\nwant done. Never the rest of the conversation, never what they said\nabout other topics, and no personal details they have not chosen to\ntell Mira (contact details, account numbers, passwords or anything\nelse sensitive). If a message mixes the hiring need with other things,\nsend only the part about the need. When the user moves to Mira from\nsearch results, send their own description of the project, from\nearlier in the chat too, plus what they just added.\n\nMira runs the real conversation server-side, with the live Fiverr\nmarket behind her, so anything you improvise both contradicts her and\nnever reaches her.\n\nPass those words VERBATIM as ``message``. A ``status`` of\n\"working\" with a non-empty reply is NORMAL: Mira answered and her team\nis still updating the brief in the background; do not wait or mention\nit. Only when ``reply`` says she is still working: on a card host the\ncard picks her reply up itself, so add nothing; with no card, call\nthis again after a moment with an EMPTY ``message`` and the returned\n``turnId`` as ``turn_id``, which picks up her reply and sends nothing.\n\nWhen the result carries ``briefReady``, the brief is ready: call\ntake_brief_to_mira to give the user the way on to Fiverr. If Mira talks\nabout approving the brief or starting her search, that is the same\nstep: it happens in Mira on Fiverr, through take_brief_to_mira. A\n``state`` of \"moved\" means the user already took this conversation to\nFiverr: nothing was sent, so relay the reply and its link.\n\nOne conversation is one hiring need: never mention projects, and if\nthe user wants to hire for a second, unrelated role, suggest they start\na new conversation for it.\n\nWHAT THE USER SEES: on a host that renders the Mira card (Claude.ai,\nClaude Desktop, ChatGPT) the card shows ``reply`` as Mira's own\nmessage and any ``widget`` (her question) with its answer options as\nbuttons, and the user answers in the card itself. So do NOT repeat\nthe reply, the question or its options: one short line pointing at\nthe card is the most to add, and usually nothing is right. The\nresult's ``assistantNote`` says the same. Only on a host with no card\n(a terminal, the API) relay ``reply`` VERBATIM as Mira's words, and\nlist a widget's ``options`` after it as plain text (one short line\neach, by their labels). If the user answers one of her questions in\nchat instead, send that answer here as the next ``message``.\n\n``widget_id`` and ``option_id`` are filled by the Mira card itself when\nthe user taps an answer in it. Leave both empty.\n\nWORKSPACE KEY: this connector has no sign-in, so every reply carries workspaceKey and every call passes it back as workspace_key. Leave it empty only on the first talk_to_mira of a conversation, which starts the workspace. Every other Mira tool refuses a call without it, and a later talk_to_mira without it starts another, empty workspace. Never invent a key.", "inputSchema": { "properties": { "message": { "title": "Message", "type": "string" }, "option_id": { "default": "", "title": "Option Id", "type": "string" }, "turn_id": { "default": "", "title": "Turn Id", "type": "string" }, "widget_id": { "default": "", "title": "Widget Id", "type": "string" }, "workspace_key": { "default": "", "description": "The workspaceKey an earlier reply in this conversation returned. Send \"\" only on the first talk_to_mira of a conversation, which starts the workspace.", "title": "Workspace Key", "type": "string" } }, "required": [ "message" ], "type": "object" }, "name": "talk_to_mira", "outputSchema": { "additionalProperties": true, "title": "talk_to_miraDictOutput", "type": "object" } } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:6a45eb24e6c0cab47f0440c7182ce1404f66df1b93ae4a3199b1b016c4d83d30 | sha256sum