WIPE Around
REMOTE · AROUND.IW.PE
Local businesses in Israel: search by trade and town, read prices, services and contacts.
Available components
Last scanned (3 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1107 tokens (~553/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% 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
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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://around.iw.pe/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=iw.pe | CN=YE1,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5c0c7615c08acc4dceb82b7162640ea4af6 |
| SANs: *.iw.pe, iw.pe | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of around.iw.pe. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pe. | present | 7981 | 8 | Verified |
| iw.pe. | 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 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://apis.google.com https://www.gstatic.com https://static.cloudflareinsights.com https://connect.facebook.net; frame-src 'self' https://app.icount.co.il https://*.firebaseapp.com https://accounts.google.com https://www.google.com https://www.youtube-nocookie.com https://www.facebook.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; media-src 'self' blob: https://*.cdninstagram.com https://*.fbcdn.net; font-src 'self' data:; connect-src 'self' https:; worker-src 'self' blob:; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://around.iw.pe/mcp | Verified | 200 | |
| http (plaintext) | http://around.iw.pe/mcp | HTTPS enforced | 301 | https://around.iw.pe/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 →
get_business Read one business ~77
Everything WIPE Around shows about one business, as Markdown: trade, town, address, phone, WhatsApp, website, hours, booking, services with prices, and more. Pass its slug or its around.iw.pe/b/… address (from search_businesses).
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | Its slug, or its page address. |
No output schema declared.
No examples provided.
search_businesses Find local businesses in Israel ~975
Search WIPE Around's map of Israel's local businesses (beauty and wellness, health, trades, food, shops, classes…). Write what is wanted in plain Hebrew: the town, the trade, a budget and a time are read from the words, e.g. "קוסמטיקאית ברעננה", "חשמלאי בחולון", "טיפול פנים בחיפה עד 400 השבוע". In English the town, a budget and a time are not read from the words (a business's name and some trade words are), so give the town as city, the trade as kind, and a budget or a time as max or when. A budget (עד 400) or a time (היום or עכשיו for today; מחר, השבוע or בשבוע הקרוב for the week) read only from the words orders the results instead of filtering them. A business known to meet it is lifted (see the order): a published price for it at or under the budget, a free time then in a WIPE booking calendar. One that has not said (no published price for it, or no online booking) stays in the results, and its unconfirmed names what to ask it. One known not to meet it is left out, unless the words give its own name: a higher price, or online booking with no free time then in a WIPE booking calendar. Given as max or when, a budget or a time filters instead. Results come best first, each with its page, phone, WhatsApp, prices and why it fits, and, when it takes bookings through a WIPE site, a booking link and the first free time in its WIPE calendar, if any. Results are ordered by how well they match the words and the trade, how near they are to a location when one is given (for businesses added from the towns around a town asked for, to that town's centre), availability, how complete the page is, reviews and who runs the page. The words can lift a business above that order: one whose own name they give comes first, even outside the trade, the town, the budget or the time asked for; then one that says yes to what they ask of the place (a language spoken there, coming to the home) comes before one that has not; then one known to meet a budget or a time typed in them comes before o…
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | A town's slug or Hebrew name, to filter. |
| kind | string | – | A trade's slug (cosmetics, hair, nails, body, electricians…), to filter. |
| lat | number | – | With lng, a point to measure from: how near a business is counts in the order, and a town in city or in the words no longer filters. The search reads the businesses within about 25 km of it, and any… |
| limit | integer | – | – |
| lng | number | – | With lat. |
| max | integer | – | Highest price in shekels, to filter. |
| q | string | – | What is wanted, in plain Hebrew (the town, the trade, a budget and a time are read from it); in English, a business's name or a trade. |
| when | string | – | Only businesses with a free time in a WIPE booking calendar: later today (today) or in the seven days from today (week), Israel time. Free times are read only from the booking calendars of businesses… |
No output schema declared.
No examples provided.
How do I install the WIPE Around MCP server?
WIPE Around is a hosted endpoint at https://around.iw.pe/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 · around.iw.pe
claude mcp add --transport http pe-iw-around-businesses 'https://around.iw.pe/mcp'
What is the WIPE Around MCP server?
WIPE Around is an MCP server listed in the public MCP registry as pe.iw.around/businesses. Local businesses in Israel: search by trade and town, read prices, services and contacts. This page covers its hosted endpoint (https://around.iw.pe/mcp).
Is the WIPE Around MCP server safe to use?
WIPE Around scores 82 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 WIPE Around MCP server expose?
WIPE Around exposes 2 tools: search_businesses, get_business. Their descriptions and schemas cost roughly 1,052 tokens of context every time the server is loaded.
Does the WIPE Around MCP server require authentication?
No. We connected to WIPE Around without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WIPE Around MCP server still maintained?
WIPE Around 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.