Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Tarteel is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
16
tools declared
remote
at its publisher
—
calls last 7d
What it does
Quran MCP server for translation, tafsir, mutashabihat, recitation playlists, and prayer times.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http tarteel-mcp https://mcp.tarteel.ai/mcp
# 2 — ask your agent for something these tools do
# ayah_mutashabihat, phrase_mutashabihat, ayah_translation and 13 more
Tarteel costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TAAll 1 server
TarteelAI1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http tarteel-mcp https://mcp.tarteel.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Show repeated phrase metadata for one ayah with an interactive display. Use this when: the user asks which phrases in a specific ayah repeat elsewhere; the user needs phrase IDs and counts before calling phrase_mutashabihat.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| surah | integer | yes | Surah number from 1 to 114. |
| ayah | integer | yes | Ayah number within the selected surah. |
| same_surah_only | no | When true, only include repeated phrase matches found in the same surah as the input ayah. |
Show phrase mutashabihat occurrences with an interactive display. Use this when: the user provides phrase text and asks where it appears; the user has a phrase_id (for example from ayah_mutashabihat) and wants all matches.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phrase_id | no | Mutashabihat phrase ID. Provide phrase_id or phrase_text, but not both. | |
| phrase_text | no | Arabic phrase text to search for. Provide phrase_text or phrase_id, but not both. | |
| same_surah_only | no | When true, only include occurrences from the same surah as each matched ayah. |
DEFAULT tool for user-facing translation display. Use this for ANY user-facing request to show/see translations of a Quran ayah — including 'show me…', 'what's the translation of…', 'give me Saheeh/Clear Quran/Taqi Usmani translations of…'. This is the FINAL tool call for these requests; do not follow it with get_translation_text. ONLY skip this widget and use get_translation_text when EITHER (a)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| queries | array | yes | Translation queries. Each query defines an ayah range plus languages or slugs. |
DEFAULT tool for user-facing tafsir display. Use this for ANY user-facing request to show/see tafsir commentary on a Quran ayah — including 'show me the tafsir of…', 'what does Ibn Kathir say about…', 'explain this ayah'. This is the FINAL tool call for these requests; do not follow it with get_tafsir_text. ONLY skip this widget and use get_tafsir_text when EITHER (a) the user explicitly asks for
| Parameter | Type | Required | Notes |
|---|---|---|---|
| queries | array | yes | Tafsir queries. Each query defines an ayah range plus tafsir slugs or languages. |
DEFAULT tool for user-facing Quran search. Use this for ANY user-facing search — 'find ayahs that contain X', 'where does X appear in the Quran', 'search the Quran for X', or similar. This is the FINAL tool call for these requests; do not follow it with search_ayahs_text. Shows matches in an interactive widget the user can browse. Query is Arabic script only (diacritics and punctuation are ignored
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query in Arabic script. Diacritics and punctuation are stripped automatically; matching is diacritic-insensitive and ranked by BM25 relevance. Numeric fragments (e.g. '255') match ayahs with th |
| max_results | integer | no | Maximum number of ayah results to return (1-100, default 20). |
DEFAULT tool for user-facing reciter-listing questions. Use this for ANY user-facing query like 'what reciters are available', 'who can recite for me', 'list Quran reciters'. This is the FINAL tool call for these requests; do not follow it with lookup_reciters. Shows the catalog in an interactive widget the user can browse. ONLY use lookup_reciters instead when EITHER (a) the user explicitly asks
No parameter schema on file.
DEFAULT tool for user-facing tafsir-listing questions. Use this for ANY user-facing query like 'what tafsirs are supported', 'list English tafsirs', 'which tafsir collections do you have'. This is the FINAL tool call for these requests; do not follow it with lookup_tafsirs. Shows the catalog in an interactive widget the user can browse. ONLY use lookup_tafsirs instead when EITHER (a) the user expl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| languages | array | no | Optional ISO 639-1 language code filters (for example ['en', 'ar']). |
DEFAULT tool for user-facing translation-listing questions. Use this for ANY user-facing query like 'what English translations are available', 'list French translations', 'which translators can I choose from'. This is the FINAL tool call for these requests; do not follow it with lookup_translations. Shows the catalog in an interactive widget the user can browse. Use ISO 639-1 codes like 'en', not
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Optional ISO 639-1 language code filter (for example 'en'). Do not pass language names like 'english'. |
| locale | string | no | Optional locale/language code for response localization (for example 'en' or 'ar'). |
Play Quranic ayah audio with an interactive player widget. Use this when: the user asks to play/listen to ayahs. RECITER HANDLING: If the user names a specific reciter (e.g. 'Husary', 'Minshawi', 'Al-Afasy', 'Abdul Basit'), ALWAYS call lookup_reciters first to resolve the exact reciter_id — do not guess the ID. Guessed IDs routinely point at the wrong reciter. If the user doesn't specify a reciter
| Parameter | Type | Required | Notes |
|---|---|---|---|
| queries | array | yes | Audio playlist queries. Each query defines an ayah range and optional reciter. |
| default_reciter_id | integer | no | Default reciter ID used when a query omits reciter_id. |
Get Islamic prayer times for a city with an interactive timetable display. Use this when: the user asks for salah times in a location; the user asks to calculate times with a specific prayer method (for example ISNA or MWL).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | yes | City name for prayer time calculation (for example 'Cairo'). |
| country | string | no | Optional country name to disambiguate city lookup (for example 'Egypt'). |
| method | string | no | Prayer time calculation method (for example 'ISNA', 'MWL', or 'Makkah'). |
INTERNAL/preparatory tool — text-only, no widget rendered. NEVER use as the user-facing answer to a 'what reciters are available' question — use list_reciters for that (the default interactive widget). Use this ONLY when EITHER (a) the user explicitly asks for plain text / raw data / no widget, OR (b) you will chain the result into play_ayahs in the same turn without showing the raw list (e.g. use
No parameter schema on file.
INTERNAL/preparatory tool — text-only, no widget rendered. NEVER use as the user-facing answer to a 'what tafsirs are supported' question — use list_tafsirs for that (the default interactive widget). Use this ONLY when EITHER (a) the user explicitly asks for plain text / raw data / no widget, OR (b) you will chain the result into ayah_tafsir in the same turn without showing the raw list (e.g. reso
| Parameter | Type | Required | Notes |
|---|---|---|---|
| languages | array | no | Optional ISO 639-1 language code filters (for example ['en', 'ar']). |
INTERNAL/preparatory tool — text-only, no widget rendered. NEVER use as the user-facing answer to a 'what translations are available' question — use list_translations for that (the default interactive widget). Use this ONLY when EITHER (a) the user explicitly asks for plain text / raw data / no widget, OR (b) you will chain the result into ayah_translation in the same turn without showing the raw
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Optional ISO 639-1 language code filter (for example 'en'). Do not pass language names like 'english'. |
| locale | string | no | Optional locale/language code for response localization (for example 'en' or 'ar'). |
INTERNAL/preparatory tool — text-only, no widget rendered. NEVER use as the user-facing answer to any 'show me / what's the translation of…' request — use ayah_translation for that (the default interactive widget). Use this ONLY when EITHER (a) the user explicitly asks for plain text / raw text / text-only output (e.g. 'give me just the text', 'no widget'), OR (b) you will chain the result into an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| queries | array | yes | Translation queries. Each query defines an ayah range plus languages or slugs. |
INTERNAL/preparatory tool — text-only, no widget rendered. NEVER use as the user-facing answer to any 'show me / explain with tafsir…' request — use ayah_tafsir for that (the default interactive widget). Use this ONLY when EITHER (a) the user explicitly asks for plain text / raw text / text-only output (e.g. 'give me just the commentary text', 'no widget'), OR (b) you will chain the result into an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| queries | array | yes | Tafsir queries. Each query defines an ayah range plus tafsir slugs or languages. |
INTERNAL/preparatory tool — text-only, no widget rendered. NEVER use as the user-facing answer to a search query — use ayah_search for that (the default interactive widget). Use this ONLY when EITHER (a) the user explicitly asks for plain text / raw results / no widget, OR (b) you will chain the resolved ayah keys into another tool in the same turn (play_ayahs, ayah_tafsir, or ayah_translation) wi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query in Arabic script. Diacritics and punctuation are stripped automatically; matching is diacritic-insensitive and ranked by BM25 relevance. Numeric fragments (e.g. '255') match ayahs with th |
| max_results | integer | no | Maximum number of ayah results to return (1-100, default 20). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tarteel or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 2.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest4a3a60d9036afdbd15a41aba838bf0b65af0455696910a2e68e1da2d93613678
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ayah_mutashabihat | no tags | |
| phrase_mutashabihat | no tags | |
| ayah_translation | no tags | |
| ayah_tafsir | no tags | |
| ayah_search | untrusted-input | untrusted-input: keyword "browse" |
| list_reciters | untrusted-input | untrusted-input: keyword "browse" |
| list_tafsirs | untrusted-input | untrusted-input: keyword "browse" |
| list_translations | untrusted-input | untrusted-input: keyword "browse" |
| play_ayahs | no tags | |
| prayer_times | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lookup_reciters | no tags | |
| lookup_tafsirs | no tags | |
| lookup_translations | no tags | |
| get_translation_text | no tags | |
| get_tafsir_text | no tags | |
| search_ayahs_text | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest4a3a60d9036afdbd
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.0.
2.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Tarteel can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.