scrapemole-social
https://social.scrapemole.workers.dev
Registry code: 064f2c5208cd5f31
ScrapeMole Social: Bluesky, Hacker News and Lobsters data for AI agents: every tool is paid per successful call with x402 (USDC on Base). Call a tool without payment to get the x402 PaymentRequired object (isError: true), then retry with the signed payment in params._meta["x402/payment"]. Failed calls are never charged.
- endpoint
- https://social.scrapemole.workers.dev/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is scrapemole-social live?
- Not measured yet: the hub has not completed a check of this server.
- Is scrapemole-social free to use?
- Not measured yet.
- What tools does scrapemole-social have?
- 6 tools: bluesky_search, bluesky_profile, bluesky_feed, hn_search, hn_thread, lobsters_hot.
- Is scrapemole-social safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
last good check
of 6 tools
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 9 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-10-12
counted from three payers (thin, concentrated, shared-payto)
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
bluesky_search unknown never probed
Use for real-time social listening, brand/topic mentions and sentiment research on Bluesky: returns up to 50 public posts matching a query (supports from:handle, #tags, since:/until: dates via Bluesky search syntax) with text, author handle/display name, createdAt, engagement counts, outbound links and a bsky.app URL. Optional cursor for pagination. Paid tool: x402 USDC on Base, $0.003 per successful call; call without payment to receive the PaymentRequired object.
{ "type": "object", "required": [ "q" ], "properties": { "q": { "type": "string", "description": "Search query (Bluesky search syntax)." }, "sort": { "type": "string", "default": "latest", "description": "\"latest\" or \"top\"." }, "limit": { "type": "string", "default": "25", "description": "Max posts (1-50)." }, "cursor": { "type": "string", "description": "Pagination cursor from a previous response." } }, "additionalProperties": false }arguments 27 linesbluesky_profile unknown never probed
Use to look up or verify a Bluesky account: returns DID, handle, display name, description (bio), follower/following/post counts, account creation time, avatar and banner URLs, and labels. Public profile data only. Paid tool: x402 USDC on Base, $0.002 per successful call; call without payment to receive the PaymentRequired object.
{ "type": "object", "required": [ "actor" ], "properties": { "actor": { "type": "string", "description": "Handle (e.g. bsky.app) or DID." } }, "additionalProperties": false }arguments 13 linesbluesky_feed unknown never probed
Use to monitor what a specific Bluesky account has posted recently: returns up to 50 posts (original posts by default, optionally including replies/reposts) with text, time, likes/reposts/replies, outbound links and URLs. Cursor pagination supported. Paid tool: x402 USDC on Base, $0.003 per successful call; call without payment to receive the PaymentRequired object.
{ "type": "object", "required": [ "actor" ], "properties": { "actor": { "type": "string", "description": "Handle or DID." }, "limit": { "type": "string", "default": "20", "description": "Max posts (1-50)." }, "cursor": { "type": "string", "description": "Pagination cursor." }, "filter": { "type": "string", "default": "posts", "description": "\"posts\" (no replies), \"replies\" (posts and replies) or \"all\" (incl. reposts)." } }, "additionalProperties": false }arguments 27 lineshn_search unknown never probed
Use to find what Hacker News says about a product, company, library or topic: searches stories (default) or comments across HN history, sorted by relevance or newest, optionally limited to the last N days or a minimum points threshold. Returns title, URL, author, points, comment count, time, text excerpt and the HN link. Paid tool: x402 USDC on Base, $0.002 per successful call; call without payment to receive the PaymentRequired object.
{ "type": "object", "required": [ "q" ], "properties": { "q": { "type": "string", "description": "Search text." }, "days": { "type": "string", "description": "Only items from the last N days (1-3650)." }, "sort": { "type": "string", "default": "relevance", "description": "\"relevance\" or \"date\"." }, "type": { "type": "string", "default": "story", "description": "\"story\" or \"comment\"." }, "limit": { "type": "string", "default": "20", "description": "Max hits (1-50)." }, "minPoints": { "type": "string", "description": "Minimum points (stories)." } }, "additionalProperties": false }arguments 36 lineshn_thread unknown never probed
Use to read the discussion on a Hacker News post: returns the story (title, URL, points, author, time) and up to N comments in thread order with depth, author, time and plain text (HTML stripped). Good for summarising community reaction to a launch. Paid tool: x402 USDC on Base, $0.003 per successful call; call without payment to receive the PaymentRequired object.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "HN item id (story)." }, "limit": { "type": "string", "default": "100", "description": "Max comments (1-300)." } }, "additionalProperties": false }arguments 18 lineslobsters_hot unknown never probed
Use to see what programmers on Lobsters are discussing right now: returns up to 25 stories from the hottest or newest page, optionally filtered to one tag, with title, URL, score, comment count, tags, submitter and time. Paid tool: x402 USDC on Base, $0.002 per successful call; call without payment to receive the PaymentRequired object.
{ "type": "object", "required": [], "properties": { "tag": { "type": "string", "description": "Optional tag, e.g. rust, ai, security." }, "list": { "type": "string", "default": "hottest", "description": "\"hottest\" or \"newest\"." }, "limit": { "type": "string", "default": "25", "description": "Max stories (1-25)." } }, "additionalProperties": false }arguments 21 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id064f2c5208cd5f31.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/064f2c5208cd5f31/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/064f2c5208cd5f31?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.