Skip to content

MCP servers › io.github.sepehr071 › jabama-mcp

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

io.github.sepehr071/jabama-mcp

Unofficial read-only Jabama: villas and stays with exact prices, group tours, events and theater. — the publisher's description

7 of 8 record checks metRead-only · tools listed 2026-10-23Topic: commerce-and-marketing · AI-classifiedversion 0.4.1PythonMITstandard input/output21 tools

Summary

io.github.sepehr071/jabama-mcp is a local MCP server listed in the official MCP registry at version 0.4.1. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 21 tools, 0 resources and 0 prompts.

Record checks

7 of 8 record checks met · 1 does not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #12,981 of 15,112 packages by monthly downloads, tied with 33 others
  • Not ranked by stars: 2 stars (ranked from 10)

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

Key facts

Runs
local package
Transport
standard input/output
Package
PyPI · listed version current
License
MIT
Dependencies
no known high or critical advisories
Repository
public
Tools
21
Described as changing data
0 of 21 toolsAI-classified
Mainly works on
nothing outside itself: it only answers questionsAI-classified
Topic
commerce-and-marketingAI-classified
Last tested
2026-10-23

Add to your client

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.4.1, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-05 (earliest version still in the registry; older removed versions would be earlier)
Version history
7 versions listed, 2026-10-05 to 2026-10-22; 7 in the 90 days before the 2026-10-23 snapshot.
Most recent 7 versions
  • 0.4.1 · 2026-10-22
  • 0.4.0 · 2026-10-18
  • 0.3.0 · 2026-10-16
  • 0.2.2 · 2026-10-13
  • 0.2.1 · 2026-10-12
  • 0.2.0 · 2026-10-11
  • 0.1.0 · 2026-10-05
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
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.4.1 (published 2026-10-22).

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
21tools
0resources
0prompts

What it mainly works on, as our AI model read its tool descriptions: nothing outside itself: it only answers questions.

