Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Nothing to run from here
Traplens 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.
99/100
trust score
4
tools declared
local
runs on your machine
—
downloads a day
What it does
Dated, verified API breakages for coding agents: look up traps by provider or by error text.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user traplens-mcp '--' npx -y @reneturcios/traplens mcp
# 2 — ask your agent for something these tools do
# lookup_traps, search_traps, file_trap and 1 more
Traplens costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 380 servers
CloudCorpRecords380 servers
28 categories
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. This one runs on your machine: your client starts Traplens as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
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 traplens-mcp '--' npx -y @reneturcios/traplens mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: 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 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.
What you approve
4 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.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | The service, by slug or common name, e.g. "stripe", "supabase", "github-actions", "openai api". |
| surface | string | no | Optional part of the service you are working on, e.g. "webhooks" or "image generation". Ranks matching traps first; never filters others out. |
| context | string | no | Optional one-line description of the task, e.g. "verify webhook signatures in Next.js". Ranks the most relevant traps first. |
| include_stale | boolean | no | Also return traps not re-checked recently. Default false. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| error_text | string | yes | The error message or unexpected output, as shown. Known key and secret formats are redacted before matching. |
| provider | string | no | Optional service slug or name to search within, e.g. "stripe". Omit to search every provider. |
| include_stale | boolean | no | Also match traps not re-checked recently. Default false. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | The service, by slug or common name, e.g. "stripe". |
| surface_type | string | yes | Which kind of surface broke: api, sdk, ui, billing, infra, or tool (CLIs and AI coding tools). |
| surface_name | string | yes | The specific endpoint, package, command or screen, e.g. "webhooks.constructEvent". |
| title | string | yes | One line naming what goes wrong, as a developer would search for it. |
| symptoms | array | yes | Exact error messages or observed behavior, one per item. Leave out secrets and personal data. |
| cause | string | yes | Why it happens. |
| fix | string | yes | What to change, in plain words. |
| apply | string | yes | A short code or command example of the fix. |
| affected | string | yes | Which versions, plans or dates are affected. |
| sources | array | no | Official documentation or changelog URLs that confirm it. |
| tags | array | no | Optional short keywords. |
| visibility | string | no | public submits to the shared registry; private keeps it in your team's space (Pro or Team key). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trap_id | string | yes | The trap id from a lookup or search result, e.g. "fg-0158". |
| still_true | boolean | yes | true if the trap happened as described, false if it no longer happens. |
| hours_lost | number | no | Optional hours the trap cost before the fix was found. |
| version_seen | string | no | Optional SDK, API or tool version where you saw it, e.g. "stripe-node 22.3.0". |
Free
$0 forever
- 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 Traplens 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: —
ATrust score 99 / 100
Release 0.1.0 · scanned 5 Nov 2026
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 score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digestd9d1c285f57ffc2673aae3f209c822cd9d73c0c754818593f528fe315be9d11e
Score vectorthreat 100 → client 99
| 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 |
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
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. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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 digestd9d1c285f57ffc26
Scanned2026-11-05
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.
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 Traplens 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.