Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

ToolYour

by AbdulWahabRaza123version 1.0.1i★ –iRuns in the cloud
Registry namecom.toolyour/mcp

Install

Overview

Description from the maker (original English)

Remote MCP: plan, run, verify for SEO/security/ship-gate. Same REST API key; 500 free credits/month.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP, SSE
  • Category: Cybersecurity
  • You need to fill in: X-Api-Key

Install

Pick the AI app you use, then copy the settings.

Before you install

Values 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.

Open in Cursor

Or copy the settings yourself

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.

Open in VS Code

Or copy the settings yourself

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.

Values you fill in

  • X-Api-Key secret required HTTP header
    ToolYour API key from the dashboard (prefix ty_). Same key as REST.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain toolyour.com (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Cybersecurityi

  • More stars than 0% of the other 995 servers in this category
  • Published to the registry more recently than 43% of the other 995 servers in this category
  • Basic checks equal to or better than 100% of the other 995 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is ToolYour safe?

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.

What keys or codes does it need?

You need to fill in: X-Api-Key

Does it run on my computer or in the cloud?

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.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 2 months ago.

Which apps can use it?

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.

What can I use instead?

In the same category: SML Risk Firewall, Nife, ipdata MCP by usefulapi

Alternatives

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

SML Risk Firewall

by scriptmasterlabs.com

Pre-trade risk checks for agent trades: orders vs your limits, signed receipts.

Runs in the cloudUpdated today
Install

Nife

by nifetency

Manage Nife.io cloud apps, sites, secrets and Git integrations from MCP clients.

Runs in the cloudUpdated today
Install

Look up location, network, company and threat data for IP addresses and ASNs in ipdata.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

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.

Open-source ToolYour MCP

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)

Quick start

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)

Auth

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).

Host contract

ToolYour does not replace Cursor/Claude. The host keeps editor, git, and terminal. Agents should:

  1. plan_task (free)
  2. run_playbook or solve_task
  3. Apply only rank-1 loop.nextActions in the workspace
  4. verify_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 (private beta)

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.

Offline evals (no API key)

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

Observability (open protocols)

SignalHow
JSON logsAlways (LOG_LEVEL)
In-process counters/health/mcp + /health/mcp/metrics
SpansSet OTEL_LOG_SPANS=1 and/or OTEL_EXPORTER_OTLP_ENDPOINT (OTLP/HTTP JSON → Collector / Jaeger / Tempo)

No proprietary APM required.

What stays hosted (optional)

  • Live tool execution via gateway + API key
  • Feature Memory / verification profiles (SaaS Mongo)
  • Redis for multi-replica async get_run

Local defaults use file-backed control-plane jobs.

License

MIT — see LICENSE.

Ask PopNx