Skip to content

MCP servers › app.gigxchange › gigxchange

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

app.gigxchange/gigxchange

UK live music: gigs, open mics, venues, musician profiles, GX Index gig rates and member bookings. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: media-and-design · AI-classifiedversion 0.1.0streamable HTTP39 tools

Summary

app.gigxchange/gigxchange is a remote MCP server listed in the official MCP registry at version 0.1.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 39 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Tools
39
Described as changing data
11 of 39 toolsAI-classified
Mainly works on
accounts and data in outside web servicesAI-classified
Topic
media-and-designAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 11 tools whose name or declaration suggests they change data (set_my_availability, toggle_my_favourite, mark_my_notifications_read, set_my_fee_range, respond_to_booking and 6 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 11 tools are described as changing something (set_my_availability, toggle_my_favourite, mark_my_notifications_read, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
0.1.0, published 2026-10-18 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-18 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-22
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.1.0 (published 2026-10-18).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
39tools
0resources
0prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services.

11 of 39 tools are described as changing something (creating, editing, deleting, sending or running).

  • search_gigson 2 other serversreads or searches

    “Gigs HAPPENING across the UK — the public listings directory of shows to go and see (mostly imported, already booked).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • citystring“UK city/town to filter by.”
    • date_fromstring“Earliest gig date, YYYY-MM-DD.”
    • date_tostring“Latest gig date, YYYY-MM-DD.”
    • window_daysinteger“How many days ahead to include (default 180).”
    • limitinteger
    • offsetinteger
  • search_open_gigsreads or searches

    “Member-posted gigs that are OPEN FOR APPLICATIONS — real venues/promoters looking to book an act, future dates only.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • citystring“UK city/town to filter by.”
    • date_fromstring“Earliest gig date, YYYY-MM-DD.”
    • date_tostring“Latest gig date, YYYY-MM-DD.”
    • min_budgetnumber“Only gigs whose stated budget reaches this.”
    • limitinteger
    • offsetinteger
  • search_available_performersreads or searches

    “GigXchange artists and bands open to a booking on a specific date.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs, 1 required
    • datestringrequired“The event date, YYYY-MM-DD.”
    • citystring“UK city/town to filter by.”
    • act_typestring“Optional act size filter.”
    • limitinteger
    • offsetinteger
  • search_open_micsreads or searches

    “Recurring UK open mic nights in a city, with day/frequency, signup method, backline and fee.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    8 inputs, 1 required
    • citystringrequired“UK city or town, e.g.”
    • limitinteger“Rows per page (max 25).”
    • offsetinteger“Row offset for paging (use next_offset from a prior call).”
    • daystring“Optional: "today"/"tonight", "tomorrow", or a weekday (mon..sun).”
    • performer_typestring“Optional: e.g.”
    • has_paboolean“Only nights that list a PA (or full backline) provided.”
    • has_backlineboolean“Only nights that list drums or amps (or full backline) provided.”
    • has_engineerboolean“Only nights that list a sound engineer.”
  • search_venueson 17 other serversreads or searches

    “The public directory of UK grassroots live-music venues in a city (listings, no booking): capacity, backline, PA, engineer and genres booked.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    10 inputs, 1 required
    • citystringrequired“UK city or town, e.g.”
    • limitinteger“Rows per page (max 25).”
    • offsetinteger“Row offset for paging (use next_offset from a prior call).”
    • genrestring“Optional genre the venue books, e.g.”
    • min_capacityinteger“Optional minimum standing capacity.”
    • max_capacityinteger“Optional maximum standing capacity.”
    • has_paboolean“Only venues with a house PA.”
    • has_backlineboolean“Only venues with drums or amps provided.”
    • has_engineerboolean“Only venues with an in-house sound engineer.”
    • daystring“Optional: venues that host live music on "today", "tomorrow" or a weekday (mon..sun), UK time.”
  • search_available_venuesreads or searches

    “GigXchange MEMBER venues open to receiving a gig request on a specific date (free-by-default: open unless the venue marked that date).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs, 1 required
    • datestringrequired“The event date, YYYY-MM-DD.”
    • citystring“UK city/town to filter by.”
    • min_capacityinteger“Optional minimum capacity.”
    • limitinteger
    • offsetinteger
  • get_index_summaryon 1 other serverreads or searches

    “Overview of the GigXchange Index (GX Index), the UK live-music pay index: headline counts, the cities it covers, every published monthly issue (slug, title, url), the latest issue's open datasets (Hu…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_rateson 14 other serversreads or searches

    “What UK acts typically get paid, from the GigXchange Index: median and range (25th-90th percentile) by city, gig type and act size, with sample size and an honest label when a figure is regional, UK-…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • citiesarray“UK cities to look up (1-13), e.g.”
    • use_casestring“Gig type.”
    • band_sizestring“Act size.”
  • get_index_issuereads or searches

    “One published GigXchange Index monthly issue by slug (e.g.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • slugstringrequired“Issue slug, e.g.”
  • get_platform_statson 14 other serversreads or searches

    “Live counts across GigXchange: members by type, venues, open mics, cities, and upcoming gigs listed in the directory (concerts to see, not work to apply for; gigs open for applications are in search_…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_profileon 124 other serversreads or searches

    “Public profile for a GigXchange member by URL slug (display name, bio, genres, location, ratings).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • slugstringrequired“Profile URL slug, e.g.”
  • get_epkreads or searches

    “Public electronic press kit for an artist by URL slug (summary, genres, rating, media counts).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • slugstringrequired“Artist profile/EPK URL slug.”
Show 27 more tools
  • get_gigon 5 other serversreads or searches

    “Full detail for a single directory gig — line-up, address, times, tickets.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • city_slugstringrequired“The city part of the gig's web address, e.g.”
    • slugstringrequired“The gig slug from a search_gigs result.”
  • get_open_micreads or searches

    “Full detail for a single open mic night — schedule, signup, slot length, backline, address.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • slugstringrequired“Open mic slug from a search_open_mics result.”
  • get_venueon 25 other serversreads or searches

    “Full detail for a single grassroots venue — capacity, PA, backline, genres booked, curfew, address.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • slugstringrequired“Venue slug from a search_venues result.”
  • get_eventon 87 other serversreads or searches

    “Public detail for an event hosted on GigXchange by URL slug — date, venue, ticketing, organiser.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • slugstringrequired“Event URL slug.”
  • list_citieson 69 other serversreads or searches

    “UK cities where GigXchange has members, with a member count each.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • list_member_spotlightsreads or searches

    “Index of published Member Spotlight features — long-form profiles of real GigXchange members.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_member_spotlightreads or searches

    “Full editorial text of one Member Spotlight issue by slug, plus a link to the member profile it features.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • slugstringrequired“Spotlight slug from list_member_spotlights.”
  • my_profileon 7 other serversreads or searches

    “The signed-in member's own profile: name, type, bio, location, verification, rating.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • my_unread_messagesreads or searches

    “Count of the member's unread messages.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • my_bookingson 7 other serversreads or searches

    “The member's own bookings from 30 days ago onwards — status, date, venue/event, agreed fee, and which side they are on.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • limitinteger“Rows to return (max 25).”
  • my_invoicesreads or searches

    “Status and amounts of the member's invoices, both directions — each row carries direction: "sent" (issued by the member) or "received" (billed to them).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • list_help_topicsreads or searches

    “The full map of GigXchange's official help centre — every category and the questions it answers.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • categorystring“Optional: only this category (e.g.”
  • search_helpon 8 other serversreads or searches

    “Searches GigXchange's help articles — its own documentation of how the platform works (payments, fees, deposits, cancellations, bookings, profiles, messages, account, what to do when something goes w…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • querystringrequired“What the member wants to know, in their own words.”
    • rolestring“Optional: the member's role (artist, venue, agent, promoter, organiser) so role-specific articles rank first.”
  • get_help_articleon 1 other serverreads or searches

    “The full text of one official GigXchange help article, by slug from a search_help result.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • slugstringrequired“Article slug from search_help.”
  • my_availabilityreads or searches

    “The member's OWN availability for a date window.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • fromstring“Start date YYYY-MM-DD.”
    • tostring“End date YYYY-MM-DD.”
  • check_member_availabilityreads or searches

    “Whether ONE named member (artist or venue, by profile id from search/get_profile) is free on a specific date.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • memberstringrequired“The member's profile SLUG from a search result (e.g.”
    • datestringrequired“The date, YYYY-MM-DD.”
  • set_my_availabilityon 2 other serverscreates or changes datadescribed as changing data

    “Set a date on the member's own GigXchange calendar: unavailable, soft_hold (pencilled), or available (clears the manual entry).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 2 required
    • datestringrequired“The date, YYYY-MM-DD (today to one year ahead).”
    • statusstringrequired“"available" clears the manual entry; the others set it.”
  • toggle_my_favouritecreates or changes datadescribed as changing data

    “Toggle a GigXchange profile (by slug) in the member's favourites list.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • slugstringrequired“Profile slug, e.g.”
  • mark_my_notifications_readcreates or changes datadescribed as changing data

    “Mark all of the member's GigXchange notifications as read.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    Takes no inputs.

  • set_my_fee_rangecreates or changes datadescribed as changing data

    “Update the member's own public fee range (GBP, min and max) shown on their profile — the same field as the app's profile editor.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 2 required
    • min_feenumberrequired“Minimum fee in GBP (0 or more).”
    • max_feenumberrequired“Maximum fee in GBP (must be >= min, capped 100000).”
  • respond_to_bookingon 1 other serverdescribed as changing data

    “Accept or decline a booking offer the member RECEIVED (never one they sent).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    4 inputs, 3 required
    • booking_idstringrequired“The booking id from a my_bookings result.”
    • actionstringrequired
    • expected_feenumberrequired“The fee currently on the booking (GBP).”
    • notestring“Short message to the other party.”
  • counter_bookingdescribed as changing data

    “Propose a different fee on a pending booking offer (posts an amended offer card in chat, retiring the old one).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    4 inputs, 3 required
    • booking_idstringrequired“The booking id from a my_bookings result.”
    • expected_current_feenumberrequired“The fee currently on the booking (GBP).”
    • new_feenumberrequired“The proposed fee (GBP), within 50-200% of the current fee.”
    • notestring“Optional short message to accompany the counter.”
  • make_offeron 6 other serversdescribed as changing data

    “Send a booking offer to another GigXchange member — the recipient gets a pending booking, a notification and an offer card in Messages, exactly as if the member had sent it in the app.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    7 inputs, 4 required
    • recipientstringrequired“The member being offered the booking, by profile SLUG from a search result (e.g.”
    • event_titlestringrequired“What the booking is for, e.g.”
    • event_datestringrequired“Event date, YYYY-MM-DD.”
    • feenumberrequired“The fee offered in GBP (1-100000).”
    • start_timestring“Optional start time, HH:MM.”
    • end_timestring“Optional end time, HH:MM.”
    • notesstring“Optional note to the recipient (max 500 chars).”
  • apply_to_gigon 1 other serverdescribed as changing data

    “Apply the member to an open gig from search_open_gigs (GigXchange member-posted gigs only).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 1 required
    • gig_idstringrequired“The gig id.”
    • notestring“Optional short application message (max 500 chars).”
  • set_my_biocreates or changes datadescribed as changing data

    “Replace the member's own public profile bio (plain text, max 1500 chars).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • biostringrequired“The new bio text.”
  • send_chat_messageon 2 other serverssends messagesdescribed as changing data

    “Send a text message into one of the member's EXISTING GigXchange conversations (no new conversations).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 2 required
    • conversation_idstringrequired“An existing conversation id the member participates in.”
    • bodystringrequired“The message text (plain text, max 2000 chars).”
  • submit_my_invoicedescribed as changing data

    “Send one of the member's own DRAFT settle-privately invoices to its GigXchange recipient (notifies them + posts the invoice card in chat).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • invoice_idstringrequired“The invoice id (drafts appear in my_invoices with status draft).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 39 tools
Says what it returns
97% of 33 tools
States limits, defaults or errors
41% of 39 tools
Says when to use it
100% of 39 tools
Items covered per tool
3.4 of 4 on average

Counted from the listing

Parameters with a description
90% of 87
Tools with a description
100% of 39
Typical description length
236 characters

The tool set

Counted from the listing

Tools
39
Size of the list
about 7,303 tokens for an agent to load (characters ÷ 4)
Naming
39 of 39 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 39 of 39 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.gigxchange.app/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "gigxchange": {
      "url": "https://mcp.gigxchange.app/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "gigxchange": {
      "type": "http",
      "url": "https://mcp.gigxchange.app/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"gigxchange","type":"http","url":"https://mcp.gigxchange.app/mcp"}'
Claude Code
claude mcp add --transport http gigxchange https://mcp.gigxchange.app/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.gigxchange.app/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.gigxchange.app/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about app.gigxchange/gigxchange

Answered from the data above

Is app.gigxchange/gigxchange safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 11 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does app.gigxchange/gigxchange need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has app.gigxchange/gigxchange been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can app.gigxchange/gigxchange do?

It lists 39 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and send messages. We did not call any tool, so this describes the text, not the behaviour.

Can app.gigxchange/gigxchange change or delete data?

11 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “media-and-design” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,558 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 39 tools, 0 resources, 0 prompts.
  4. 3,090 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
not known (our limit)
We could not fetch the website with a plain request. This is our limit, not the site's.
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-23
MCP capability
tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “app.gigxchange/gigxchange: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/app.gigxchange/gigxchange

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/app.gigxchange/gigxchange)](https://protocolprobe.com/mcp/servers/app.gigxchange/gigxchange)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology