MCP server for 104.com.tw job search platform
Free
Nothing to run from here
Edict Lang 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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Edict — A programming language for AI agents. JSON AST in, WASM out. MCP server included. Statically typed, effect-tracked, contract-verified.
Quickstart
# 1 — run it from where its publisher ships it
npx -y edict-lang
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> Edict — A programming language for AI agents. JSON AST in, WASM out. MCP server included. Statically typed, effect-tracked
Publishernot claimed
SOAll 1 server
sowiedu1 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. This one runs on your machine: your client starts Edict Lang 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. It is scanned, signed and pinned to the version you choose — 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. Claude Code registers it in one command.
claude mcp add edict-lang-mcp -- npx -y edict-langReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
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
18 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.
Return the JSON Schema defining valid Edict AST programs. Use format 'minimal' for reduced token cost (strips descriptions).
Takes no parameters.
Example callreturns →
Return compiler version and capability info.
Takes no parameters.
Example callreturns →
Return example programs as JSON ASTs.
Takes no parameters.
Example callreturns →
Validate an Edict AST against the compiler's JSON schema without typing or compiling. Use this as a first pass.
Takes no parameters.
Example callreturns →
Run the full semantic checker (name resolution, type checking, effect checking, contract verification) on an AST. Supports single module or multi-module input.
Takes no parameters.
Example callreturns →
Compile a semantically valid Edict AST into a WebAssembly module. Returns the WASM binary encoded as a base64 string. Supports single module or multi-module input.
Takes no parameters.
Example callreturns →
Execute a compiled WebAssembly module (provided as base64) in a sandboxed runtime with configurable limits.
Takes no parameters.
Example callreturns →
Apply surgical patches to an Edict AST by nodeId, then run the full check pipeline. Fix errors without resubmitting the entire AST.
Takes no parameters.
Example callreturns →
Return machine-readable catalog of all structured error types.
Takes no parameters.
Example callreturns →
Run non-blocking lint analysis on an Edict AST. Returns quality warnings without blocking compilation.
Takes no parameters.
Example callreturns →
Execute an Edict program with debug instrumentation. Returns structured crash diagnostics including call stack, crash location with nodeId, and step count.
Takes no parameters.
Example callreturns →
Compose multiple Edict program fragments into a single module. Fragments declare what they provide and require.
Takes no parameters.
Example callreturns →
Given a structured error, returns enriched repair context: pipeline stage, field metadata, example ASTs, and repair strategy.
Takes no parameters.
Example callreturns →
Export an Edict AST as a portable WASM skill package with validation and manifest generation.
Takes no parameters.
Example callreturns →
Import and execute a compiled Edict WASM skill package, validating its checksum.
Takes no parameters.
Example callreturns →
Auto-generate structured test cases from Z3-verified contracts. Extracts boundary values and counterexamples as regression tests.
Takes no parameters.
Example callreturns →
Re-execute a WASM module using a previously recorded replay token for deterministic reproduction of runtime behavior.
Takes no parameters.
Example callreturns →
Returns structured sponsorship and support information for the Edict project.
Takes no parameters.
Example callreturns →
Startermost installed
$10 / month
- 8,000 calls a month, included
- 96 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Team
$35 / month
- 40,000 calls a month, included
- 480 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Business
$75 / month
- 180,000 calls a month, included
- 2,160 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $10 a month covers every tool 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: $8.42
$16.58 left
ATrust score 93 / 100
Release 1.23.2 · scanned 25 Aug 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
Findings3 threat · 10 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest9709ea5f8b15b4c815edeeb8db7d4fe28e93edda86255a9ca999bc47c618e643
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 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. high 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. | ||
can execute shell commands or code
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 digest9709ea5f8b15b4c8
Scanned2026-08-25
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
Pinned to 1.23.2 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.23.2
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Edict Lang in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.