SuVerse MCP server
io.github.sudzikcoin/suverse-agent-assistantsudzikcoinstreamable-httpv1.7.0Scanned
Find local US businesses: what they offer, prices from their own sites, and how to order or book.
15 tools: 1 do something that can't be undone, 5 change things and 9 only read.
- Reads private data · 0
- Reads text others write · 8
- Can send data out · 2
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SuVerse MCP server can do
The SuVerse MCP server is published by the GitHub account sudzikcoin. It has 15 tools. It can do things that cannot be undone, such as sending, paying or publishing (check_availability) and create or change data (5 tools: quote_order, place_order, book_slot, request_to_owner and 1 more), but cannot delete data. 9 tools only read.
8 tools bring in text other people can write (get_offering, get_product, quote_order and 5 more); 2 tools can send data out of your system (check_availability and book_slot).
The fixed checks matched 3 findings (long-description and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.7.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Can't be undone 1Claude Code: ask
check_availabilityOnly for a business whose card shows `live_data` (its items come from its connected Shopify or Square, not from a page read).Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "check_availability" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Only for a business whose card shows `live_data` (its items come from its connected Shopify or Square, not from a page read). For a product: the platform’s stock right now — `state: confirmed | refuted | unknown` (unknown = the platform does not track stock, which is not «no»). For a service on a platform with bookings: the free `slots` between `from` and `to` (default: the next 7 days), each with a `start_at` that book_slot takes as it is — on the business’s own clock with its offset (`timezone` names the zone; `start_at_utc` is the same instant). If the card’s `cannot` lists `book`, the slots are information only and the answer says so. A business without a connection answers `not_connected`. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
Changes things 5Claude Code: ask
book_slot🔴 ACTS FOR THE USER: call it only after the user has explicitly agreed to this exact action (what, where, when, who) — never on your own judgement.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.customer.phone): what the tool writes goes there.
Description, as the server wrote it 🔴 ACTS FOR THE USER: call it only after the user has explicitly agreed to this exact action (what, where, when, who) — never on your own judgement. For a service whose business’s card shows a `book` action with method `connected` and no `book` in its `cannot` (a door the platform refuses for this account is marked there, with the reason, at every sync). Take a `start_at` from check_availability (slots) and the platform books it for the named customer; the answer is the platform’s own status (created = on the calendar awaiting confirmation · confirmed · declined). A time the platform does not offer is an `unavailable` error and nothing is booked. Idempotent by `idempotency_key` like place_order. Get the user’s explicit yes first. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
place_order🔴 ACTS FOR THE USER: call it only after the user has explicitly agreed to this exact action (what, where, when, who) — never on your own judgement.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 🔴 ACTS FOR THE USER: call it only after the user has explicitly agreed to this exact action (what, where, when, who) — never on your own judgement. For a business whose card shows an `order` action with method `connected`. Shopify: returns the shop’s own checkout link with these items and quantities already in the cart (`status: unknown`, `mode: cart`) — no customer data is needed or passed, the buyer gives their details and pays on Shopify, and nothing exists on the shop until they do. Square: an order with a payment link (no customer data either). WhatsApp: a message to the owner (customer phone or email). Returns `order_id`, `status`, `checkout_url` — HAND THE CHECKOUT URL TO THE USER AS IT IS: that page takes the money, SuVerse holds no card and charges nothing. Stock is checked live first on a platform that tracks it; «not in stock» is an `unavailable` error and no order or link is given. Send an `idempotency_key` of your own and keep it for a retry: the same key returns the same answer and the same link (`repeated: true`), never a second one. Lines name offerings by their card id (and `variant_id` when the card lists several). `status`: unknown (a cart link: payment is on the platform’s side) · created (the platform holds it) · pending_owner (WhatsApp) · confirmed · declined · failed. Get the user’s explicit yes before calling this. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
quote_orderPrices ONE cart in the shop's own public cart (Shopify or WooCommerce) to ONE ZIP, with no personal data, and orders nothing: the cart is emptied afterwards.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Prices ONE cart in the shop's own public cart (Shopify or WooCommerce) to ONE ZIP, with no personal data, and orders nothing: the cart is emptied afterwards. Answers the items, delivery options with their prices, the subtotal and what stays unknown (tax and fees at checkout; the delivery date unless the cart names it — `delivery_date` asks for a day). Other platforms answer «quote not available» with the reason and the order link. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
request_statusDelivery (`sent` · `link_given` · `expired` · `failed`) and the owner’s outcome (`declined` · `other_time` + proposal · `available` = free but NOT booked · `confirmed` = booked).1 finding
Why it is in this group
- The name "request_status" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "request_status" says "request": a word for a change.
Description, as the server wrote it Delivery (`sent` · `link_given` · `expired` · `failed`) and the owner’s outcome (`declined` · `other_time` + proposal · `available` = free but NOT booked · `confirmed` = booked). `confirmed: true` only when the owner booked it. `wait_seconds` (optional, default 0 = answer now; at most 45 s are used): waits for the owner and returns as soon as the request is answered or final, otherwise the current status when the wait ends (see `wait.ended`). Waiting is not a promise of an answer, and nothing calls you back afterwards: if it is still waiting, call request_status again later (for example when the person asks). Hanging up does not cancel the request. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
request_to_owner🔴 ACTS FOR THE USER: call it only after the user has explicitly agreed to this exact action (what, where, when, who) — never on your own judgement.Reads text others writeNo findings
Why it is in this group
- The name "request_to_owner" says "request": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 🔴 ACTS FOR THE USER: call it only after the user has explicitly agreed to this exact action (what, where, when, who) — never on your own judgement. For a business that takes requests through SuVerse (a verified owner with Telegram, e-mail or WhatsApp). Sends what, when, how many, which branch and the person’s name and contact. Requires `idempotency_key`: retrying with the same key returns the same request. Answers: `sent` (delivered to the owner), `link_given` (WhatsApp: give `whatsapp_url` to the person — THEY send it; nothing is sent yet), or `no_channel` with the business’s other doors. After it, tell the person it is NOT a booking yet and where the answer will come (`next_steps.tell_the_person`, `next_steps.answer_goes_to`). If you can set reminders, schedule a request_status check (`next_steps.check_again_after` is a pause, not a promised reply time) — and only then say you will check; otherwise tell the person how to ask again. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 9Show 9 read-only tools
find_businessOne business the user NAMED, matched by its name near `location` (default radius 15 miles); typos, word order and punctuation are tolerated.No findings
Why it is in this group
- The name "find_business" says "find": a word for reading.
Description, as the server wrote it One business the user NAMED, matched by its name near `location` (default radius 15 miles); typos, word order and punctuation are tolerated. Not in the catalogue → `name_not_found`, and up to 5 nearby businesses that carry the name's distinctive word (never presented as the business asked for). `intent`, `query`, `needed_by`, `deliver_to` shape the short card the same way as list_cards. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_businessSYNONYM of get_card, kept for agents that already know this name.No findings
Why it is in this group
- The name "get_business" says "get": a word for reading.
Description, as the server wrote it SYNONYM of get_card, kept for agents that already know this name. `transparency`: the SuVerse Transparency rating — how much the business publishes about itself (not the quality of its work), A–D, each item with its source page and read date. Free. One business in full, in the same shape for every trade: who it is (name, trade, address, telephone, e-mail, opening hours, time zone), everything it sells (60 offerings a page, cheapest first; `offerings_page` says how many there are and the next offset), the six actions with their links and `required_fields`, how the thing reaches the buyer (delivery, pickup, on_site, at_customer — with the published area, the fee and the order deadline), and how fresh each part of that is. `live_data` (platform, synced_at) when the shelf is the business’s own connected system: then every offering carries `source: connector` with its variants (each with `inventory`: units in stock as the platform counts them, null = unknown), and an action with method `connected` is taken through place_order / book_slot on this door. Use it when the user asks «can they deliver to me», «are they open now», «what else do they do», or when search_catalog offered a business with nothing listed and the next step is a telephone call. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_card`transparency`: the SuVerse Transparency rating — how much the business publishes about itself (not the quality of its work), A–D, each item with its source page and read date.No findings
Why it is in this group
- The name "get_card" says "get": a word for reading.
Description, as the server wrote it `transparency`: the SuVerse Transparency rating — how much the business publishes about itself (not the quality of its work), A–D, each item with its source page and read date. Free. One business in full, in the same shape for every trade: who it is (name, trade, address, telephone, e-mail, opening hours, time zone), everything it sells (60 offerings a page, cheapest first; `offerings_page` says how many there are and the next offset), the six actions with their links and `required_fields`, how the thing reaches the buyer (delivery, pickup, on_site, at_customer — with the published area, the fee and the order deadline), and how fresh each part of that is. `live_data` (platform, synced_at) when the shelf is the business’s own connected system: then every offering carries `source: connector` with its variants (each with `inventory`: units in stock as the platform counts them, null = unknown), and an action with method `connected` is taken through place_order / book_slot on this door. Use it when the user asks «can they deliver to me», «are they open now», «what else do they do», or when search_catalog offered a business with nothing listed and the next step is a telephone call. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_offeringFree.Reads text others writeNo findings
Why it is in this group
- The name "get_offering" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Free. One offering in full, with ONE live request to the shop asking for that item’s price and stock right now (`live_check`). Call it before you quote a price to a person: a catalogue read yesterday is yesterday’s price. One business is asked at most once every ten minutes however many of its offerings you open, so walking a shop is one request and not twenty; `from_cache` and `checked_at` say which. A price list, a menu or a quote form has no single-item door to ask (`ok: false` with the reason) and the stored reading stands with its date. Hand `action_url` to the user as it is, ref=suverse included. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_productSYNONYM of get_offering, kept for agents that already know this name.Reads text others writeNo findings
Why it is in this group
- The name "get_product" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it SYNONYM of get_offering, kept for agents that already know this name. A «product» is just an offering whose kind is `product`; the same id works in both. Free. One offering in full, with ONE live request to the shop asking for that item’s price and stock right now (`live_check`). Call it before you quote a price to a person: a catalogue read yesterday is yesterday’s price. One business is asked at most once every ten minutes however many of its offerings you open, so walking a shop is one request and not twenty; `from_cache` and `checked_at` say which. A price list, a menu or a quote form has no single-item door to ask (`ok: false` with the reason) and the stored reading stands with its date. Hand `action_url` to the user as it is, ref=suverse included. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
list_cardsEvery business of ONE trade (`niche`: a key from list_niches, exactly) near `location`, default radius 15 miles, 20 a page.1 finding
Why it is in this group
- The name "list_cards" says "list": a word for reading.
Findings
- Info
The description is 4,606 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...thing is sent to an owner, booked, ordered or paid without the user’s permission."
Description, as the server wrote it Every business of ONE trade (`niche`: a key from list_niches, exactly) near `location`, default radius 15 miles, 20 a page. The order is fixed and is not a ranking: independent businesses, then chains, then marketplaces; inside each, by distance (a trade that comes to the customer: published service area first). `query` does NOT filter or reorder businesses: it chooses which ITEM each card shows. To find businesses that have an item, use search_catalog. Each card: id, name, distance, phone, a few items, `next` (one action), and for what you pass — `needed_by`, `max_price`, `deliver_to` — a state: hours give open_then / closed_then / unknown (never a free slot); an item price within the budget is item_price_within_budget (the total is not known until priced). `needed_by`: «today», «tomorrow 19:00», «after 15:00», an interval «tomorrow 08:00 to 17:00», a deadline «by 2026-11-20», a range «this week» — read the same way in every tool. A `niche` that is not a key returns no cards and the variants to choose from. Each card carries `transparency` {grade A–D, have, of, items ✓/✗}: how much the business publishes about itself, NOT quality. You may sort or filter by it; this order does not use it. Trades on the shelf: restaurant (2520) · medical clinic (1227) · auto repair (1111) · insurance agent (1107) · hair salon (1095) · dentist (1076) · lawyer (1037) · oil change (978) · clothing store (903) · massage (890) · accountant (881) · nail salon (782) · hvac (776) · print shop (768) · real estate agent (762) · beauty salon (757) · barber (734) · chiropractor (710) · notary (673) · gas station (663) · appliance repair (589) · grocery (562) · car dealer (560) · storage (548) · optometrist (542) · bakery (537) · bar (530) · landscaping (516) · pharmacy (505) · elder care and home care (461) · daycare (448) · body shop (446) · photographer (440) · pet grooming (433) · pizza (426) · catering (411) · cleaning (409) · event venue (402) · florist (402) · tire shop (393) · auto parts store (389) · hotel (379) · pressure washing (378) · plumber (372) · jewelry (362) · furniture (361) · electrician (355) · pool service (355) · windows and doors (330) · tree service (327) · coffee shop (325) · party rental (319) · towing (316) · roofer (313) · veterinarian (306) · tattoo studio (296) · truck tire service (294) · pest control (293) · car wash (274) · junk removal (272) · movers (271) · liquor store (268) · tutoring (262) · ev charging station (260) · urgent care (256) · window cleaning (248) · truck repair (237) · carpet cleaning (224) · travel agency (214) · painter (191) · physical therapy (190) · ice cream shop (189) · car rental (188) · parking (176) · bike repair (175) · dance studio (169) · fishing charter and boat tours (168) · fuel delivery (167) · jewelry and watch repair (164) · music lessons (160) · dry cleaner (159) · locksmith (154) · handyman (152) · med spa (152) · auto glass (151) · gym (147) · general contractor (146) · shipping and packing store (146) · wedding planner (139) · septic and well service (131) · garage door (124) · dog walking and pet sitting (108) · garden center and nursery (103) · pet boarding (103) · phone repair (101) · mattress (88) · thrift store (87) · yoga (83) · hardware store (75) · boat rental (73) · tailor (68) · bike and jet ski rental (65) · funeral home (60) · medical equipment rental (55) · golf course (53) · driving school (52) · pet store (49) · butcher and seafood market (43) · swim school (30) · meal prep (21) · cinema (20) · shooting range (20) · juice bar (19) · computer repair (18) · kids play center (18) · escape room (17) · tennis and sports courts (17) · bowling and billiards (12) · brewery (9) · kids sports and activities (9) · specialty grocery and farmers market (9) · babysitting and nanny agency (8) · motorcycle repair (8) · taxi and transfer service (8) · local business (6) · other online service (6) · martial arts (5) · shoe repair (4) · online store (3) · food truck (2) · lash and brow studio (2) · museum (2) · services (2) · sporting goods store (2) · aquarium (1) · butcher (1) · furniture store (1) · logistics software (1) · motel (1) · shoe store (1) · store (1) · transportation service (1) · travel booking site (1); known but not scanned anywhere: candle shop, confectionery, garden center, gift shop, medical apparel, party shop, toy store. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_nichesThe trades (niches) this catalogue holds near a place, by key, with how many businesses are inside the radius (default 15 miles).No findings
Why it is in this group
- The name "list_niches" says "list": a word for reading.
Description, as the server wrote it The trades (niches) this catalogue holds near a place, by key, with how many businesses are inside the radius (default 15 miles). Without `niche`: a compact list of keys. With `niche`: that trade in full — its tags, coverage and the conditions its businesses publish. A `niche` that is not a key comes back with `variants` and why (a tag, a similar name, a meaning) — nothing is substituted: pick a key. `detail: "full"` lists every trade in full. Coverage: local businesses in a few US cities — call it and the answer says what was searched. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
order_statusThe status of an `order_id` from place_order or book_slot, asked of the platform again when it is not final (paid?Reads text others writeNo findings
Why it is in this group
- The name "order_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The status of an `order_id` from place_order or book_slot, asked of the platform again when it is not final (paid? confirmed? declined by the owner?). A Shopify cart link answers `unknown` — payment is on Shopify’s side and the shop does not report it here. Free. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
search_catalogSearch by what is wanted (an item, a dish, a service, in any language) near `location`, default radius 15 miles, when the trade is not known.No findings
Why it is in this group
- The name "search_catalog" says "search": a word for reading.
Description, as the server wrote it Search by what is wanted (an item, a dish, a service, in any language) near `location`, default radius 15 miles, when the trade is not known. Each business shows its best-fitting items first; `match.fit` says how well: exact (the thing and every asked property), likely (the thing, a property not stated), property (the thing with another quantity or colour), partial (only its main word), none. `nothing_fitting` says so when nothing does. Conditions you pass come back per business as met / violated / unknown (time: open_then / closed_then / unknown): the item's price is not the total, opening hours are not a delivery time, being near is not being served. No `location` and nothing fitting → an empty list, not unrelated businesses from anywhere. Coverage: local businesses in a few US cities — call it and the answer says what was searched. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:21 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.suverse.io/mcp: tools/list returned 15 tools to an anonymous client, including check_availability (irreversible), quote_order (write), place_order (write), book_slot (write), request_to_owner (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "check_availability" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
- Warnrequest_status
The server marks "request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "request_status" says "request": a word for a change.
- Infolist_cards
The description is 4,606 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...thing is sent to an owner, booked, ordered or paid without the user’s permission."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.7.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http suverse-agent-assistant https://www.suverse.io/mcpclaude mcp add --transport http suverse-agent-assistant https://www.suverse.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__suverse-agent-assistant__list_niches",
"mcp__suverse-agent-assistant__list_cards",
"mcp__suverse-agent-assistant__find_business",
"mcp__suverse-agent-assistant__search_catalog",
"mcp__suverse-agent-assistant__get_card",
"mcp__suverse-agent-assistant__get_offering",
"mcp__suverse-agent-assistant__get_product",
"mcp__suverse-agent-assistant__get_business",
"mcp__suverse-agent-assistant__order_status"
],
"ask": [
"mcp__suverse-agent-assistant__quote_order",
"mcp__suverse-agent-assistant__check_availability",
"mcp__suverse-agent-assistant__place_order",
"mcp__suverse-agent-assistant__book_slot",
"mcp__suverse-agent-assistant__request_to_owner",
"mcp__suverse-agent-assistant__request_status"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as suverse-agent-assistant. Review it before you use it.
Capability tags behind 8 rules
- mcp__suverse-agent-assistant__get_offering untrusted-input
- mcp__suverse-agent-assistant__get_product untrusted-input
- mcp__suverse-agent-assistant__quote_order untrusted-input
- mcp__suverse-agent-assistant__check_availability untrusted-input, outbound
- mcp__suverse-agent-assistant__place_order untrusted-input
- mcp__suverse-agent-assistant__book_slot untrusted-input, outbound
- mcp__suverse-agent-assistant__order_status untrusted-input
- mcp__suverse-agent-assistant__request_to_owner untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.sudzikcoin/suverse-agent-assistant/verify?hash=6638f21539b945c44baa6b459f56b8b1d0aff0c8da470b8c0354e3e394156ad5" | jq -e '.changed == false'Pinned hash 6638f21539b9, from Nov 11, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.sudzikcoin/suverse-agent-assistant/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.sudzikcoin/suverse-agent-assistant)Source: MCP Registry · repository. Synced Nov 11, 2026, 05:17 UTC.
SuVerse MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SuVerse MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 6 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SuVerse MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SuVerse MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: check_availability.
What tools does the SuVerse MCP server have?
- 15 tools: 1 irreversible, 5 write, 9 read. check_availability, quote_order, place_order, book_slot, request_to_owner, request_status, list_niches, list_cards and 7 more.
Does the SuVerse MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SuVerse MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_availability and book_slot.
Has the SuVerse MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.