None of its 21 tools are described as changing anything.

  • jb_find_destinationreads or searches

    “Turn a place name into ready jb_search_stays arguments (keyword and filters).”

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

    1 input, 1 required
    • querystringrequired“Place name in Persian: city, province, area, landmark or complex, e.g.”
  • jb_parse_requestcalculates or converts

    “Turn a free-text stay request into jb_search_stays arguments with Jabama's own AI parser.”

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

    1 input, 1 required
    • textstringrequired“What the user wants, in Persian (English works partly), e.g.”
  • jb_search_staysreads or searches

    “Search Jabama stays (villas, suites, apartments, cottages, eco-lodges) with prices for your dates and guests.”

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

    24 inputs
    • keywordstring“Keyword from jb_find_destination or jb_categories, e.g.”
    • check_instring or null“Check-in date, Gregorian YYYY-MM-DD, e.g.”
    • check_outstring or null“Check-out date, Gregorian YYYY-MM-DD, e.g.”
    • guestsinteger or null“Number of guests; count children too (the site prices every guest), e.g.”
    • typesarray or null“Listing types, e.g.”
    • amenitiesarray or null“Amenity slugs (all required), e.g.”
    • regionsarray or null“Setting, e.g.”
    • citiesarray or null“English city slugs, with keyword 'all', e.g.”
    • provincesarray or null“English province slugs, with keyword 'all', e.g.”
    • zonesarray or null“Zone slugs, with keyword 'all', e.g.”
    • areasarray or null“Area slugs from jb_find_destination, e.g.”
    • poistring or null“Point-of-interest token from jb_find_destination, unchanged.”
    • tagsarray or null“Tags from jb_categories, e.g.”
    • codesarray or null“Only these listing codes (keyword 'all'), e.g.”
    • name_containsstring or null“Words in the listing title (full-text), not a place filter.”
    • roomsinteger or null“Bedrooms, 0 = studio, 5 = five or more.”
    • instant_onlyboolean“Only instantly bookable listings.”
    • min_scoreenum or null“Minimum guest rating: 3, 3.5, 4, 4.5 or 5.”
    • min_priceinteger or null“Lowest price in Toman for the whole stay.”
    • max_priceinteger or null“Highest price in Toman for the whole stay, e.g.”
    • price_per_nightboolean“Treat min_price / max_price as per night (whole-stay price divided by nights).”
    • sortstring“default = Jabama's ranking; cheapest / most_expensive by whole-stay price; rating = weighted by review count.”
    • pageinteger“1-based page number.”
    • limitinteger“Stays per page.”
  • jb_categoriesreads or searches

    “List Jabama's themed stay categories (special pool, A-frame, luxury, cheap, jungle, sea view, pet friendly, last-minute deals, instant booking, ...).”

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

    Takes no inputs.

  • jb_stayreads or searches

    “Get one listing: capacity, beds, rooms, check-in/out times, house rules, amenities (and what is missing), cancellation policy, host, review scores.”

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

    2 inputs, 1 required
    • codeintegerrequired“Listing code from a search or URL, e.g.”
    • full_textboolean“Return long text (reviews, descriptions) unclipped, not cut at …”
  • jb_stay_calendarreads or searches

    “Nightly availability and price of one listing for the next ~76 days, with weekend and holiday flags.”

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

    3 inputs, 1 required
    • codeintegerrequired“Listing code from a search or URL, e.g.”
    • startstring or null“First night to show, Gregorian YYYY-MM-DD; default today, e.g.”
    • nightsinteger“How many nights to show.”
  • jb_price_quotereads or searches

    “Get the exact amount to pay for one listing, dates and guest count (Toman), with per-night lines and the cancellation windows.”

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

    4 inputs, 3 required
    • codeintegerrequired“Listing code from a search or URL, e.g.”
    • check_instringrequired“Check-in date, Gregorian YYYY-MM-DD, e.g.”
    • check_outstringrequired“Check-out date, Gregorian YYYY-MM-DD, e.g.”
    • guestsinteger“Everyone who stays, children included (the quote has no child price), e.g.”
  • jb_similar_staysreads or searches

    “Find alternatives to a listing: similar stays nearby, and other units of the same property.”

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

    5 inputs, 1 required
    • codeintegerrequired“Listing code from a search or URL, e.g.”
    • check_instring or null“Check-in date, Gregorian YYYY-MM-DD, e.g.”
    • check_outstring or null“Check-out date, Gregorian YYYY-MM-DD, e.g.”
    • guestsinteger or null“Number of guests, children included, e.g.”
    • limitinteger“Max similar stays.”
  • jb_reviewsreads or searches

    “Read guest reviews of a listing: stars 1-5, text, when they stayed, nights, and the host's reply.”

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

    5 inputs, 1 required
    • codeintegerrequired“Listing code from a search or URL, e.g.”
    • sortstring“Order.”
    • pageinteger“1-based page number.”
    • limitinteger“Reviews per page.”
    • full_textboolean“Return long text (reviews, descriptions) unclipped, not cut at …”
  • jb_hostreads or searches

    “A host's listings (with ratings and a from-price per night) and guest reviews across all of them, newest first.”

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

    4 inputs, 1 required
    • host_idintegerrequired“Host id (host.host_id from jb_stay), e.g.”
    • pageinteger“1-based page number.”
    • limitinteger“Reviews per page.”
    • full_textboolean“Return long text (reviews, descriptions) unclipped, not cut at …”
  • jb_helpreads or searches

    “Answer questions about Jabama's rules: cancellation and refunds, payment, tax, check-in, host and guest duties.”

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

    3 inputs, 1 required
    • querystringrequired“Topic in Persian, e.g.”
    • limitinteger“Max answers from each source.”
    • full_textboolean“Return long text (reviews, descriptions) unclipped, not cut at …”
  • jb_travel_guidereads or searches

    “Search Jabama's travel magazine (/mag): guides on attractions, best time to visit, how to get there, food.”

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

    3 inputs, 1 required
    • querystringrequired“Destination or topic in Persian, e.g.”
    • limitinteger“Max articles.”
    • text_charsinteger“Characters of article text to include per article; 0 = summary only.”
