io.github.CloudCorpRecords/traplens
NPM · @RENETURCIOS/TRAPLENS · 2 COMPONENTS
Dated, verified API breakages for coding agents: look up traps by provider or by error text.
Available components
Last scanned (7 hours ago)
Scores higher than 36% of npm servers
Category Developer Tools
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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
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 0 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 824 tokens (~206/item across 4 items; 4 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 Management3
- Stability observed for 1 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 69
First indexed and scored.
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/@reneturcios/traplens@0.1.0
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
confirm_trap Confirm or dispute a trap ~168
After you hit or avoid a trap returned by lookup_traps or search_traps, record whether it is still true. Confirmations raise a trap's trust score and disputes lower it; several disputes send it back for review. One vote per trap per 30 days. Needs a free API key.
| Name | Type | Req | Description |
|---|---|---|---|
| hours_lost | number | – | Optional hours the trap cost before the fix was found. |
| still_true | boolean | yes | true if the trap happened as described, false if it no longer happens. |
| trap_id | string | yes | The trap id from a lookup or search result, e.g. "fg-0158". |
| version_seen | string | – | Optional SDK, API or tool version where you saw it, e.g. "stripe-node 22.3.0". |
No output schema declared.
No examples provided.
file_trap File a new trap ~317
Draft a trap after a failure was fixed. Private by default with a Pro or Team key. Public filings are checked automatically against official sources and published only when an official source confirms them. A reviewer can still act on any filing. Citing the provider's official documentation or changelog in sources helps. No API key needed. Set visibility to public to submit to the public registry.
| Name | Type | Req | Description |
|---|---|---|---|
| affected | string | yes | Which versions, plans or dates are affected. |
| apply | string | yes | A short code or command example of the fix. |
| cause | string | yes | Why it happens. |
| fix | string | yes | What to change, in plain words. |
| provider | string | yes | The service, by slug or common name, e.g. "stripe". |
| sources | array | – | Official documentation or changelog URLs that confirm it. |
| surface_name | string | yes | The specific endpoint, package, command or screen, e.g. "webhooks.constructEvent". |
| surface_type | string | yes | Which kind of surface broke: api, sdk, ui, billing, infra, or tool (CLIs and AI coding tools). |
| symptoms | array | yes | Exact error messages or observed behavior, one per item. Leave out secrets and personal data. |
| tags | array | – | Optional short keywords. |
| title | string | yes | One line naming what goes wrong, as a developer would search for it. |
| visibility | string | – | public submits to the shared registry; private keeps it in your team's space (Pro or Team key). |
No output schema declared.
No examples provided.
lookup_traps Look up traps for a provider ~197
Call before writing code against a third-party API, platform, or AI tool. Returns up to 10 verified, dated failure modes for that provider, each with symptoms, cause, fix, a code example and the date it was last checked. Use search_traps instead when you already have an error message.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional one-line description of the task, e.g. "verify webhook signatures in Next.js". Ranks the most relevant traps first. |
| include_stale | boolean | – | Also return traps not re-checked recently. Default false. |
| provider | string | yes | The service, by slug or common name, e.g. "stripe", "supabase", "github-actions", "openai api". |
| surface | string | – | Optional part of the service you are working on, e.g. "webhooks" or "image generation". Ranks matching traps first; never filters others out. |
No output schema declared.
No examples provided.
search_traps Search traps by error text ~142
Call when a call to a third-party service fails or behaves unexpectedly. Paste the error text. Returns up to 5 verified traps whose symptoms match it, closest first, each with cause and fix. Returns nothing when no trap matches closely. Use lookup_traps instead before writing code.
| Name | Type | Req | Description |
|---|---|---|---|
| error_text | string | yes | The error message or unexpected output, as shown. Known key and secret formats are redacted before matching. |
| include_stale | boolean | – | Also match traps not re-checked recently. Default false. |
| provider | string | – | Optional service slug or name to search within, e.g. "stripe". Omit to search every provider. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/traplens MCP server?
io.github.CloudCorpRecords/traplens runs locally as an npm package, launched with npx -y @reneturcios/traplens. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/traplens
claude mcp add cloudcorprecords-traplens -- npx -y @reneturcios/traplens
What is the io.github.CloudCorpRecords/traplens MCP server?
io.github.CloudCorpRecords/traplens is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/traplens. Dated, verified API breakages for coding agents: look up traps by provider or by error text. This page covers its npm package (@reneturcios/traplens).
Is the io.github.CloudCorpRecords/traplens MCP server safe to use?
io.github.CloudCorpRecords/traplens scores 69 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.CloudCorpRecords/traplens MCP server expose?
io.github.CloudCorpRecords/traplens exposes 4 tools: lookup_traps, search_traps, file_trap, confirm_trap. Their descriptions and schemas cost roughly 824 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/traplens MCP server still maintained?
io.github.CloudCorpRecords/traplens 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.CloudCorpRecords/traplens MCP server under?
io.github.CloudCorpRecords/traplens declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.