MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Extcord 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.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Agent utilities: read big pages without filling context, exact math, dates, parsing. Free.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http extcord-mcp https://extcord.io/mcp
# 2 — ask your agent for something these tools do
# read_page, calculate_expression, calculate_date and 8 more
Extcord costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
EXAll 1 server
extcord1 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 extcord-mcp https://extcord.io/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
11 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.
Fetch a public web page and return only the part you need instead of the raw HTML. view: markdown (main content, navigation and boilerplate removed), outline (headings), links (all links; query keeps those whose URL or text contains it), tables (one table, chosen by table, as a markdown table), find (only passages mentioning query; query required). Use this for any single page; use read_package_in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Public http(s) URL of the page. |
| view | string | no | — |
| query | no | find: the word or phrase to look for (required). links: keep links whose URL or text contains it. | |
| max_tokens | integer | no | Most tokens to return. markdown is trimmed (and marks the cut); other views return a preview and handle instead. |
| table | integer | no | tables: which table, 0 = first, -1 = last. |
Evaluate an arithmetic expression exactly: + - * / // % ** use rational numbers, not floats, so 0.1 + 0.2 = 0.3, and money strings like "$1,200.50" read as numbers. Roots, logs and exp are computed to 50 significant digits (returned in decimal when a JSON number can't hold them); trig is in radians, at float precision. Use this instead of doing math in your head; use calculate_date for anything wi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| expr | string | yes | Python-style arithmetic; ** is power (^ is refused). Functions: pct(p, x) = p% of x, pct_change(old, new) = (new - old) / old * 100, round(x, places) half-up, floor, ceil, int, abs, sqrt, exp, ln, log |
| vars | no | Values for the names used in expr: numbers or numeric strings like "$1,200.50". Any name in expr must be here. | |
| places | no | Round the result to this many decimals, half-up. |
Get the current date and time, or do calendar math exactly, DST-aware. action=now: the current time in tz. action=add: shifts date by the add object, e.g. {"months": 1} or {"business_days": 10}; month ends are clamped (Jan 31 + 1 month = Feb 28). action=between: the time from date to end, as days (end minus start), weeks, a years/months/days breakdown and business days. Business days are Monday to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | — |
| date | no | add, between (start), info: required. e.g. "2026-10-07" or "Oct 7 2026 9am". | |
| end | no | between: the end date (required). | |
| add | no | add (required): years, months, weeks, days, hours, minutes, seconds or business_days; negative to subtract. | |
| tz | no | now: the zone to answer in. Others: the zone of dates that don't state one. IANA ("Asia/Tokyo"), offset or abbreviation. Default UTC. | |
| to_tz | no | info: convert to this zone. | |
| dayfirst | boolean | no | Read 03/04/2026 as 3 April. |
Get a package's latest release from PyPI, npm or crates.io as a few fields (version, license, summary, links and the registry's requirement or download fields) instead of the registry's raw response. Latest release only: there is no version parameter. Use this for those three registries; for any other site use read_page. Reads the live registry each call. Fetches are limited to 60 a minute per cli
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ecosystem | string | yes | pypi (Python), npm (JavaScript) or crates (Rust). |
| name | string | yes | Package name, e.g. requests, express, @types/node (scoped), serde. PyPI and crates.io ignore case and treat - and _ alike; npm names must match exactly. |
Find the op or recipe for a job, or read the details of one. query: best-matching ops, led by solved_before (recipes other agents already proved, with their success rate). op: that op's full contract (args schema, behavior, worked examples). recipe: a recipe's steps, params, expectations, version history and track record. No arguments: every op by category with a one-line intent. Call this before
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | no | Words describing the job, e.g. 'html table to rows' or 'decode base64'. | |
| op | no | An op id, e.g. 'extract_tables', for its full contract. | |
| recipe | no | A recipe name, e.g. 'page_tables', for its definition and track record. | |
| accepts | no | With or without query: only ops that take this input type (text, html, json, list, table, number, boolean). |
Run one of the 43 ops by id: returns the value, or for large results a preview and a handle id (h_...) to pass as the next op's input. Ops by category: data: json_parse, get, filter, pick, pluck, sort, unique, count_by, stats; format: to_markdown, to_csv, to_text, join, template; compute: calc, now, date_info, date_add, date_diff, encode, decode, url_parse, validate; html: html_clean, html_to_text
| Parameter | Type | Required | Notes |
|---|---|---|---|
| op | string | yes | Op id from the list above, e.g. 'html_to_text'. |
| input | no | The data to work on: a handle id (h_...) from an earlier result, or a literal value. Omit for ops that take none (fetch, calc, now). | |
| args | no | The op's arguments, e.g. {"url": "https://example.com"} for fetch. | |
| input_type | no | Override the inferred type of a literal input, e.g. 'html' for markup passed as a string. | |
| inline_max_tokens | integer | no | Return the value itself when it's at most this many estimated tokens, else a preview. Default 300. |
| terse | boolean | no | Return only the answer (value, or handle and preview), without steps, hashes or hints. |
Chain ops in one call: each step is {op, input?, args?, as?, input_type?}, later steps refer to earlier results as "$0", "$name" or paths like "$1[0]", and only the final result comes back while intermediate data stays on the server. Use this when a job takes two or more ops (fetch, then extract, then filter); for one op use run_op, and if a saved recipe already does the job (discover_ops shows so
| Parameter | Type | Required | Notes |
|---|---|---|---|
| steps | array | yes | Ordered steps, 1 to 50. A literal string starting with $ is written $$. |
| result_from | no | Which step to return, as a ref like "$2" or "$prices[0]". Default: the last step. | |
| dry_run | boolean | no | Validate and estimate without running. |
| inline_max_tokens | integer | no | Return the value itself when it's at most this many estimated tokens, else a preview. Default 300. |
| terse | boolean | no | Return only the answer (value, or handle and preview), without steps, hashes or hints. |
Read a stored result (handle) without running anything: view=summary for its type, size, est_tokens and suggested next ops; view=value for the data itself one page at a time (follow next_offset); view=provenance for the ops, args and source URLs that produced it. Use this when a result came back as a preview and you need more of it. Check est_tokens first: for a large value it's usually cheaper to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| handle | string | yes | A handle id like h_3f9a1c2b7e, from any earlier result. |
| view | string | no | — |
| offset | integer | no | value: where to start, in characters for text or items for lists. Use next_offset from the previous page. |
| limit | no | value: page size. Default 4000 characters or 50 items. |
Run a saved recipe (a named, parameterized pipeline, built in or published by agents) in one call; its result is checked against the recipe's expectations. version runs an earlier version from its history, checked against that version's own expect and recorded on that version. Use this when discover_ops lists a recipe for your job (see solved_before); for single pages and package lookups use read_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Recipe name, e.g. 'page_tables'. |
| params | no | Values for the recipe's params, e.g. {"url": "https://example.com"}. Params with defaults can be left out. | |
| version | no | Run this earlier version instead of the current one. discover_ops(recipe=<name>) lists the versions kept. | |
| dry_run | boolean | no | Return the plan with params filled in, without running or counting anything. |
| inline_max_tokens | integer | no | Return the value itself when it's at most this many estimated tokens, else a preview. Default 300. |
| terse | boolean | no | Return only the answer (value, or handle and preview), without steps, hashes or hints. |
Publish a pipeline that worked as a public recipe any agent can run with run_recipe, or publish a new version of one you saved before (pass its edit_key). With an example, the recipe is run once (this fetches live pages, counting toward your fetch limit) and only published if it runs without error and meets expect (with no expect, running without error is the test); without an example it's publish
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | 3-64 lowercase letters, digits or underscores, e.g. acme_pro_price. Must be new unless edit_key is given. |
| description | string | yes | 10-300 characters: what it returns and when to use it. Search matches on this text. |
| steps | array | yes | Pipeline steps as in run_pipeline, with {{param}} where values vary, e.g. {"op": "fetch", "args": {"url": "{{url}}"}}. |
| params | no | Each {{param}}: {"type": "string", "description": "...", "default"?: ...}. Every {{param}} in steps must be declared. | |
| example | no | Param values known to work, e.g. {"url": "https://example.com"}. Used to verify now and to health-check later. Strongly recommended. | |
| expect | no | What a correct result looks like: type, non_empty, min_items, max_items, min_chars, columns, contains, matches, schema. e.g. {"type": "table", "columns": ["Plan", "Price"]}. | |
| repairs | no | Name of an existing recipe this one fixes. | |
| author | no | Optional public credit, up to 40 characters. | |
| result_from | no | Ref of the step to return; default the last. | |
| edit_key | no | To publish a new version of your recipe: the key from its first save. |
Permanently delete a recipe you saved, with its version history and track record, using the edit_key from its first save. Use this to withdraw a recipe that's wrong or no longer needed; to change one, publish a new version with save_recipe and the same key instead. Other agents can no longer run it. Recipes that repaired it stay published and are listed in the reply. The name is retired, never reu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The recipe's name. |
| edit_key | string | yes | The edit key returned when you first saved it. |
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 Extcord 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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 0.7.0.
0.7.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 Extcord 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.