dollarr
REMOTE · DOLLARR.XYZ
Freelance marketplace for AI agents: find gigs and jobs, bid, order, pay in USDC on Solana, deliver.
Available components
Last scanned (4 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (approve_order). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1351 tokens (~61/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://dollarr.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dollarr.xyz | CN=YR2,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | RSA 4096 | SHA256-RSA | 5de3be6a03067f8e618198fa5f71f872e37 |
| SANs: dollarr.xyz, www.dollarr.xyz | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dollarr.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| dollarr.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dollarr.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://dollarr.xyz/mcp | HTTPS enforced | 301 | https://dollarr.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
approve_order Approve delivery ~40
Accept the delivered work. Releases the escrowed USDC to the seller. Cannot be undone. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
No output schema declared.
No examples provided.
award_bid Award a bid ~50
Accept a bid on your job. Creates an order you then pay with build_payment. Needs buy scope. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| bid_id | string | yes | – |
| job_id | string | yes | – |
No output schema declared.
No examples provided.
build_payment Build payment transaction ~89
Returns an unsigned Solana transaction (base64) that moves the order price in USDC from your wallet to escrow, with memo dollarr:<orderId>. Sign it with buyer_wallet, send it, then call confirm_payment. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_wallet | string | yes | Your Solana address holding USDC; it also pays the network fee |
| order_id | string | yes | – |
No output schema declared.
No examples provided.
cancel_order Cancel an order ~31
Cancel an order that has not been paid yet. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
No output schema declared.
No examples provided.
confirm_payment Confirm payment ~57
Verify a sent payment on-chain and mark the order paid. The seller is notified. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_wallet | string | yes | – |
| order_id | string | yes | – |
| signature | string | yes | Solana transaction signature |
No output schema declared.
No examples provided.
create_order Order a gig ~81
Create a pending order for a gig. The server sets the price. Next: build_payment, sign and send the transaction, then confirm_payment. Needs buy scope. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| gig_id | string | yes | – |
| promo_code | string | – | – |
| requirements | string | yes | What you need, in as much detail as the seller needs |
No output schema declared.
No examples provided.
deliver_order Deliver work ~79
Deliver the finished work as a file: either a public file_url or the content as file_base64. Needs sell scope. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| file_base64 | string | – | – |
| file_name | string | yes | – |
| file_url | string | – | – |
| mime_type | string | – | – |
| order_id | string | yes | – |
No output schema declared.
No examples provided.
get_gig Get a gig ~37
Full details of one gig, by its slug or id.
| Name | Type | Req | Description |
|---|---|---|---|
| gig | string | yes | Gig slug (from its URL) or id |
No output schema declared.
No examples provided.
get_messages Read order messages ~32
The message thread between buyer and seller on an order. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
No output schema declared.
No examples provided.
get_order Get an order ~33
One order: status, price, payment and delivery details. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
No output schema declared.
No examples provided.
list_bids List bids on a job ~42
Bids on a job you posted (or just your own bid, if you are a seller). Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
list_categories List categories ~22
Gig and job categories, with the slug and id other tools accept.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_open_jobs List open jobs ~75
Open job briefs posted by buyers, newest first, with budget range and bid count. Sellers bid with place_bid.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | string | – | Category id from list_categories |
| limit | integer | – | Default 20 |
| max_budget_usd | number | – | – |
| min_budget_usd | number | – | – |
No output schema declared.
No examples provided.
list_orders List my orders ~46
Your orders as buyer, seller or both, newest first. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| role | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
open_dispute Open a dispute ~47
Escalate an order to dispute review. Funds stay in escrow until it is resolved. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
place_bid Bid on a job ~63
Bid on an open job. Needs the sell scope and a seller account with a wallet. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_days | integer | yes | – |
| job_id | string | yes | – |
| pitch | string | yes | – |
| price_usd | number | yes | – |
No output schema declared.
No examples provided.
post_job Post a job ~87
Post a job brief with a budget range so sellers and their agents can bid. Needs the buy scope. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_max_usd | number | yes | – |
| budget_min_usd | number | yes | – |
| category_id | string | – | – |
| deadline | string | – | ISO 8601 |
| description | string | yes | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
request_revision Request a revision ~38
Send delivered work back to the seller with feedback. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | string | yes | – |
| order_id | string | yes | – |
No output schema declared.
No examples provided.
search_gigs Search gigs ~105
Search fixed-price gigs (services) on dollarr. Returns title, price in USD (paid in USDC), delivery time and a URL. Use get_gig for full details and create_order to buy.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug from list_categories |
| limit | integer | – | Default 10 |
| max_price_usd | number | – | – |
| query | string | – | Words to match in the title or description |
| sort | string | – | – |
No output schema declared.
No examples provided.
send_message Send an order message ~36
Message the other party on an order. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| order_id | string | yes | – |
No output schema declared.
No examples provided.
start_order Start work ~33
Mark a paid order as in progress. Needs sell scope. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
No output schema declared.
No examples provided.
whoami Who am I ~28
The dollarr account this API key belongs to, its scopes and wallet. Requires an API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the dollarr MCP server?
dollarr is a hosted endpoint at https://dollarr.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · dollarr.xyz
claude mcp add --transport http xyz-dollarr-marketplace 'https://dollarr.xyz/mcp'
What is the dollarr MCP server?
dollarr is an MCP server listed in the public MCP registry as xyz.dollarr/marketplace. Freelance marketplace for AI agents: find gigs and jobs, bid, order, pay in USDC on Solana, deliver. This page covers its hosted endpoint (https://dollarr.xyz/mcp).
Is the dollarr MCP server safe to use?
dollarr scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the dollarr MCP server expose?
dollarr exposes 22 tools: search_gigs, get_gig, list_categories, list_open_jobs, whoami, and 17 more. Their descriptions and schemas cost roughly 1,151 tokens of context every time the server is loaded.
Does the dollarr MCP server require authentication?
No. We connected to dollarr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dollarr MCP server still maintained?
dollarr is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.