pelando-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@pelando-mcp search for deals on smart TVs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
pelando-mcp
MCP server for pelando.com.br, the Brazilian community deal board. It answers the question a price comparator structurally cannot: did the crowd believe this discount?
Pelando's temperature score goes negative when users judge a deal fake or the price inflated before the "promotion". No other Brazilian price source exposes that, and — as of August 2026 — no other MCP server exposes Pelando at all.
See PLAN.md for the full design, the reconnaissance behind it, and the source-selection
decision.
What it is, and what it is not
This is a community deal reader, not a price comparator. Pelando has no product catalogue —
verified four ways, see PLAN.md §2 — so the
server does not pretend otherwise:
It can tell you | It cannot tell you |
What users posted, at what price, from which store | What a product costs on a shelf right now |
Whether the crowd upvoted or downvoted it | Every store selling product X, with prices |
What the comment thread says is wrong with it | A 30/90-day price curve |
Coupon codes and which store has active deals | Product specs, or anything about a product nobody posted |
Coverage is exactly what the community posts. Even mainstream terms legitimately return nothing:
iphone 16 pro currently has zero live promotions against ~99 archived ones. That is a real
answer, not a failure.
Related MCP server: mcp-brazil-marketplaces
Tools
Tool | Purpose |
| Free-text deal search. Weak matches are demoted to |
| Pelando's own feeds, optionally scoped to a community ( |
| One deal by UUID or slug — a pasted |
| The comment thread, where a bad posting gets corrected. |
| The point of the project. The crowd's verdict, with its evidence. |
| Merchant lookup: live promotion counts and top coupons. |
| Literal redeemable codes, with prose masquerading as codes filtered out. |
| The 11 communities — the site's only taxonomy. |
| Liveness. |
assess_deal_quality
Every signal is already in payloads we fetch, so it costs at most one extra request. Real output, against a live deal:
{
"title": "[REEMBALADO] GeForce RTX 5070 OC 12GB",
"verdict": "crowd_rejected",
"temperature": -229,
"price": 4129.0,
"store_name": "Terabyte",
"warnings": [
"Negative temperature (-229). On Pelando that usually means users judged the discount fake,
the price inflated beforehand, or the listing misleading.",
"The title declares this as 'reembalado'. Do not compare it against new-unit prices."
]
}It returns a verdict with its evidence attached, never a bare score. A score invites the calling model to quote it as fact; evidence invites it to explain, and lets you disagree.
Quick start (local, venv)
Requires Python ≥ 3.12.
python3 -m venv venv
./venv/bin/pip install -e ".[dev]"
./venv/bin/pytest -m "not live" # offline, runs against checked-in fixtures
./venv/bin/pelando-mcp # runs the MCP server over stdioEnd-to-end check against the live site:
./venv/bin/python scripts/verify_all_tools.py # writes to data/verify/Docker
Multi-arch images (linux/amd64, linux/arm64) are published on every push to main:
docker pull ghcr.io/gabrielbelli/pelando-mcp:latest
docker run --rm -i -v pelando-mcp-data:/data ghcr.io/gabrielbelli/pelando-mcp:latestOr build locally:
docker compose build
docker compose run --rm pelando-mcpA named volume holds the sqlite cache at /data/cache.sqlite.
Run this from home, not from a cloud host. Cloudflare fronts Pelando and blocks datacentre IP ranges outright — a 403 interstitial on every request,
robots.txtincluded, no matter how honest the User-Agent is. Measured: the identical client returns 200 from a residential connection and 403 from a GitHub Actions runner. So the image is fine on a laptop, home server or NAS, and will not work on a VPS. Treat that as a constraint to respect rather than a puzzle to route around with a proxy — see Politeness.
Wiring into Claude
Docker (recommended)
{
"mcpServers": {
"pelando": {
"command": "docker",
"args": ["run", "--rm", "-i", "-v", "pelando-mcp-data:/data", "ghcr.io/gabrielbelli/pelando-mcp:latest"]
}
}
}Local venv
{
"mcpServers": {
"pelando": {
"command": "/absolute/path/to/pelando-mcp/venv/bin/pelando-mcp"
}
}
}Configuration
Variable | Default | Purpose |
|
| Sent on every request. See below. |
|
| Max requests/sec. |
|
| Token-bucket burst. |
|
| sqlite cache. |
|
| structlog level. |
Politeness, and why Pelando
Pelando was chosen on compliance grounds as much as data grounds. Zoom, Buscapé, Bondfaro, Mercado
Livre and Hardmob all name ClaudeBot / Claude-User / Anthropic-AI under Disallow: / —
Zoom's under a heading reading "Bloqueio de Scrapers de Inteligência Artificial (Proteção do
catálogo e dados de preço)". Pelando's robots.txt is Allow: /, with disallows confined to
logged-in pages, and its Terms of Use carry no anti-crawler clause.
Practically, that means:
The User-Agent identifies us truthfully rather than impersonating Chrome. Cloudflare blocks bot UA strings — including
python-httpx, our own library — but an honest self-identifying UA returns 200. If this server ever becomes a nuisance, the operator can email us instead of blocking us. Don't replace it with a browser string.Cloudflare also blocks by IP range, not only by UA. Datacentre ranges get a 403 interstitial however honest the UA is, which is why this runs from a home connection and why the live contract tests are not in CI. A residential proxy would defeat that block; we don't ship one.
1 req/s, concurrency 1, with aggressive sqlite caching. Measured headroom is much larger; that is not a reason to use it.
robots.txtis fetched at startup and paths are actually evaluated against it.The merchant's own link is surfaced, never Pelando's affiliate redirect. A tool that presents itself as neutral should not silently monetise your click for a third party.
No login, no writes, no background polling, no bulk crawling.
Layout
src/pelando_mcp/
├── server.py # MCPServer entry, registers tools
├── client.py # httpx async, honest UA, token bucket, retries, robots, cache
├── api.py # typed calls; validates params the API would silently ignore
├── models.py # pydantic v2 — nullability mirrors observed live payloads
├── normalise.py # condition detection + relevance filtering
├── quality.py # the crowd-verdict heuristic
└── tools/ # MCP tool registrations
tests/
└── fixtures/ # real captured JSON + HTML for offline parser tests
scripts/
└── verify_all_tools.pyNotes
Data comes from an undocumented internal JSON API. It has no contract and no deprecation policy, so
pytest -m livehits the real endpoints and fails on schema drift. A scraper does not break loudly — it starts returning "no deals found" and lies to you. Run it by hand every so often, from home; if the edge blocks the network it skips rather than fails, because a 403 says nothing about the schema.Deal
statusis maintained by users and moderators, not verified against the merchant. An "active" deal can be long dead at the shop.Titles are free text.
[REEMBALADO],usadoandopen boxare detected and flagged; a silent title is reported asunknowncondition, never as new.Prices are BRL, exclude frete unless
free_shippingis true, and0is a real price (free games).
Licence
BSD 2-Clause — see LICENSE.
Available Tools
9 toolsassess_deal_qualityA
Judge whether the community believes a deal is genuine.
This is what Pelando has that a price comparator does not. It reads the crowd's vote
(temperature, which goes NEGATIVE when users think a discount is fake or the price was
inflated beforehand), the comment reactions, the poster's reputation, the deal's age and
status, and any condition declared in the title.
Returns a verdict WITH its evidence attached, never a bare score — present the reasoning to the user rather than the label alone. It judges community sentiment, not merchant truth: it cannot verify that the price is real or still available.
Inputs: id_or_slug (required), include_comments.
browse_feedB
Browse Pelando's own feeds, optionally scoped to one community.
community must be one of the 11 canonical slugs — there is no finer taxonomy on the site.
For electronics use tech-lover or mundo-gamer. An unknown slug is rejected here rather
than sent, because the API silently ignores it and returns the global feed instead.
Inputs: feed, limit, community, include_expired.
get_dealB
Fetch one deal by UUID or by slug.
A slug works directly, so a URL the user pasted (pelando.com.br/d/<slug>) can be handed
over with just the last path segment.
Inputs: id_or_slug (required).
get_deal_commentsB
Read a deal's comment thread — where the crowd corrects a bad posting.
The thread is the only place a fake discount gets explained; there is no report or flag
field in Pelando's data. Note the upstream endpoint has no pagination and returns the whole
tree at once, so limit truncates locally and truncated tells you when that happened.
Inputs: id_or_slug (required), limit.
get_store_couponsA
Fetch a store's coupon codes.
only_valid_codes drops entries whose code is prose rather than a redeemable code — the
field has been seen holding instructions like "Resgatar cupom abaixo do produto".
Coupons expire silently. Every code is reported with the date it was posted so its age is visible; none of them is guaranteed to still work.
Inputs: store (required), only_valid_codes.
list_communitiesA
List Pelando's 11 communities — the site's only browse taxonomy.
There is no category system beside this: deals carry a bare numeric categoryId with no
label anywhere in the data. tech-lover and mundo-gamer are the electronics ones.
Inputs: refresh.
pingA
Liveness check. Returns server name, version, and runtime config.
Inputs: no named parameters.
search_dealsA
Search deals that Pelando users have posted.
Returns community postings, NOT a catalogue: one merchant per posting, free-text titles, and only products someone chose to post. There is no product database behind this — even mainstream terms can legitimately return nothing.
Pelando's search is token-based and loose ("iphone 16 pro" matches "iPhone 14 Pro ... 16"),
so each result carries a relevance block. With drop_irrelevant the weak matches are
moved to related rather than deleted, so nothing is hidden from you.
Only include_expired and sort are server-side. Every other filter is applied locally
after fetching, so a narrow filter with a small size may return few rows even when more
exist upstream.
Inputs: query (required), kind, page, size, +7 more.
search_storesA
Look up a merchant: its live activity counts and its top coupons.
Matching is loose and substring-based upstream — "amazon" also returns "Amaro" — so results are ranked here by how closely the name matches, but the caller should still check the name before acting on the first row.
promotion_count tells you how many active promotions a store has, but there is no
endpoint anywhere that lists them. To see a store's deals, search a product term and
filter by store.
Inputs: query (required), limit, include_coupons.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct action+resource: search_deals vs browse_feed are separated by query-based vs community-feed retrieval, search_stores vs get_store_coupons split merchant lookup from coupon codes, and get_deal/get_deal_comments/assess_deal_quality are clearly layered. Descriptions explicitly state boundaries and upstream limitations, leaving little room for misselection.
Uniform snake_case verb_noun pattern throughout (search_deals, browse_feed, get_deal, get_deal_comments, assess_deal_quality, search_stores, get_store_coupons, list_communities, ping). Verbs are used consistently and predictably for their intent.
Nine tools is well within the ideal 3-15 range and each one maps to a distinct capability (search, browse, fetch, comments, quality, stores, coupons, taxonomy, liveness). No filler or redundant tools.
The read-only deal-consumption surface is thorough: discovery (search/browse), retrieval (deal/comments), trust assessment, stores, coupons, and taxonomy are all covered. Minor gaps exist—no direct store-deals listing (only a documented workaround) and no pagination for comments beyond local truncation—but agents can work around these.
Related MCP Connectors
MCP server for real-time product search by barcode (EAN, UPC, GTIN) or keyword on ean-search.org
Official MCP server for MAQAMI, a hotel and flight booking platform with 3M+ hotels. Search live hotel rates and flights, look up places, airports and hotel details, then prebook and book. Remote Streamable HTTP endpoint, no API key required.
An MCP server that exposes functionalities to use Zomato's services.
Hosted MCP server for DataLikers — Instagram & TikTok data API. 51 tools: Instagram user search by demographics (gender/age/race/country/city), profiles, bulk lookup, engagement, posts & reels, comments, hashtags, locations, stories, highlights, music, business accounts, top users; TikTok users, videos, comments, hashtags, playlists and top charts. Streamable HTTP, Bearer API key. Free tier: 100 requests on signup at https://datalikers.com/p/1by27bwg
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for Prelo, the Brazilian literary releases aggregator. Enables searching the catalog by month, publisher, or author.-
- AlicenseAqualityDmaintenanceMCP server to search and retrieve public ads from OLX Brasil and Mercado Livre Brasil with automatic anti-bot bypass.41MIT
- AlicenseAqualityDmaintenanceMCP server for Brazilian marketplace product search across Mercado Livre, Shopee, and AliExpress, with automatic x402 micropayments.472 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides access to Brazilian public and commercial data, including CNPJ company info, government procurement (PNCP) searches, and FIPE vehicle pricing, with optional alert registration for new tenders.MIT