MCP server that wraps the Dagster GraphQL API — manage runs, assets, schedules, sensors, and backfills from any MCP client
Nothing to run from here
GlanceDesk 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
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Checked calculators for money, tax, crypto, engineering and compliance, each with formula and source
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http glancedesk-mcp https://glancedesk.com/mcp
# 2 — ask your agent for something these tools do
# search_tools, get_tool, run_calculator and 5 more
GlanceDesk costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GLAll 1 server
glancedesk1 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 glancedesk-mcp https://glancedesk.com/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
8 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.
Find GlanceDesk calculators and compliance checks by topic, for example "UAE gratuity", "Pakistan salary tax", "loan EMI", "e-invoicing Saudi", "crypto liquidation price", "concrete mix cement bags". Returns each tool's slug, title, one-line description, page URL and which tool runs it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Words describing what the person wants to work out. Empty lists every tool. |
| product | string | no | calculators = GlanceDesk Calculators (money, tax, loans, conversions); jurisdiction = GlanceDesk Jurisdiction (compliance, labour law); crypto = GlanceDesk Crypto (futures, spot, staking, fees, crypto |
| limit | integer | no | Most results to return (default 10). |
Get everything about one GlanceDesk tool before running it: its inputs (types, units, options, min/max) as JSON Schema, outputs, formula or legal rule, official sources with URLs, last-checked date, disclaimer, page URL and a worked example computed by the tool itself.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug from search_tools, e.g. "uae-gratuity-calculator". |
Run one GlanceDesk Calculators, GlanceDesk Crypto or GlanceDesk Compute calculator with the person's values and get the tested answer with units, a one-sentence explanation, the formula, official sources, last-checked date, page URL and disclaimer. Invalid or missing values return the calculator's own error message; nothing is guessed or filled in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Calculator slug (see search_tools / get_tool). |
| inputs | object | yes | Field id to value, as listed by get_tool. Numbers may be given as numbers or as text like "10,000"; dates as YYYY-MM-DD; options by their value. |
Work out what a private-sector worker is owed when a job ends in Saudi Arabia, the UAE or Qatar: end-of-service award or gratuity, unpaid wages, unused leave and overtime, each line with its labour-law article, plus a claim summary. Uses GlanceDesk Jurisdiction's tested engine.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | sa = Saudi Arabia (Labor Law, Royal Decree M/51), ae = United Arab Emirates (Federal Decree-Law 33 of 2021, private sector), qa = Qatar (Labour Law, Law No. 14 of 2004). |
| first_day | string | yes | First day of work, YYYY-MM-DD. |
| last_day | string | yes | Last day of work, YYYY-MM-DD. Both days count as service. |
| basic_monthly_wage | number | yes | Last basic monthly wage, without allowances (SAR, AED or QAR). The UAE and Qatar gratuity and leave pay use this. |
| total_monthly_wage | number | yes | Last total monthly wage: basic plus contractual allowances. The Saudi award and leave pay use this. Must be at least the basic wage. |
| how_it_ended | string | yes | employer = the employer ended the contract (not for misconduct); expired = fixed-term contract ended, not renewed; resign = the worker resigned; breach = the worker left because the employer broke the |
| unpaid_wage_months | number | no | Optional. Months of wages not paid (decimals for part months). |
| unused_leave_days | number | no | Optional. Unused annual leave days earned, including this year's share. |
| overtime_hours | number | no | Optional. Unpaid overtime hours. |
| normal_hours_per_day | number | no | Needed only with overtime: normal working hours per day in the contract. |
| night_overtime_hours | number | no | UAE or Qatar, optional: how many of the overtime hours were at night (UAE 10 pm to 4 am, Qatar 9 pm to 3 am; not for shift workers). |
| unpaid_absence_days | integer | no | UAE only, optional: days of unpaid absence (not counted as service). |
Check whether e-invoicing applies to a business and its deadline: Saudi ZATCA Phase 1 and Phase 2 waves, UAE e-invoicing phases (Ministerial Decisions 243 and 244 of 2025), Pakistan FBR electronic invoicing (S.R.O. 1852(I)/2025). Every line cites its legal reference and official source; unconfirmed facts are marked "Being verified" and not used.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | sa = Saudi Arabia (ZATCA), ae = United Arab Emirates (MoF/FTA), pk = Pakistan (FBR). |
| resident | boolean | no | Saudi Arabia: is the business resident in Saudi Arabia? |
| vat_registered | boolean | no | Saudi Arabia or UAE: is the business registered for VAT there? |
| revenue_by_year | object | no | Saudi Arabia: revenue subject to VAT (SAR) for each year the ZATCA waves use: 2022, 2023, 2024, 2025. Leave a year out if not trading. |
| conducts_business_in_uae | boolean | no | UAE: does the person conduct business in the UAE? |
| entity_type | string | no | UAE: business, or gov = government entity. |
| revenue | number | no | UAE: gross revenue in the most recent accounting period (AED). |
| customers | array | no | Who you invoice: b2b = businesses, b2g = government, b2c = consumers. |
| sales_tax_registered | boolean | no | Pakistan: registered for sales tax with the FBR? |
| business_type | string | no | Pakistan: public = public listed company, company = other company, individual = individual or association of persons. |
| imports_goods | boolean | no | Pakistan: does the business import goods? |
| turnover | number | no | Pakistan: turnover declared in sales tax returns for the last twelve months (PKR). |
Work out the GDPR / UK GDPR Article 33 deadline for notifying a personal data breach: 72 elapsed hours from becoming aware, given as local time in the person's time zone (IANA zone with daylight saving, or a fixed UTC offset) and in UTC. Returns the deadline, which authority to notify (lead authority, every EU authority where affected people live, or the UK Information Commission), the steps for a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| aware | string | yes | When the organisation became aware of the personal data breach: local date and time YYYY-MM-DDTHH:MM in time_zone (or utc_offset). |
| role | string | yes | controller = decides why and how the data is used; processor = handles the data for a client. |
| scope | array | no | Which apply (any combination): eu_main = EU GDPR, main establishment in the EU; eu_none = EU GDPR, no establishment in the EU (serves EU users from outside); uk = UK GDPR, affected people in the UK. E |
| time_zone | string | no | IANA time zone of the person, e.g. "Europe/London", "Asia/Karachi", "America/Los_Angeles". Daylight saving time is applied. Give this or utc_offset; with neither, times are UTC. |
| utc_offset | string | no | Fixed offset from UTC instead of time_zone, e.g. "+05:00" or "-04:00" (no daylight-saving changes). Default "+00:00" (UTC). |
Work out the deadline to answer a data subject or consumer request: EU GDPR and UK GDPR Article 12(3) (one month, extendable by two further months; UK Data (Use and Access) Act 2025 changes), or California CCPA/CPRA (confirm within 10 business days, respond within 45 days with one 45-day extension; opt-out or limit requests within 15 business days). Returns each date with its legal reference, the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| law | string | yes | eu = EU GDPR, uk = UK GDPR, ccpa = California CCPA/CPRA. |
| request_type | string | no | CCPA only (required for ccpa): know = know/access, delete or correct; optout = opt out of sale/sharing, or limit use of sensitive data. Not used for eu or uk. |
| received | string | yes | Local date the request was received, YYYY-MM-DD. |
| time_zone | string | no | IANA time zone of the person, e.g. "Europe/London", "Asia/Karachi", "America/Los_Angeles". Daylight saving time is applied. Give this or utc_offset; with neither, times are UTC. |
| utc_offset | string | no | Fixed offset from UTC instead of time_zone, e.g. "+05:00" or "-04:00" (no daylight-saving changes). Default "+00:00" (UTC). |
Work out a business tax filing deadline and estimate the late penalty: Pakistan income tax return (Income Tax Ordinance s.118 with official FBR extensions; s.182 penalty) and quarterly withholding statements (s.165), UAE Corporate Tax return and payment (9 months after the tax period; registration deadline under FTA Decision 3/2024; Cabinet Decision 75/2023 penalties), UAE VAT return and payment (
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filing | string | yes | Which deadline: pk_income_tax_return = Pakistan income tax return (Income Tax Ordinance s.118, penalty s.182); pk_withholding_statement = Pakistan quarterly withholding statement (s.165); uae_corporat |
| taxpayer_type | string | no | pk_income_tax_return: company; salaried = individual with 75% or more of income from salary; other = other individual or association of persons (AOP). |
| tax_year_end | string | no | pk_income_tax_return: last day of the tax year (normal tax year ends 30 June, e.g. 2026-06-30 = tax year 2026; special tax years end on another month end). Date as YYYY-MM-DD. |
| tax_payable | number | no | pk_income_tax_return: tax payable for the year in PKR (the higher of assessed tax and the last duly filed year's tax). Needed with filed to estimate the late-filing penalty. |
| quarter_end_month | integer | no | pk_withholding_statement: month the quarter ends (3 = March, 6 = June, 9 = September, 12 = December). |
| year | integer | no | pk_withholding_statement: calendar year the quarter ends in, e.g. 2026. |
| withheld_tax_paid_on_time | string | no | pk_withholding_statement, with filed: yes = the tax withheld or collected was paid by its due date; no = it was not; nil = no tax was required to be withheld or collected. |
| period_end | string | no | uae_corporate_tax, uae_vat, saudi_vat: last day of the tax period (Saudi: a month end). Date as YYYY-MM-DD. |
| incorporated | string | no | uae_corporate_tax, optional: date the business was set up (checks the FTA Decision 7/2024 postponement for first tax periods ending on or before 29 February 2024). Date as YYYY-MM-DD. |
| registration_type | string | no | uae_corporate_tax, optional (gives the registration deadline, FTA Decision 3/2024): res_new = resident company set up on or after 1 March 2024; res_old = resident company set up before 1 March 2024 (r |
| registration_start | string | no | uae_corporate_tax, with registration_type: the date that starts the registration period (see registration_type). Date as YYYY-MM-DD. |
| repeat_within_24_months | boolean | no | uae_vat, with filed: true if a late return was already penalised in the previous 24 months. |
| taxable_supplies_12m | number | no | saudi_vat: value of taxable supplies in the last 12 months in SAR (over SAR 40,000,000 = monthly tax period). |
| monthly_approved | boolean | no | saudi_vat: true if ZATCA approved or directed a monthly tax period although supplies are not over SAR 40,000,000. |
| vat_due | number | no | saudi_vat, with filed or paid: VAT due for the period in SAR (to estimate the fines). |
| unpaid_tax | number | no | uae_corporate_tax, uae_vat, with paid: tax paid late, in AED. |
| filed | string | no | Optional: date the return or statement was or will be filed (estimates the late-filing penalty). Date as YYYY-MM-DD. |
| paid | string | no | Optional: date the tax was or will be paid (uae_corporate_tax, uae_vat with unpaid_tax; saudi_vat with vat_due). Date as YYYY-MM-DD. |
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 GlanceDesk 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 0.1.0 · scanned 30 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 digesta376ca15e34b3cd7c8f5dabff0cd301f367c673603236520b114ca76b53b3c24
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 |
|---|---|---|
| search_tools | no tags | |
| get_tool | no tags | |
| run_calculator | no tags | |
| gulf_final_settlement | no tags | |
| einvoicing_check | no tags | |
| breach_notification_deadline | no tags | |
| data_request_deadline | no tags | |
| business_filing_deadline | 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 digesta376ca15e34b3cd7
Scanned2026-10-30
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 0.1.0.
0.1.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 GlanceDesk 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.