Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Morocco Hcp Statistics 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.
What it does
Morocco, Haut-Commissariat au Plan (HCP) -- quarterly Bulletin statistique. Fleet #2932.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user morocco-hcp-statistics-mcp '--' npx -y @pipeworx/mcp-morocco-hcp-statistics
# 2 — ask your agent for something these tools do
# ma_bulletins, ma_indicators, ma_indicator_series
Morocco Hcp Statistics costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user morocco-hcp-statistics-mcp '--' npx -y @pipeworx/mcp-morocco-hcp-statisticsReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://gateway.pipeworx.io/morocco-hcp-statistics/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http morocco-hcp-statistics-mcp https://gateway.pipeworx.io/morocco-hcp-statistics/mcpNothing is required, but it can take PIPEWORX_API_KEY (Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.) if you want to set it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
3 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List the Moroccan Haut-Commissariat au Plan (HCP) quarterly statistical bulletins covered: title, quarter, publication date, how many indicator series parsed from each, plus the topic areas (prices, tourism, trade, labour, public finance, stock exchange, national accounts, ...). Start here for…
Takes no parameters.
Search Morocco's national economic and social indicators from the HCP quarterly bulletin (monthly and quarterly series: consumer and producer price indexes by city, industrial/mining/energy output, tourism nights, external trade, exchange rates, public finances, Casablanca stock exchange, labour…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Words from the indicator name, French or English, e.g. "indice general", "inflation", "nuitees", "euro". All words must match. |
| topic | string | no | Optional topic filter (substring), e.g. "IPC", "Tourisme", "COMMERCE EXTERIEUR", "FINANCES PUBLIQUES". Listed by ma_bulletins. |
| limit | number | no | Max results (1-100, default 25) |
Time series for one Moroccan HCP indicator by id (from ma_indicators): every period with its value, latest value, and the change vs the previous period and vs a year earlier. Optional from/to as YYYY-MM, YYYY-Qn or a bare year. A miss returns found:false with data_as_of and nearby ids.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Indicator id returned by ma_indicators |
| from | string | no | Earliest period, e.g. "2025-01", "2025-Q1" or "2025" |
| to | string | no | Latest period, e.g. "2026-06", "2026-Q2" or "2026" |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Morocco Hcp Statistics or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
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
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
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.
Any signed-in account that does not publish Morocco Hcp Statistics can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.