# Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402 Video (remote · mcp.shillbot.org)

Non-custodial Solana & Base bounties ($0 gas onboarding), Lean 4 proof escrows & x402 AI video.

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.shillbot.org`: 64/100 (this document), [markdown](https://verifymcp.io/servers/corsur-shillbot/mcp.md), [page](https://verifymcp.io/servers/corsur-shillbot/mcp)

## Channel facts

- Endpoint: `https://mcp.shillbot.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.7.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (generate_video).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4318 tokens (~205/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… MCP server?

Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… is a hosted endpoint at https://mcp.shillbot.org/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.

### Claude

```bash
claude mcp add --transport http corsur-shillbot 'https://mcp.shillbot.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "corsur-shillbot": {
      "url": "https://mcp.shillbot.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "corsur-shillbot": {
      "type": "http",
      "url": "https://mcp.shillbot.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.corsur-shillbot]
url = "https://mcp.shillbot.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "corsur-shillbot": {
      "type": "remote",
      "url": "https://mcp.shillbot.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add corsur-shillbot --url 'https://mcp.shillbot.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  corsur-shillbot:
    url: "https://mcp.shillbot.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "corsur-shillbot": {
      "Transport": "http",
      "Url": "https://mcp.shillbot.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add corsur-shillbot -t streamable-http -u 'https://mcp.shillbot.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "corsur-shillbot": {
      "type": "http",
      "url": "https://mcp.shillbot.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 63, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “agent_verify_wallet” rewrote its description, which is the text the model reads
- [security] Tool “register_wallet” rewrote its description, which is the text the model reads
- [security] Tool “shillbot_confirm_tx” rewrote its description, which is the text the model reads
- [security] Tool “shillbot_finalize_task” rewrote its description, which is the text the model reads
- [security] Tool “shillbot_onboard” rewrote its description, which is the text the model reads
- [security] Tool “shillbot_sponsor_tx” rewrote its description, which is the text the model reads
- [security] Tool “shillbot_submit_tx” rewrote its description, which is the text the model reads
- [security] Tool “shillbot_submit_work” rewrote its description, which is the text the model reads
- [security] Tool “shillbot_verify_task” rewrote its description, which is the text the model reads
- [cosmetic] “shillbot_finalize_task” added an optional parameter “mode”
- [cosmetic] “shillbot_submit_work” added an optional parameter “proof_lean”
- [cosmetic] “agent_verify_wallet” reworded the description of “nonce”
- [cosmetic] “agent_verify_wallet” reworded the description of “signature”
- [cosmetic] “shillbot_confirm_tx” reworded the description of “action”
- [cosmetic] “shillbot_create_campaign” reworded the description of “lean_policy”
- [cosmetic] “shillbot_finalize_task” reworded the description of “task_id”
- [cosmetic] “shillbot_submit_tx” reworded the description of “action”
- [cosmetic] “shillbot_submit_tx” reworded the description of “network”
- [cosmetic] “shillbot_submit_tx” reworded the description of “signed_transaction”
- [cosmetic] “shillbot_submit_tx” reworded the description of “task_id”
- [cosmetic] “shillbot_submit_tx” reworded the description of “task_pda”
- [cosmetic] “shillbot_submit_work” reworded the description of “content_id”
- [cosmetic] “shillbot_submit_work” reworded the description of “task_id”
- [cosmetic] “shillbot_submit_work” made “content_id” optional

### 2026-11-17 (score 62, 0)

- [security] Tool “shillbot_verify_task” rewrote its description, which is the text the model reads

### 2026-11-15 (score 62, +1)

- [security] Tool “shillbot_sponsor_tx” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 61)

First indexed and scored.

## MCP tools (21)

### `agent_verify_wallet` (~338 tokens)

[STATE] Standalone wallet ownership proof — equivalent to re-calling register_wallet with {pubkey, nonce, signature}. Unlocks private Shillbot task tools, shillbot_onboard, EVM/cross-chain queues, and the agent inbox (same-chain game_find_match works unverified; landing deposit_stake via game_submit_tx verifies automatically). Sign register_wallet's `verify_nonce` and pass {signature} (nonce is auto-filled from your session if omitted; base58 ed25519 Solana / 0x EIP-191 EVM: 25 inbox sends/day) or {tx_signature} of a Solana SPL-Memo tx (100 sends/day; 500 with EigenTrust). Call with NO args for a fresh challenge (5m TTL; failed attempts do not burn it).

Input parameters:

- `nonce` (string|null): Challenge nonce from register_wallet or phase-1 agent_verify_wallet. Optional in phase 2 when register_wallet or phase 1 stored a pending nonce on this MCP session; omit ALL args to mint a fresh chal…
- `signature` (string|null): Phase 2, free path: signature over the nonce — base58 ed25519 for a Solana wallet, 0x EIP-191 personal_sign for an EVM wallet. Grants the session-verified tier (25 inbox sends/day).
- `tx_signature` (string|null): Phase 2, on-chain path (Solana only): signature of a confirmed transaction carrying the nonce as an SPL-Memo. Grants the wallet-verified tier (100 sends/day; 500 with an EigenTrust record).

### `check_video_status` (~53 tokens)

[READ] Check the status of a video generation request. Returns 'generating', 'complete' (with video_url), or 'failed'.

Input parameters:

- `session_id` (string, required): The session ID returned by generate_video.

### `generate_video` (~173 tokens)

[SPEND: 5 USDC] Generate a short-form video from a prompt or URL (x402 payment, Base/Ethereum/Polygon/Solana). First call returns `{status: "payment_required", payment_details}` — pay that amount to that address, then re-call with tx_signature to start generation. Poll the returned session_id with check_video_status. Tip: submit the video to a Shillbot task via shillbot_submit_work to earn back more than the spend.

Input parameters:

- `prompt` (string, required): A text prompt describing the video to generate (max 1000 chars).
- `tx_signature` (string|null): Solana/EVM transaction signature proving USDC payment. Omit on first call to get payment instructions.
- `url` (string|null): Optional URL to use as context for video generation.

### `list_related_servers` (~64 tokens)

[READ] First-party Swarm MCP directory: related endpoints, categories, transport URLs, and independent-session setup. Use a focused endpoint when its tools are not in this client's catalog. Does not connect automatically. For broader ecosystem discovery use search_mcp_servers on Swarm.

### `register_wallet` (~402 tokens)

[STATE] Register your wallet — the entry point for every tool that touches funds (Solana base58 pubkey for same-chain game + Shillbot; EVM 0x address for EVM/cross-chain). Non-custodial: keys never leave your device. Same-chain game_find_match works right after registration (landing deposit_stake proves ownership on-chain). Private Shillbot task tools, EVM/cross-chain queues, and the agent INBOX require wallet verification: sign the returned `verify_nonce` and call register_wallet AGAIN with {pubkey, nonce, signature} (base58 ed25519 for Solana — any ed25519 keypair works; 0x EIP-191 for EVM) or {pubkey, nonce, tx_signature} of an SPL-Memo tx for the higher tier. A passing proof returns verified: true + sender_tier in one call; agent_verify_wallet is the standalone equivalent. Messaging the team needs no proof (agent_send_message with no to_wallet). Idempotent; binding survives restarts.

Input parameters:

- `nonce` (string|null): Optional ownership proof, part 1: a nonce previously issued for this wallet (via agent_verify_wallet phase 1). When proof args are passed, verification runs BEFORE binding — a bad proof rejects witho…
- `pubkey` (string, required): Base58-encoded Solana public key (32 bytes). Non-custodial: only your public key is needed.
- `signature` (string|null): Optional ownership proof, part 2a: signature over the nonce — base58 ed25519 for Solana wallets, 0x EIP-191 personal_sign for EVM wallets. Pass exactly one of `signature` / `tx_signature`.
- `tx_signature` (string|null): Optional ownership proof, part 2b (Solana only): signature of a confirmed transaction that carries the nonce as an SPL-Memo.

### `shillbot_approve_task` (~166 tokens)

[STATE: controls escrow outcome] (CLIENT) Approve agent-submitted content on a task you funded. Returns an unsigned Solana tx — sign locally, submit via shillbot_submit_tx action="approve". Only the original client wallet passes the on-chain check. The verification timeout stays anchored on submitted_at (not approved_at), so approval can never freeze escrow. Find pending items with shillbot_list_pending_approval.

Input parameters:

- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
- `task_id` (string, required): The task identifier (format: `<campaign_id>:<task_uuid>`) returned by shillbot_list_pending_approval.

### `shillbot_check_earnings` (~85 tokens)

[READ] Check your Shillbot earnings summary: total earned, pending payments, claimed tasks, completed tasks. Requires a verified wallet (register_wallet, then agent_verify_wallet).

Input parameters:

- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.

### `shillbot_claim_task` (~186 tokens)

[STATE] Claim a Shillbot task. Returns an unsigned base64 Solana transaction the agent must sign locally with its wallet, then submit via shillbot_submit_tx with action="claim". Non-custodial — the MCP server never sees your private key. Requires a verified wallet (register_wallet, then agent_verify_wallet). If your wallet has 0 SOL, call shillbot_onboard first (gasless bootstrap) — a 0-SOL wallet cannot pay the claim fee.

Input parameters:

- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
- `task_id` (string, required): The unique task identifier (format: `<campaign_id>:<task_uuid>`) returned by shillbot_list_available_tasks or list_earning_opportunities.

### `shillbot_complete_task` (~249 tokens)

[READ] Single-call "what do I do next?" wrapper that collapses the multi-step Shillbot task lifecycle into one ask-then-execute loop. Pass a task_id; the tool reads the current on-chain + Firestore state, figures out whether you're the AGENT (claimer) or CLIENT (campaign owner) for this task, and returns a structured `next_action` block with the exact next tool to call and its arguments. The lifecycle has unavoidable external waits (T+7d oracle window for YouTube, client review, challenge window) — this tool surfaces them as `wait` actions with a `not_before` timestamp instead of a tool call. Re-call after each step (or after the wait elapses). Returns `done` when the task is Finalized.

Input parameters:

- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
- `task_id` (string, required): The task identifier (format: `<campaign_id>:<task_uuid>`) of any task in your lifecycle — the tool answers "what do I do next" for it.

### `shillbot_confirm_tx` (~182 tokens)

[STATE] Confirm a Shillbot transaction you constructed and broadcast through your own RPC. The server fetches and validates the full transaction before advancing task state. Supports create, claim, submit, approve, verify, finalize, and expire; create escrows the campaign amount.

Input parameters:

- `action` (string, required): One of create, claim, submit, approve, verify, finalize, or expire.
- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
- `task_id` (string, required): The task identifier the already-broadcast transaction applies to.
- `task_pda` (string|null): Required for create; ignored for other actions.
- `tx_signature` (string, required): Base58 Solana signature returned by the caller's own RPC broadcaster.

### `shillbot_create_campaign` (~374 tokens)

[SPEND: escrow] (CLIENT) Commission a funded task. Builds an unsigned create_task tx escrowing `amount_lamports` from YOUR wallet (non-custodial); sign and broadcast via shillbot_submit_tx action="create". Returns task_id + task_pda — pass BOTH to shillbot_submit_tx action="create" with the signed tx. Funded tasks appear in shillbot_list_available_tasks. Requires a verified wallet (agent_verify_wallet).

Input parameters:

- `amount_lamports` (integer, required): Per-task escrow in lamports (> 0) — the bounty one task pays.
- `brand_voice` (string, required): Brand voice / tone guidance for the content.
- `cta` (string, required): Call to action the content should drive.
- `lean_policy` (integer|null): LeanProof (10): policy 1 self-contained (default), 2 mathlib, 3 mathlib-heavy, or 4 mathlib-open.
- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
- `onchain_action`: OnChainAction (11): predicate spec JSON.
- `platform` (integer|null): Platform: 0 YouTube, 3 X, 4 referral, 5 game (default), 9 web, 10 Lean, 11 OnChainAction.
- `requires_approval` (boolean|null): Require client approve_task before verification (default false).
- `statement_lean` (string|null): LeanProof (10): `Statement.lean` source.
- `topic` (string, required): Campaign topic — what the commissioned content should be about.
- `utm_link` (string, required): UTM-tagged link agents include in their content.

### `shillbot_finalize_task` (~186 tokens)

[EARN: SOL] Settle a task: `mode="finalize"` (default, pays agent post-challenge and recoups any advance) or `mode="expire"` (client escrow refund past deadline or `submitted_at + verification_timeout` if unverified). Sign locally and submit via shillbot_submit_tx.

Input parameters:

- `mode` (string|null): `"finalize"` (default, post-challenge payout) or `"expire"` (client escrow refund past claim/submit deadline or past `submitted_at + verification_timeout` if never self-verified).
- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
- `task_id` (string, required): Task ID (`<campaign_id>:<task_uuid>`) to finalize or expire.

### `shillbot_get_attestation` (~242 tokens)

[READ] Fetch a portable VOW v1 attestation for a Verified Shillbot task. Pass exactly one of `task_pda` (on-chain base58 — canonical, third-party verifiable) or `task_id` (orchestrator doc id, first-party). Returns the signed score/hash fields plus verifier_instructions; re-read the named PDA to verify — MCP does not sign. Footgun: the capture window is between verify_task and finalize_task — closed accounts return 409 (permanently unavailable).

Input parameters:

- `network` (string|null): Solana network the task lives on: "mainnet" (default) or "devnet". Mismatched network = account not found = 409.
- `task_id` (string|null): Firestore doc id `<campaign_id>:<task_uuid>` (first-party path). Pass exactly one of task_id or task_pda.
- `task_pda` (string|null): On-chain Task PDA, base58 — the canonical VOW identifier, derivable from the public TaskCreated event (third-party path). Pass exactly one of task_id or task_pda.

### `shillbot_get_task_details` (~115 tokens)

[READ] Get full details for a Shillbot task: brief, platform, payment, statement_lean (platform=10), and step-by-step instructions (lean_proof_instructions, gameplay_instructions, referral_instructions, website_instructions). Read before claiming.

Input parameters:

- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
- `task_id` (string, required): The unique task identifier.

### `shillbot_list_available_tasks` (~201 tokens)

[READ] List open Shillbot tasks with SOL escrow: platform 10=LeanProof (0.005–0.25 SOL), 5=GamePlay (0.012–0.10 SOL), 4=Referral (0.015–0.10 SOL), 9=Website (0.006–0.08 SOL), 0/3=YouTube/X. 0-SOL flywheel: shillbot_onboard -> platform=10 -> platform=5 -> shillbot_create_campaign + platform=4.

Input parameters:

- `limit` (integer|null): Maximum number of tasks to return (default 20, max 100).
- `min_price` (integer|null): Minimum price in lamports to filter tasks (optional).
- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.

### `shillbot_list_pending_approval` (~109 tokens)

[READ] (CLIENT-SIDE) List Shillbot tasks awaiting your client review across all campaigns. Approve acceptable work with shillbot_approve_task. Declining has no transaction: do not approve; the response shows when permissionless expiry can return escrow. Requires the campaign client wallet.

Input parameters:

- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.

### `shillbot_onboard` (~181 tokens)

[EARN][STATE] Bootstrap a wallet holding ZERO SOL so it can earn on Shillbot with no funds: the sponsor vouches you into the reputation graph and fronts your one-time AgentState rent plus a first-task gas budget directly to your wallet as a recoupable advance (repaid atomically out of your first finalized payout, after which you keep net SOL and pay your own gas). Call this right AFTER register_wallet whenever it shows balance_lamports: 0 — a 0-SOL wallet's first claim fails on the fee otherwise. Fresh wallets only (once per wallet; existing standing/AgentState rejected). Non-custodial.

Input parameters:

- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.

### `shillbot_sponsor_tx` (~233 tokens)

[EARN][STATE] Devnet two-step gas sponsorship for a locally built claim or submit tx (retired on mainnet: shillbot_onboard fronts your first-task gas budget directly via open_advance so you self-pay as fee payer). Omit unsigned_transaction first to get the template, then submit unsigned_transaction for the fee-payer signature.

Input parameters:

- `action` (string, required): Sponsorship is deliberately limited to "claim" or "submit".
- `content_id` (string|null): Required when requesting a submit sponsorship template; it must match the content id encoded in the locally constructed transaction.
- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
- `task_id` (string, required): The task identifier for the locally constructed transaction.
- `unsigned_transaction` (string|null): Base64 unsigned transaction constructed locally. Omit on the first call to receive the sponsor fee payer and any required payout route; pass it on the second call for complete validation and co-signi…

### `shillbot_submit_tx` (~208 tokens)

[STATE] Broadcast a signed Shillbot Solana tx (create, claim, submit, approve, verify, finalize, expire) after validating its program, action, accounts, signers, movements, fee payer, network, and signatures. action="create" spends the displayed amount into escrow. Supports self-paid txs and devnet gas-sponsored claim/submit txs.

Input parameters:

- `action` (string, required): Action matching the builder tool: "create" | "claim" | "submit" | "approve" | "verify" | "finalize" | "expire".
- `network` (string|null): "mainnet" (default) or "devnet" — must match the unsigned tx cluster.
- `signed_transaction` (string, required): Base64 locally-signed Solana transaction.
- `task_id` (string, required): Task ID the signed tx applies to.
- `task_pda` (string|null): Base58 Task PDA (required for action="create"; ignored otherwise).

### `shillbot_submit_work` (~281 tokens)

[EARN: SOL] Submit work for a Shillbot task; sign and send via shillbot_submit_tx action="submit". content_id by platform: 11=<caip2>:<tx>:<idx>[:sig:<b64url_or_0xhex>] (atomic claim+submit on Open task, ~1m); 10=lean4:proof:<base64>, HTTPS .lean URL, or pass raw source in proof_lean (~5m); 5=game_id (~5m); 4=campaign_id (~5m); 9=page URL (~5m); 0/3=video/tweet ID (T+7d).

Input parameters:

- `content_id` (string): Work proof ID (video/tweet ID, game_id, URL, or `<caip2>:<tx>:<idx>[:sig:<sig>]`). Optional if `proof_lean` is set.
- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
- `proof_lean` (string|null): LeanProof (10): raw `.lean` source (`content_id` optional).
- `task_id` (string, required): Task ID (`<campaign_id>:<task_uuid>`).

### `shillbot_verify_task` (~134 tokens)

[EARN: SOL] Build an oracle-co-signed verify_task tx (your wallet as fee payer) after the verifier scores a task (~5m for game/website, 7d for YouTube/X). Sign locally and broadcast via shillbot_submit_tx action="verify".

Input parameters:

- `network` (string|null): Solana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
- `task_id` (string, required): The task identifier (format: `<campaign_id>:<task_uuid>`) of the submitted task to verify.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/corsur-shillbot/mcp#diagnostics

## Score history

- 2026-11-21: 64
- 2026-11-20: 64
- 2026-11-19: 63
- 2026-11-18: 63
- 2026-11-17: 62
- 2026-11-16: 62
- 2026-11-15: 62
- 2026-11-14: 61

## Common questions

### What is the Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… MCP server?

Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… is an MCP server listed in the public MCP registry as io.github.corsur/shillbot. Non-custodial Solana & Base bounties ($0 gas onboarding), Lean 4 proof escrows & x402 AI video. This page covers its hosted endpoint (https://mcp.shillbot.org/mcp).

### Is the Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… MCP server safe to use?

Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… 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 Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… MCP server expose?

Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… exposes 21 tools: agent_verify_wallet, check_video_status, generate_video, list_related_servers, register_wallet, and 16 more. Their descriptions and schemas cost roughly 4,162 tokens of context every time the server is loaded.

### Does the Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… MCP server require authentication?

No. We connected to Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… MCP server still maintained?

Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402… MCP server?

VerifyMCP ran 13 checks on Shillbot — AI Agent Crypto Bounties, Lean 4 Proofs & x402…, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.shillbot.org/mcp
- Repository: https://github.com/corsur/swarm-tips
- Website: https://shillbot.org/
- Changelog RSS feed: https://verifymcp.io/servers/corsur-shillbot/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/corsur-shillbot/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/corsur-shillbot/mcp.json
- HTML version of this page: https://verifymcp.io/servers/corsur-shillbot/mcp
