
Servidor MCP de Freelance Clearing
Quais servidores MCP são de Freelance Clearing, do registro oficial e encontrados perguntando ao próprio domínio, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.
lido em 2026-10-24
- Nome no registrocom.freelanceclearing/marketplaceverificado no registro MCP
O nome no registro fica sob freelanceclearing.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.
- Estadorespondeverificado em 2026-10-24
- Ferramentas33
- O servidor se chamafreelance-clearing
- Versão do servidor1.0.0
- Versão do protocolo2025-06-18
Em 2026-10-24 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 105 ms.
- As ferramentas fazem todos os casos de uso verificados: post work and accept bids from sellers; send requests on offers of work.
- Verificado em 4 dos 7 dias necessários para julgar a confiabilidade.
Depois de conectar
- Para "post work and accept bids from sellers", a primeira chamada provável é post_job.
- post_job, send_message, cancel_job, update_me, post_offer alteram dados sem login: qualquer pessoa com o endereço pode chamá-las.
Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.
- Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 4 até agora
- O que um agente consegue fazer com ele2 de 2 casos de uso
- Respondeumedindo4 das 7 verificações diárias necessárias para mostrar a porcentagem
- Mediana da primeira resposta156 ms
- Espaço no contexto do agente≈ 12.194 tokensas definições de todas as ferramentas (34), que o agente carrega a cada turno
- Definições das ferramentasA · 100 de 100
- Resultados tipados0 de 34 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez
- Todas as ferramentas passam nas seis verificações.
O que um agente consegue fazer com ele
- consegue · post work and accept bids from sellers
- consegue · send requests on offers of work
- incerto · hold card payment until the job is completed
Cada caso de uso do produto foi perguntado ao Jev junto com a lista de ferramentas deste servidor: um agente consegue fazer isso com essas ferramentas?
Vale conferir
- Ferramentas que alteram dados, em um servidor que responde sem login: post_job, send_message, cancel_job, update_me, post_offer
Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →
browse_jobsList jobs on Freelance Clearing, with the Browse page's Jobs-tab filters and sorts: status, category (who the buyer would prefer, on a job that began as a job post), budget and search. ONE DEFAULT DIFFERS FROM THE PAGE: this defaults to…
get_user_jobsList what one user has posted and bid on -- the same lists the website's profile page shows to anyone. Same shape as get_my_jobs: one merged list of rows tagged role 'poster' or 'bidder', with the same pagination. A bidder row carries…
get_user_offersList the offers one user has posted, active and ended -- the same list their profile's Offers tab shows to anyone. Rows are GET /offers' rows, so a caller that reads the market listing reads this one with no new parsing: each carries the…
browse_usersList the people on Freelance Clearing (equivalent to the Browse page's Users tab), with the same facts a person sees: username, description, join date, rating average and count, completed jobs, jobs posted, jobs bid on, totals for gross…
get_jobFetch full detail for a single job by id, regardless of its status (open, in progress, completed, or cancelled). Two close-request fields: close_requested_at is set while the accepted seller has asked the buyer to close, and is cleared if…
post_jobPost a new job listing, as the authenticated user. Equivalent to the website's "Post a Job" form. Charges a $2 posting fee immediately; requires a saved payment method.
get_bidsList every bid on a job, with each bidder's rating average and count. Bids are listed to everyone, including while the job is open: who bid, when, and whether the bid still stands is public from the moment a bid is placed. The list…
submit_bidSubmit a bid on an open job, as the authenticated user. You can't bid on your own job. You get one bid per job, ever: your bid amount cannot be edited afterwards, and if you withdraw it you cannot bid on that job again. Decide the amount…
accept_bidAccept a specific bid on a job, as that job's buyer. Moves the job to in_progress. Only the job's buyer can do this -- the bidder accepting their own bid is rejected, as is anyone who isn't the buyer. Charges the buyer the full bid…
get_messagesRead the messages for a job. The job's buyer sees every conversation on that job (with every bidder they've messaged); a bidder sees only their own conversation with the buyer, never another bidder's thread. Every message names its sender…
send_messageSend a message on a job to a specific other participant. If you're the buyer, the recipient must be someone who has actually bid on the job. If you're a bidder, the recipient must be the buyer.
complete_jobMark a job as complete, as that job's buyer. Moves the job from in_progress to completed. Only the buyer can do this -- not even the accepted bidder can mark their own job complete. Transfers 90% of the held amount to the seller's own…
cancel_jobCancel a job, either while it's still open (as the buyer only) or while it's in progress (as the buyer or the accepted bidder). A reason is required whenever the job is in progress, or when it's open with one or more existing bids…
withdraw_bidWithdraw your own bid on a job, as the bidder who placed it. Only possible while the job is still open and your bid hasn't been accepted. No reason required. This is permanent and cannot be undone: once you withdraw, you cannot bid on…
request_closeAsk the buyer to close an in-progress job, as the seller working on it. Use this after delivering, when the buyer has gone quiet. It starts a 7-day clock: if the buyer marks the job complete or cancels it, that resolves the job normally…
mark_job_seenRecord that you have seen everything on this job, which clears has_new_messages and has_new_bids for it on get_my_jobs. Call it after reading a job's messages or bids, so the next get_my_jobs tells you what has arrived since rather than…
submit_ratingRate your counterparty on a job that's completed or cancelled. Only the buyer and the accepted bidder can rate each other, only each other (not a third party, not yourself), and only once per job.
get_meGet your own identity and capabilities: user id, username, join date, rating, and whether you can currently post a job or place a bid -- with why not and where to fix it, if not. Also what the key you are using may do: its permissions…
get_my_jobsList jobs you've posted and/or bid on, with pagination. Posted jobs carry bid_count (bids still standing: a withdrawn bid is not counted) and accepted bidder (once one exists); jobs you've bid on carry your own bid and whether it was…
get_my_paymentsWhere your money actually is -- the same ledger the website's Payments page shows you, and the only place this API says what happened AFTER a transfer was created. get_my_jobs tells you a job's share was sent to your Stripe account; this…
get_userFetch a user's public profile by username: description, join date, rating average and count, completed jobs, cancelled jobs (cancellations this person performed -- either party to an in-progress job can cancel it, so it includes jobs they…
get_ratingsRead individual ratings, including the written review text -- not just the average that job results inline. Pass username for every rating that user has received, or add direction 'given' for the ones they left instead. Pass job_id for…
get_documentFetch one of this site's published documents in full, as markdown: Terms of Service, Privacy Policy, About, or Payments & Trust. Read from the files the published pages are generated from, so an agent never has to fetch a web page to…
browse_offersList the standing offers on Freelance Clearing, with the Browse page's Offers-tab filters and sorts: status, starting-price band, search and sort. DEFAULTS TO ACTIVE offers, the ones that take requests, which is the page's default too…
get_offerFetch one offer in full, with the seller's figures and the offer's OWN record: completed_through counts the jobs finished through this listing and transacted_through is the money that moved through it, which are different numbers from the…
get_my_requestsThe requests you have sent and the requests on your own offer, each with its status. Two lists rather than one, because they are two questions: 'sent' is what you asked for, 'received' is what somebody asked of you -- a pending row in…
post_offerPost a standing offer: what you provide and the price to start from. Free, unlike posting a job. Requires a verified email and a completed Stripe Connect payout account -- an offer is a promise to do paid work, and a seller who cannot be…
end_offerStop an offer taking new requests. It stays public with its history, pending requests on it can still be accepted or declined, and jobs already running through it carry on. There is no un-end and no edit: posting a replacement is the way…
send_requestAsk a seller to do something, naming your own amount and how long you expect it to take. Requires a verified email and a saved payment method: a request is a commitment to pay if the seller accepts. NOTHING IS CHARGED NOW -- if this…
accept_requestAccept a pending request on your own offer. CHARGES THE BUYER the amount they named, held in our Stripe account until they mark the job complete, and creates the job: you are its seller and they are its buyer. Requires your payout account…
decline_requestDecline a pending request on your own offer. Nothing is charged, the buyer is told, and any reservation held against their spending limit is released. The request stays as a declined row rather than disappearing, and declining frees the…
withdraw_requestTake back a request you sent, while it is still pending. Only the buyer who sent it can, and only before the seller answers: once a request is accepted, declined or already withdrawn this returns 409 request_not_pending, and whichever of…
report_gapTell the people who run this market what you could not get here. Use it when you wanted to do something and there was no way to do it, when a rule stopped you, or when you could not tell whether the market had what you needed. Needs no…
Como conectar
Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:
{
"mcpServers": {
"marketplace": {
"type": "http",
"url": "https://freelanceclearing.com/api/mcp"
}
}
}Adicionar
Claude Code, no terminal
claude mcp add --transport http freelanceclearing https://freelanceclearing.com/api/mcpAdicionar ao CursorAdicionar ao VS Code
claude.ai, ChatGPT e outros clientes: adicione https://freelanceclearing.com/api/mcp como conector personalizado nas configurações.
Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.
Cookies
Antes de contar esta visita
A análise e a medição de anúncios nos dizem quais páginas e quais dos nossos anúncios cumprem seu papel: Google Analytics e Google Ads, o pixel da Meta, Yandex Metrica e um identificador próprio. Nada é armazenado até você responder, e recusar não muda nada no site.