SML Risk Firewall
Pre-trade risk checks for agent trades: orders vs your limits, signed receipts.
Description from the maker (original English)
Remote MCP: plan, run, verify for SEO/security/ship-gate. Same REST API key; 500 free credits/month.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
X-Api-KeyValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http toolyour https://api.toolyour.com/mcp/http --header 'X-Api-Key: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"toolyour": {
"url": "https://api.toolyour.com/mcp/http",
"headers": {
"X-Api-Key": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"toolyour": {
"type": "http",
"url": "https://api.toolyour.com/mcp/http",
"headers": {
"X-Api-Key": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
X-Api-Key secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain toolyour.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: X-Api-Key
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: SML Risk Firewall, Nife, ipdata MCP by usefulapi
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Pre-trade risk checks for agent trades: orders vs your limits, signed receipts.
Manage Nife.io cloud apps, sites, secrets and Git integrations from MCP clients.
Look up location, network, company and threat data for IP addresses and ASNs in ipdata.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Remote MCP gateway for AI agents: plan → run playbook/solve → verify until pass.
MIT licensed. Hosted API/SaaS backends are optional — offline evals and local file control-plane run without them.
Product docs: https://www.toolyour.com/developers/mcp Official registry: com.toolyour/mcp npm client (separate): @toolyour/sdk (MIT)
cp .env.example .env
npm install npm run build:registry # from monorepo docs/ when regenerating npm run build npm run dev
Endpoints: http://localhost:3090/mcp (legacy SSE for compatible hosts) · Streamable HTTP: /mcp or /mcp/http. All Streamable HTTP endpoints are stateless: clients do not need session affinity, and a stale Mcp-Session-Id is ignored. The OAuth-protected /mcp/chatgpt endpoint validates its bearer token on every request. GET /mcp remains the legacy SSE endpoint and keeps its session behavior.
Health: GET /health/mcp · Ready: GET /health/mcp/ready · Metrics: GET /health/mcp/metrics (Prometheus text)
X-Api-Key: ty_...
Same key as ToolYour REST. Free tier: 500 credits/month (tools cost 1–10 credits). MCP exposes API-backed catalog tools only (hasApi).
ToolYour does not replace Cursor/Claude. The host keeps editor, git, and terminal. Agents should:
plan_task (free)run_playbook or solve_taskloop.nextActions in the workspaceverify_task with prior result as baseline until loop.gate is pass (or stop)Skill-loop responses also include an additive execution envelope (runId, intentId, intentType, idempotencyKey, and projectScope). Preserve it when handing a result to another MCP tool. Async jobs reuse execution.runId as the get_run polling id.
Internally, plan_task, solve_task, run_playbook, run_workflow, and verify_task use one executeIntent lifecycle boundary for correlation and the execution envelope. Credits settle on each gateway tool invoke (billing.settledBy = gateway_per_tool) — MCP does not double-bill. Free recall_context recalls purpose-typed memory before rebuilds.
Saved Playbooks turns a repeatable ToolYour workflow into a named, versioned recipe that an MCP-capable agent can run again. V1 deliberately points only to existing ToolYour skills or workflows; it does not store arbitrary shell commands, control another agent, or bypass host approval. Each account gets owner-scoped playbooks and durable run receipts.
Enable this only on a private/default MCP deployment with PLAYBOOKS_BETA=true. The beta adds create_saved_playbook, list_saved_playbooks, get_saved_playbook, update_saved_playbook, run_saved_playbook, and get_saved_playbook_run. It is intentionally excluded from /mcp/chatgpt so the reviewed public tool surface stays separate. The public surface includes the authenticated get_profile identity tool.
See Saved Playbooks beta design for the data model, safe execution boundary, and rollout guidance.
npm run ci # build + lint + unit/contract/integration + evals
npm run eval:golden # routing + jobReport fields + verify gate npm run eval:playbooks # skill → workflow → synthesizer matrix + fixture coverage npm run golden:tier1 # host work-package shapes
Fixtures: tests/eval/synth-fixtures.json · Goals: tests/eval/goals.jsonl
| Signal | How |
|---|---|
| JSON logs | Always (LOG_LEVEL) |
| In-process counters | /health/mcp + /health/mcp/metrics |
| Spans | Set OTEL_LOG_SPANS=1 and/or OTEL_EXPORTER_OTLP_ENDPOINT (OTLP/HTTP JSON → Collector / Jaeger / Tempo) |
No proprietary APM required.
get_runLocal defaults use file-backed control-plane jobs.
MIT — see LICENSE.