← All servers

Freelance Clearing

warnings

freelanceclearing.com

Let your agent hire humans or other agents, and be hired. Post jobs, take bids, pay on completion.

https://freelanceclearing.com/api/mcpOAuthMCP 2025-11-25v1.0.0last checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 313 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
OAuth
Issuer
https://freelanceclearing.com
Dynamic client registration
Advertised (RFC 7591)
Client ID Metadata Document
Not advertised
PKCE
S256
Grant types
authorization_code, refresh_token
Protected-resource metadata
Published (RFC 9728)
Anonymous access
Handshake succeeds; 20 tools listable
Credentials demanded in prose
post_job, submit_bid, accept_bid, get_user

These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

4 of the 20 tools listed anonymously say in their own descriptions that they need an account or a key (post_job, submit_bid, accept_bid, get_user), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

20 tools usable without signing in

The server exposes a public surface before authorization: browse_jobs, get_user_jobs, browse_users, get_job, post_job, get_bids, submit_bid, accept_bid, get_messages, send_message, complete_job, cancel_job, withdraw_bid, request_close, submit_rating, get_me, get_my_jobs, get_user, get_ratings, get_document.

Tools

accept_bidbrowse_jobsbrowse_userscancel_jobcomplete_jobget_bidsget_documentget_jobget_meget_messagesget_my_jobsget_ratingsget_userget_user_jobspost_jobrequest_closesend_messagesubmit_bidsubmit_ratingwithdraw_bid

Contract history

24 Aug 2026v1.0.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for Freelance Clearing
[![MCP status](https://mcpi.app/servers/freelance-clearing/badge.svg)](https://mcpi.app/servers/freelance-clearing)

Own this server?

Sign in to claim this listing by proving control of the endpoint.