SideQuest
REMOTE · SIDEQUESTPAYS.COM
Hire verified local people for real-world tasks. Paid upfront, released on approved photo proof.
Available components
Last scanned (2 hours ago)
Scores higher than 14% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Workflow Automation
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 5 Nov 26 −30
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Nov 26 +3
- Authorization: Authorisation not fully verified: this server exposes a tool marked destructive (approve_quest) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. security
- Tool “approve_quest” is now declared destructive security
- Tool “cancel_quest” is now declared destructive security
- Schema quality: 95 → 107 ▼ functional
- Tool coverage: 58% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- Server version: 0.2.0 → 0.3.0 functional
- “approve_quest” reworded the description of “quest_id” cosmetic
- “approve_quest” reworded the description of “rating” cosmetic
- “cancel_quest” reworded the description of “quest_id” cosmetic
- “create_quest” reworded the description of “details” cosmetic
- “create_quest” reworded the description of “reward_usd” cosmetic
- “create_quest” reworded the description of “zip” cosmetic
- “dispute_quest” reworded the description of “quest_id” cosmetic
- “dispute_quest” reworded the description of “reason” cosmetic
- “get_quest” reworded the description of “quest_id” cosmetic
- “list_quests” reworded the description of “limit” cosmetic
- “list_quests” reworded the description of “status” cosmetic
- “set_webhook” reworded the description of “url” cosmetic
- 3 Nov 26 58
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 5 Nov 2026 · Probed https://sidequestpays.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sidequestpays.com | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 1c167b418a26e0640e25ca3603241420 |
| SANs: sidequestpays.com, www.sidequestpays.com, *.www.sidequestpays.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sidequestpays.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sidequestpays.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://sidequestpays.com/.well-known/oauth-protected-resource/mcp", scope="quests"
Bearer resource_metadata="https://sidequestpays.com/.well-known/oauth-protected-resource/mcp", scope="quests"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://sidequestpays.com/.well-known/oauth-protected-resource/mcp", scope="quests" |
Protected resource metadata
| Document | https://sidequestpays.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://sidequestpays.com/mcp |
| Authorisation server | https://sidequestpays.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sidequestpays.com/mcp | Auth required | 401 | |
| http (plaintext) | http://sidequestpays.com/mcp | Inconclusive | 401 |
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_quest ~101
Approve a submitted quest after checking its proof. This releases the secured reward to the quester. Optionally rate the quester 1 to 5. Submitted quests not approved or disputed within 72 hours are approved automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| quest_id | string | yes | The quest id returned by create_quest, like q_abc123. |
| rating | number | – | Optional rating of the quester, 1 (poor) to 5 (excellent). |
No output schema declared.
No examples provided.
cancel_quest ~55
Cancel a quest before a quester claims it. Paid quests are refunded in full. Claimed quests cannot be cancelled.
| Name | Type | Req | Description |
|---|---|---|---|
| quest_id | string | yes | The quest id returned by create_quest, like q_abc123. |
No output schema declared.
No examples provided.
create_quest ~356
Post a paid real-world quest for a verified human quester near a location. If your prepaid balance covers the reward plus the 20% fee, it is paid instantly and opens to nearby questers right away. Otherwise it returns a checkout_url a person must pay first (use funding: 'balance' to fail instead). Use for tasks only a person on site can do. Account creation, social media posting, reviews, CAPTCHAs, and anything illegal are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional 2-letter ISO code. For remote quests, only questers in this country can claim it (for example NG for a quest needing local knowledge of Nigeria). |
| details | object | – | Step-by-step instructions shown to the quester. |
| funding | string | – | auto (default): use balance if it covers the total, else return a checkout_url. balance: only use balance, error if short. checkout: always return a checkout_url. |
| language | string | – | Language needed, like Spanish or Yoruba. Required for translation quests. |
| lat | number | – | Latitude where the quest happens. Required for in-person templates, ignored for remote ones. |
| lng | number | – | Longitude where the quest happens. Required for in-person templates, ignored for remote ones. |
| reward_usd | number | yes | What the quester earns. A 20% platform fee (minimum $2) is added on top. |
| template | string | yes | Quest type from list_templates. |
| title | string | yes | Short, clear instruction, e.g. 'Confirm Joe's Hardware at 12 Main St is open and photograph posted hours'. |
| zip | string | – | Optional ZIP or postal code of the quest location. |
No output schema declared.
No examples provided.
dispute_quest ~82
Dispute a submitted quest whose proof does not meet the instructions. Funds stay held while a SideQuest reviewer decides. Give a specific reason.
| Name | Type | Req | Description |
|---|---|---|---|
| quest_id | string | yes | The quest id returned by create_quest, like q_abc123. |
| reason | string | yes | What the proof is missing or got wrong, specific enough for a reviewer to judge. |
No output schema declared.
No examples provided.
get_balance ~45
Check your prepaid balance, this key's spend caps, and how much it has spent in the last 24 hours. Call before posting quests to know whether they will be paid instantly.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_quest ~68
Get one of your quests by id, including status and, once submitted, the quester's proof (photo URLs, GPS, timestamp, notes). Photo URLs need the same API key.
| Name | Type | Req | Description |
|---|---|---|---|
| quest_id | string | yes | The quest id returned by create_quest, like q_abc123. |
No output schema declared.
No examples provided.
list_quests ~73
List your quests, newest first. Optionally filter by status: draft, open, claimed, submitted, approved, disputed, paid, cancelled, refunded.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum quests to return. Default 50. |
| status | string | – | Only return quests with this status. Omit for all. |
No output schema declared.
No examples provided.
list_templates ~72
List the quest types a person can do for you. In person (needs lat/lng): verify_location, photo_proof, pickup_dropoff, inspect_item. Remote (anyone, anywhere, optionally limited to a country): phone_call, translation, check_ai_output. Call this first to pick the right template.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_webhook ~81
Receive signed HTTPS callbacks when your quests change status (quest.opened, quest.claimed, quest.submitted, quest.paid, quest.disputed, quest.released, quest.refunded, quest.cancelled) instead of polling get_quest. Returns a signing secret once.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Your https endpoint that will receive POSTed quest events. |
No output schema declared.
No examples provided.
How do I install the SideQuest MCP server?
SideQuest is a hosted endpoint at https://sidequestpays.com/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 · sidequestpays.com
claude mcp add --transport http uckhill-sidequest 'https://sidequestpays.com/mcp'
What is the SideQuest MCP server?
SideQuest is an MCP server listed in the public MCP registry as io.github.uckhill/sidequest. Hire verified local people for real-world tasks. Paid upfront, released on approved photo proof. This page covers its hosted endpoint (https://sidequestpays.com/mcp).
Is the SideQuest MCP server safe to use?
SideQuest scores 31 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 SideQuest MCP server expose?
SideQuest exposes 9 tools: list_templates, create_quest, get_balance, get_quest, list_quests, and 4 more. Their descriptions and schemas cost roughly 933 tokens of context every time the server is loaded.
Does the SideQuest MCP server require authentication?
Yes. SideQuest asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the SideQuest MCP server still maintained?
SideQuest is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.