Show 9 more tools
  • jb_search_eventsreads or searches

    “Search Jabama Events: concerts, shows, workshops, exhibitions and experiences (offroad, boats, riding, food tours) with prices in Toman.”

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

    10 inputs
    • querystring or null“Words, e.g.”
    • citystring or null“City slug from jb_event_filters, e.g.”
    • categorystring or null“Category slug from jb_event_filters, e.g.”
    • kindstring“events = shows, workshops, exhibitions; experiences = tours, boats, riding, food, ...”
    • on_datestring or null“Only events with a session that day, Gregorian YYYY-MM-DD, e.g.”
    • pricestring“Free or paid events.”
    • rated_4_plusboolean“Only events rated 4 or more.”
    • sortstring“cheapest puts free events first.”
    • limitinteger“Events per page.”
    • cursorstring or null“next_cursor of the previous page, to get the next one.”
  • jb_eventreads or searches

    “One event or experience: what it is, exact address, rules, what to bring, price, refundability, sessions with seats left, reviews and the organizer.”

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

    3 inputs, 1 required
    • event_idstringrequired“Event id from jb_search_events, e.g.”
    • max_sessionsinteger“Max sessions (showtimes or days) to list.”
    • full_textboolean“Return long text (reviews, descriptions) unclipped, not cut at …”
  • jb_event_seatsreads or searches

    “Live seat availability of one seated event session: free seats per section and row, with the section prices in Toman.”

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

    1 input, 1 required
    • session_idstringrequired“session_id of a seated session from jb_event, e.g.”
  • jb_theatersreads or searches

    “List theater plays on sale on Jabama Events (Tehran, via the partner Zirbana): venue, address, from-price in Toman, rating, writer, director and cast.”

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

    2 inputs
    • limitinteger“Plays per page.”
    • cursorstring or null“next_cursor of the previous page.”
  • jb_theaterreads or searches

    “One theater play: venue, cast and crew, reviews, showtimes with live seats left; with showtime_id also the free seats by row and their prices.”

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

    3 inputs, 1 required
    • play_idstringrequired“Play id from jb_theaters, e.g.”
    • showtime_idstring or null“A showtime id from this tool's showtimes, e.g.”
    • full_textboolean“Return long text (reviews, descriptions) unclipped, not cut at …”
  • jb_event_filtersreads or searches

    “Cities and categories of Jabama Events with event counts, for the city and category filters of jb_search_events.”

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

    1 input
    • citystring or null“City slug to count categories in, e.g.”
  • jb_search_toursreads or searches

    “Search Jabama group tours (nature, desert, hiking, history, food tours across Iran) with price per person in Toman.”

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

    17 inputs
    • querystring or null“Loose text match over all tour text, e.g.”
    • destination_idinteger or null“Destination place id from jb_tour_places, e.g.”
    • origin_idinteger or null“Start place id from jb_tour_places, e.g.”
    • start_datestring or null“Departure on or after this Gregorian date, e.g.”
    • end_datestring or null“Departure on or before this Gregorian date, e.g.”
    • categorystring or null“Tour category.”
    • tagsarray or null“Tag slugs (any of), e.g.”
    • durationstring“One-day or multi-day trips.”
    • min_priceinteger or null“Lowest price per person in Toman.”
    • max_priceinteger or null“Highest price per person in Toman, e.g.”
    • difficultyarray or null“Difficulty levels (any of).”
    • min_ratingnumber or null“Minimum traveller rating 1-5, e.g.”
    • min_free_seatsinteger or null“Group size that must fit, e.g.”
    • available_onlyboolean“Only tours with an upcoming departure that can be booked.”
    • sortstring“Order; bookable tours always come first.”
    • pageinteger“1-based page number.”
    • limitinteger“Tours per page.”
  • jb_tourreads or searches

    “One group tour: packages, every departure with free seats and the per-person price of each package, day plan, meals, what is included, cancellation rules, guide, operator and reviews.”

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

    3 inputs, 1 required
    • tour_idstringrequired“Tour id (8 digits) from jb_search_tours, e.g.”
    • include_pastboolean“Also list past (completed) departures.”
    • full_textboolean“Return long text (reviews, descriptions) unclipped, not cut at …”
  • jb_tour_placesreads or searches

    “Turn a place name into a Jabama Tours place id for jb_search_tours (destination_id / origin_id).”

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

    3 inputs, 1 required
    • querystringrequired“Place name, e.g.”
    • directionstring“destination = where tours go; origin = where they start.”
    • limitinteger“Max places.”

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 21 tools
Says what it returns
100% of 21 tools
States limits, defaults or errors
8% of 12 tools
Says when to use it
100% of 21 tools
Items covered per tool
3.5 of 4 on average

