Tarteel MCP Server
io.github.TarteelAI/tarteel-mcp-serverTarteelAIstreamable-httpv2.0.0Scanned
Quran MCP server for translation, tafsir, mutashabihat, recitation playlists, and prayer times.
16 tools: 3 change things and 13 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 3 findings, 3 high
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- 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 Tarteel MCP Server can do
The Tarteel MCP Server is published by the GitHub account TarteelAI. It has 16 tools. It can create or change data (3 tools: ayah_translation, ayah_tafsir and play_ayahs), but cannot delete data. 13 tools only read.
1 tool brings in text other people can write (prayer_times).
The fixed checks matched 3 findings, 3 of them high severity (model-directed-text). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 2.0.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.
16 tools
Changes things 3Claude Code: ask
ayah_tafsirDEFAULT tool for user-facing tafsir display.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 plain text / raw text / text-only output, OR (b) the result will be piped into another tool in the same turn without being shown to the user. When in doubt, use this widget. SLUG HANDLING: If the user names a specific tafsir (e.g. 'Ibn Kathir', 'Mokhtasar', 'Maarif-ul-Quran', 'Tazkirul Quran'), ALWAYS call lookup_tafsirs first to resolve the exact slug — do not guess the slug from the name. Guessed slugs fail validation. If the user only specifies a language ('English tafsir', 'Arabic tafsir'), you may pass 'languages' without a slug. Each query must include at least one of languages or tafsir_slugs. Use ayah keys in 'surah:ayah' format (for example '2:255'). Limits: max 20 queries per request and max 50 total ayah+tafsir items.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
ayah_translationDEFAULT tool for user-facing translation display.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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) the user explicitly asks for plain text / raw text / text-only output, OR (b) the result will be piped into another tool in the same turn without being shown to the user. When in doubt, use this widget. SLUG HANDLING: If the user names a specific translator (e.g. 'Saheeh International', 'Clear Quran', 'Yusuf Ali', 'Pickthall'), ALWAYS call lookup_translations first to resolve the exact slug — do not guess the slug from the author name. Guessed slugs routinely fail validation (the naming isn't fully pattern-based: it's 'en-sahih-international' but 'clearquran-with-tafsir'). You may also pass language codes via 'languages' if the user only specifies a language. Each query must include at least one of languages or translations. Use ayah keys in 'surah:ayah' format (for example '2:255'). In queries[].languages use ISO 639-1 codes (for example 'en', 'ur'), not language names. Do not use 'ar'; Arabic translation is unsupported in this tool.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
play_ayahsPlay Quranic ayah audio with an interactive player widget.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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, omit reciter_id entirely so default_reciter_id applies. Use ayah keys in 'surah:ayah' format (for example '1:1'). In each query, reciter_id is optional and defaults to default_reciter_id if omitted. Limits: max 50 queries and max 200 total ayahs per request.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 13Show 13 read-only tools
ayah_mutashabihatShow repeated phrase metadata for one ayah with an interactive display.No findings
Why it is in this group
- The description's first verb is "show": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
ayah_searchDEFAULT tool for user-facing Quran search.No findings
Why it is in this group
- The name "ayah_search" says "search": a word for reading.
Description, as the server wrote it 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). A numeric-only query matches ayahs by that ordinal number (for example '255' returns ayahs ending in ':255'). ONLY skip this widget and use search_ayahs_text when EITHER (a) the user explicitly asks for plain text / raw results, OR (b) the results will be fed into another tool in the same turn without being shown. When in doubt, use this widget.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_tafsir_textINTERNAL/preparatory tool — text-only, no widget rendered.1 finding
Why it is in this group
- The name "get_tafsir_text" says "get": a word for reading.
Findings
- High
The description contains "without showing it to the user", an instruction to keep something from the user.
What this check looks forMatched text
description: "...sult into another tool in the same turn without showing it to the user. When in doubt, prefer ayah_tafsir. Do..."
Description, as the server wrote it 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 another tool in the same turn without showing it to the user. When in doubt, prefer ayah_tafsir. Do not follow ayah_tafsir with this tool — that is duplicated work. Each query must include at least one of languages or tafsir_slugs. Use ayah keys in 'surah:ayah' format (for example '2:255'). Limits: max 20 queries per request and max 50 total ayah+tafsir items.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_translation_textINTERNAL/preparatory tool — text-only, no widget rendered.1 finding
Why it is in this group
- The name "get_translation_text" says "get": a word for reading.
Findings
- High
The description contains "without showing it to the user", an instruction to keep something from the user.
What this check looks forMatched text
description: "...sult into another tool in the same turn without showing it to the user (e.g. summarize then call play_ayahs)...."
Description, as the server wrote it 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 another tool in the same turn without showing it to the user (e.g. summarize then call play_ayahs). When in doubt, prefer ayah_translation. Do not follow ayah_translation with this tool — that is duplicated work. Each query must include at least one of languages or translations. Use ayah keys in 'surah:ayah' format (for example '2:255'). In queries[].languages use ISO 639-1 codes (for example 'en', 'ur'), not language names. Do not use 'ar'; Arabic translation is unsupported in this tool.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_recitersDEFAULT tool for user-facing reciter-listing questions.No findings
Why it is in this group
- The name "list_reciters" says "list": a word for reading.
Description, as the server wrote it 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 for plain text / raw data, OR (b) you will pipe the result into another tool (e.g. play_ayahs) in the same turn without showing the list. When in doubt, use this widget.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_tafsirsDEFAULT tool for user-facing tafsir-listing questions.No findings
Why it is in this group
- The name "list_tafsirs" says "list": a word for reading.
Description, as the server wrote it 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 explicitly asks for plain text / raw data, OR (b) you will pipe the result into ayah_tafsir in the same turn without showing the list. When in doubt, use this widget.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_translationsDEFAULT tool for user-facing translation-listing questions.No findings
Why it is in this group
- The name "list_translations" says "list": a word for reading.
Description, as the server wrote it 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 names like 'english'. ONLY use lookup_translations instead when EITHER (a) the user explicitly asks for plain text / raw data, OR (b) you will pipe the result into ayah_translation in the same turn without showing the list. When in doubt, use this widget. Returned language_name values are display labels. Rows without usable slugs are filtered out.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
lookup_recitersINTERNAL/preparatory tool — text-only, no widget rendered.No findings
Why it is in this group
- The name "lookup_reciters" says "lookup": a word for reading.
Description, as the server wrote it 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. user asks to play audio by a named reciter; call this to resolve reciter_id, then call play_ayahs). When in doubt, prefer list_reciters.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
lookup_tafsirsINTERNAL/preparatory tool — text-only, no widget rendered.No findings
Why it is in this group
- The name "lookup_tafsirs" says "lookup": a word for reading.
Description, as the server wrote it 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. resolve a named tafsir to its slug, then call ayah_tafsir). When in doubt, prefer list_tafsirs.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
lookup_translationsINTERNAL/preparatory tool — text-only, no widget rendered.No findings
Why it is in this group
- The name "lookup_translations" says "lookup": a word for reading.
Description, as the server wrote it 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 list (e.g. resolve a named translator to the correct slug, then call ayah_translation). When in doubt, prefer list_translations. Use ISO 639-1 codes like 'en', not names like 'english'.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
phrase_mutashabihatShow phrase mutashabihat occurrences with an interactive display.No findings
Why it is in this group
- The description's first verb is "show": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
prayer_timesGet Islamic prayer times for a city with an interactive timetable display.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "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 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
search_ayahs_textINTERNAL/preparatory tool — text-only, no widget rendered.1 finding
Why it is in this group
- The name "search_ayahs_text" says "search": a word for reading.
Findings
- High
The description contains "without showing the raw search results to the user", an instruction to keep something from the user.
What this check looks forMatched text
description: "...yahs, ayah_tafsir, or ayah_translation) without showing the raw search results to the user. When in doubt, prefer ayah_search. Do..."
Description, as the server wrote it 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) without showing the raw search results to the user. When in doubt, prefer ayah_search. Do not follow ayah_search with this tool — that is duplicated work. Query is Arabic script only; diacritics and punctuation are ignored. A numeric-only query matches ayahs by that ordinal number.
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 or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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 20, 2026, 19:00 UTC, unchanged since Oct 22, 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
- 3
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.tarteel.ai/mcp: tools/list returned 16 tools to an anonymous client, including ayah_translation (write), ayah_tafsir (write), play_ayahs (write)
Findings
Matches of fixed checks, with the text they matched.
The description contains "without showing it to the user", an instruction to keep something from the user.
What this check looks forMatched text
description: "...sult into another tool in the same turn without showing it to the user (e.g. summarize then call play_ayahs)...."
- Highget_tafsir_text
The description contains "without showing it to the user", an instruction to keep something from the user.
What this check looks forMatched text
description: "...sult into another tool in the same turn without showing it to the user. When in doubt, prefer ayah_tafsir. Do..."
The description contains "without showing the raw search results to the user", an instruction to keep something from the user.
What this check looks forMatched text
description: "...yahs, ayah_tafsir, or ayah_translation) without showing the raw search results to the user. When in doubt, prefer ayah_search. Do..."
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 2.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http tarteel https://mcp.tarteel.ai/mcpclaude mcp add --transport http tarteel https://mcp.tarteel.ai/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__tarteel__ayah_mutashabihat",
"mcp__tarteel__phrase_mutashabihat",
"mcp__tarteel__ayah_search",
"mcp__tarteel__list_reciters",
"mcp__tarteel__list_tafsirs",
"mcp__tarteel__list_translations",
"mcp__tarteel__prayer_times",
"mcp__tarteel__lookup_reciters",
"mcp__tarteel__lookup_tafsirs",
"mcp__tarteel__lookup_translations",
"mcp__tarteel__get_translation_text",
"mcp__tarteel__get_tafsir_text",
"mcp__tarteel__search_ayahs_text"
],
"ask": [
"mcp__tarteel__ayah_translation",
"mcp__tarteel__ayah_tafsir",
"mcp__tarteel__play_ayahs"
],
"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 tarteel. Review it before you use it.
Capability tags behind 1 rule
- mcp__tarteel__prayer_times 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.TarteelAI/tarteel-mcp-server/verify?hash=f3a962a071584e97cfaeeaf61a4911f18d7478a9983571d85f096f30bcdb9ea1" | jq -e '.changed == false'Pinned hash f3a962a07158, from Nov 16, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.TarteelAI/tarteel-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.TarteelAI/tarteel-mcp-server)Source: MCP Registry. Synced Oct 21, 2026, 18:21 UTC.
Tarteel MCP Server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Tarteel MCP Server safe?
- No scan can promise that. What its definitions show: 16 tools, 3 of which can change, send or delete something, and 3 findings (3 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Tarteel MCP Server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Tarteel MCP Server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Tarteel MCP Server have?
- 16 tools: 3 write, 13 read. ayah_translation, ayah_tafsir, play_ayahs, ayah_mutashabihat, phrase_mutashabihat, ayah_search, list_reciters, list_tafsirs and 8 more.
Does the Tarteel MCP Server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Tarteel MCP Server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Tarteel MCP Server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.