Tool ChainerSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://tss.topiray.com/products/mcp-chain)
An MCP (Model Context Protocol) server that chains calls to other MCP tools, reducing token usage by allowing sequential tool execution with result passing. Designed to solve https://github.com/modelcontextprotocol/specification/issues/215
Step function like JSON paths:
Features
- Chain multiple MCP tools together in sequence
- Pass results from one tool as input to another tool using
CHAIN_RESULTplaceholder - Filter and extract specific data using JsonPath with
inputPathandoutputPathparameters - Automatic tool discovery from configured MCP servers
- Minimal token usage compared to individual tool calls
Tools
This server implements the following MCP tools:
mcp_chain- Chain together multiple MCP serverschainable_tools- Discover tools from all MCP servers so the mcp_chain tool can be useddiscover_tools- Rediscover tools from all MCP servers
Installation
Prerequisites
- Node.js (v16 or later)
- npm
Installing from npm
# Install npm install @thirdstrandstudio/mcp-tool-chainer # Or use with npx directly npx -y @thirdstrandstudio/mcp-tool-chainer
Installing from source
# Clone the repository git clone https://github.com/thirdstrandstudio/mcp-tool-chainer.git cd mcp-tool-chainer # Install dependencies npm install # Build the package npm run build
Usage with Claude Desktop, Cursor etc
ENSURE IT IS THE LAST MCP TO RUN OTHERWISE IT WILL HAVE TO RUN DISCOVERY AGAIN
Add the following to your claude_desktop_config.json or mcp.json:
If installed from npm globally
5b1aa7e2c466OBSERVED · 2026-10-07Exposed tools (3)
3 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
chainable_tools | read | Discover tools from all MCP servers so the mcp_chain tool can be used |
discover_tools | read | Rediscover tools from all MCP servers so the mcp_chain tool can be used |
mcp_chain | read | Chain together multiple MCP servers |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
5b1aa7e2c466full audit observations/trust-audit/mcp-server/thirdstrandstudio__tool-chainer.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | 5b1aa7e2c466 | SAFE | B | 89 | first audit |
Questions
What tools does Tool Chainer expose?
3 in total: 3 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Tool Chainer safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Tool Chainer need?
No credential environment variables were found in its source, so it appears to need none.
How does Tool Chainer run?
It speaks stdio, so it runs as a local process your client starts.
How current is this page?
The grade is for one exact copy of the source (5b1aa7e2c466), read on 2026-10-07. The repository is watched and re-audited when it changes.