io.github.codecraf8/maap
NPM · MAAP-MCP
Calibrated numeric estimates with uncertainty from messy records
Available components
Last scanned (8 hours ago)
Scores higher than 53% of npm servers
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 462 tokens (~231/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/maap-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
estimate ~340
Estimate a number for one case, with calibrated uncertainty. Returns a median (the answer), an 80% range the true value should fall inside about 80 times in 100, the quantiles you asked for, and the probability of crossing any threshold you name. Use the median as the answer, and the range when the decision depends on how wrong it could be. Needs a `target` id from `list_targets`. The first call after an idle period can take tens of seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| examples | array | – | Past cases with their known answers, up to 16. Required (at least 8) for a target that is not in the catalogue. |
| interval_levels | array | – | Coverage levels for ranges, e.g. [0.5, 0.8]. Default 0.8. |
| levels | array | – | Quantile levels in (0, 1). Default 0.1, 0.5, 0.9. |
| return_pmf | boolean | – | Count targets only: the probability of each individual value. |
| state | – | yes | The case to read, as an object of your own columns ({"airline": "Vistara", "days_left": 9}) or as plain text. Send everything you know about this one case — the model reads it as a record. |
| target | string | yes | A target id from list_targets, e.g. "uci_1.rings" or "kgl_flight_price_prediction.price". |
| thresholds | array | – | Numbers to test crossing. Returns P(value > t) for each — use this rather than comparing the median yourself. |
No output schema declared.
No examples provided.
list_targets ~122
Search the maap catalogue of trained targets. A target is one specific number the model can predict, named by id. Call this FIRST to find the id to pass to `estimate`; ids cannot be guessed. Filter by keyword and by kind of number.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return. |
| primitive | string | – | amount = money-like, count = whole numbers, measure = a reading on a scale. |
| query | string | – | Keyword matched against the id and the description, e.g. "price", "pollution", "rings". |
No output schema declared.
No examples provided.
How do I install the io.github.codecraf8/maap MCP server?
io.github.codecraf8/maap runs locally as an npm package, launched with npx -y maap-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · maap-mcp
claude mcp add codecraf8-maap -- npx -y maap-mcp
What is the io.github.codecraf8/maap MCP server?
io.github.codecraf8/maap is an MCP server listed in the public MCP registry as io.github.codecraf8/maap. Calibrated numeric estimates with uncertainty from messy records. This page covers its npm package (maap-mcp).
Is the io.github.codecraf8/maap MCP server safe to use?
io.github.codecraf8/maap scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.codecraf8/maap MCP server expose?
io.github.codecraf8/maap exposes 2 tools: list_targets, estimate. Their descriptions and schemas cost roughly 462 tokens of context every time the server is loaded.
Is the io.github.codecraf8/maap MCP server still maintained?
io.github.codecraf8/maap is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.codecraf8/maap MCP server under?
io.github.codecraf8/maap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.