MCP server for DeepL translation API
Nothing to run from here
Stigmer 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.
93/100
trust score
189
downloads a day
remote
at its publisher
10k
downloads in 30d
What it does
Model Context Protocol server for the Stigmer platform — exposes Stigmer agents, skills, MCP servers, and workflows as MCP tools and resources
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http stigmer-mcp https://stigmer.network/mcp
# 2 — ask your agent for something these tools do
# run_agent, get_agent_execution, submit_agent_execution_approval and 30 more
Stigmer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
STAll 1 server
@stigmer1 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 stigmer-mcp https://stigmer.network/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
33 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.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
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 Stigmer 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 93 / 100
Release 3.41.0 · scanned 6 Oct 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 score93
Findings1 threat · 1 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digeste93490cfcf643e9363d34958cf7d083989f3c37ac19864cfb00530cedacce0fc
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| 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 surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (33 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, 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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| run_agent | no tags | |
| get_agent_execution | no tags | |
| submit_agent_execution_approval | no tags | |
| get_agent | no tags | |
| apply_agent | no tags | |
| delete_agent | no tags | |
| send_channel_message | external-sink | external-sink: parameter "recipient" |
| escalate_to_human | no tags | |
| get_environment | sensitive-source | sensitive-source: keyword "get_env" |
| apply_environment | no tags | |
| delete_environment | no tags | |
| cancel_execution | no tags | |
| get_mcp_server | no tags | |
| apply_mcp_server | no tags | |
| delete_mcp_server | no tags | |
| remember | no tags | |
| search | no tags | |
| get_skill | no tags | |
| delete_skill | no tags | |
| list_skill_versions | no tags | |
| run_workflow | no tags | |
| get_workflow_execution | no tags | |
| get_workflow_execution_events | no tags | |
| list_pending_approvals | no tags | |
| submit_workflow_task_approval | no tags | |
| get_task_kind_registry | no tags | |
| get_task_kind | no tags | |
| get_workflow | no tags | |
| apply_workflow | no tags | |
| delete_workflow | no tags | |
| list_workflow_versions | no tags | |
| tag_workflow_version | no tags | |
| validate_workflow_yaml | 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.
get_environment → send_channel_message
A sensitive-source → external-sink chain exists: get_environment ⇒ send_channel_message.
Supply chain and provenance
Integrityfirst-seen
Surface digeste93490cfcf643e93
Scanned2026-10-06
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 3.41.0.
3.41.0
30 Sep 2026
latestNo release note was published with this version.
3.38.3
28 Sep 2026
No release note was published with this version.
3.27.2
24 Sep 2026
No release note was published with this version.
3.27.0
23 Sep 2026
No release note was published with this version.
3.20.0
20 Sep 2026
No release note was published with this version.
3.18.0
18 Sep 2026
No release note was published with this version.
3.15.2
13 Sep 2026
No release note was published with this version.
3.14.1
11 Sep 2026
No release note was published with this version.
3.13.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Stigmer 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.