Extcord

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.extcord/extcord and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 7 Oct 2026. Not supplied by the maker.

• discover

  Find out what this server can do. With no arguments: every op by category with a one-line intent, plus saved recipes. With query: the best-matching ops and recipes. With op: that op's full contract an

• invoke

  Run one operation and get its result as a handle: type, size, estimated tokens, the value itself if small (else a preview), and suggested next ops. Example: invoke(op="fetch", args={"url": "https://ex

• run_pipeline

  Chain operations in one call; only the final result comes back, intermediate data stays on the server. Example steps: [{"op": "fetch", "args": {"url": "https://example.com/pricing"}, "as": "page"}, {"

• inspect

  Look at a handle: its summary, its value one page at a time, or its provenance. Check est_tokens in the summary before reading a big value; it's usually cheaper to narrow it with an op first (find, se

• run_recipe

  Run a saved pipeline in one call. Built-ins: page_to_markdown (url, max_tokens), page_outline (url), page_links (url, contains), page_tables (url, index), find_on_page (url, pattern).

• save_recipe

  Save a working pipeline under a name so any agent can run it later with run_recipe. Saved recipes are shared and can't be overwritten.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.