Counted from the listing

Parameters with a description
100% of 98
Tools with a description
100% of 21
Typical description length
384 characters

The tool set

Counted from the listing

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

AI reading: easy to mix up

No pair found.

The AI items cover 21 of 21 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 PyPI package jabama-mcp

Our sandbox started this package 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. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "jabama-mcp": {
      "command": "uvx",
      "args": [
        "jabama-mcp==0.4.1"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "jabama-mcp": {
      "command": "uvx",
      "args": [
        "jabama-mcp==0.4.1"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "jabama-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "jabama-mcp==0.4.1"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"jabama-mcp","type":"stdio","command":"uvx","args":["jabama-mcp==0.4.1"]}'
Claude Code
claude mcp add --transport stdio jabama-mcp -- uvx jabama-mcp==0.4.1
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- uvx jabama-mcp==0.4.1
  • Optional settings the entry also lists (left out above): JABAMA_MCP_PROXY.
  • This runs the publisher's code on your machine (uvx). Read its README first.
  • 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.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.4.1
Latest stable
0.4.1
Status
current
Withdrawn
no

Source: pypi.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-10-23 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha256-99ca6bd176e530a7a…
License
MIT

Source: the package registry · 2026-10-23.

Usage

Downloads
117 in the last month

Source: pypistats.org · 2026-10-23.

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
Published package can be startedStarted and answeredmatchesour test · 2026-10-23
Version 0.4.1 on PyPIExists and can be installedmatchesPyPI · 2026-10-23
Repository github.com/sepehr071/jabama-mcpOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.sepehr071 · 38 servers
GitHub owner
a personal account (sepehr071)
Repository
github.com/sepehr071/jabama-mcp
Stars
2
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

7 of 8 record checks met · 1 does not apply

  • #12,981 of 15,112 packages by monthly downloads, tied with 33 others
  • Not ranked by stars: 2 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. 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 io.github.sepehr071/jabama-mcp

Answered from the data above

Is io.github.sepehr071/jabama-mcp safe to install?

We do not rate servers as safe or unsafe. 7 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.sepehr071/jabama-mcp been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.sepehr071/jabama-mcp do?

It lists 21 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 and calculate or convert. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.sepehr071/jabama-mcp change or delete data?

None of its 21 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.

Does io.github.sepehr071/jabama-mcp publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 0.4.1, the latest stable release on PyPI.

Where is the source code of io.github.sepehr071/jabama-mcp?

In github.com/sepehr071/jabama-mcp, which opens publicly.

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 “commerce-and-marketing” 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

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. 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 applicable
  17. Consent handling: not applicable
  18. Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

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

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 10
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.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 package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.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 package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.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
Does not apply to this server · 6
  • 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 runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 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 the published package in an isolated sandbox (read-only mode)
  2. 2,297 msConnected after 0 redirects.
  3. Read the inventory: 21 tools, 0 resources, 0 prompts.
  4. 2,817 msFinished: 2 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
no value
The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.
Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
prompts, resources, tools
our test · 2026-10-23
Transport
standard input/output
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
registry · 2026-10-23
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
package registry · 2026-10-23
Integrity hash
declared (sha256)
package registry · 2026-10-23
Signature / provenance
does not apply
PyPI publishes no registry signature or attestation equivalent to npm dist.signatures
Dependency advisories
none known
OSV.dev · 2026-10-23
Popularity
117 downloads a month
package registry · 2026-10-23
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
your machine
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. “io.github.sepehr071/jabama-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.sepehr071/jabama-mcp

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: 7 of 8 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.sepehr071/jabama-mcp)](https://protocolprobe.com/mcp/servers/io.github.sepehr071/jabama-mcp)

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