English Français العربية

Iso

السجل الرسمي أخرى

ISO Standards MCP.

الشيفرة المصدرية الموقع التوثيق

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http iso 'https://gateway.pipeworx.io/iso/mcp'
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "iso": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/iso/mcp"
        }
    }
}
NPM package @pipeworx/mcp-iso
Claude Code 
claude mcp add iso -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-iso@0.2.1
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "iso": {
            "command": "npx",
            "args": [
                "-y",
                "@pipeworx/mcp-iso@0.2.1"
            ],
            "env": {
                "PIPEWORX_API_KEY": "<your pipeworx_api_key>"
            }
        }
    }
}

متغيرات البيئة

  • PIPEWORX_API_KEY سري Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. mcp-iso
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-iso

ISO Standards MCP.

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

ToolDescription
search_standardsSearch the full ISO catalogue (~all deliverables) by keyword across reference, title and abstract, with optional filters. Returns reference, title, status, abstract snippet, committee and the iso.org link. Use to find standards on a topic ("supply chain security", "medical device risk").
get_standardFull record for one ISO standard by number ("27001") or reference ("ISO/IEC 27001:2022"): title, abstract, status, edition, publication date, ICS, committee, the supersession chain, the correct iso.org page, and a best-effort live price. The reliable lookup (resolves any standard via its catalogue id).
compliance_catalogCurated catalogue of the compliance-relevant ISO standards (ISMS/27000, privacy, AI/42000, quality, continuity, risk) → ISO number, family and summary. Static name→number resolver; pass a number to get_standard for the live record.
open_data_filesURLs for the ISO Open Data bulk files (deliverables metadata, ICS classification, technical committees), ODC-By 1.0. The deliverables file is what backs this pack. Use to ingest the full dataset yourself.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "iso": {
      "url": "https://gateway.pipeworx.io/iso/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/iso/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1683+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/search_standards \
  -H 'Content-Type: application/json' \
  -d '{"query":"supply chain security"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/search_standards. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "iso": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-iso"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-iso

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Iso data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

الأسئلة الشائعة

ما هو Iso؟

ISO Standards MCP.

كيف أثبّت Iso؟

يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http iso 'https://gateway.pipeworx.io/iso/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج Iso إلى مفتاح API؟

نعم. يتطلب PIPEWORX_API_KEY، وتضبطها في إعداداته.

هل Iso مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون Iso؟

ينشره pipeworx-io. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.