Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Search a curated directory of ISO 27001, SOC 2 and compliance services, with listing checks.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"complydir": {
"command": "npx",
"args": [
"-y",
"@reneturcios/complydir",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add complydir -- npx -y @reneturcios/complydir mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"complydir": {
"command": "npx",
"args": [
"-y",
"@reneturcios/complydir",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"complydir": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/complydir",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A directory of compliance help, searchable from your agent. complydir wraps a curated catalog of services that work on ISO 27001, SOC 2, DORA and neighbouring frameworks — consultancies, auditors and software — published as a single catalog snapshot. There is no account and no API key: the tools fetch the snapshot, answer questions about it locally, and can queue a new free listing for review.
Because search happens over the snapshot rather than a remote search call, the filter rules are exact and predictable. Tag filters never do substring matching: asking for the region "Germany" returns services tagged Germany, and asking for two frameworks returns only services tagged with both.
search_services — multi-filter catalog search. All parameters are optional, but at least one is required: query (free text used to rank the filtered set), framework (a single framework), frameworks (several frameworks, ANDed together), region, industry, service_type, and limit (1–25, default 10). Tag matches are case-insensitive and exact, and a service_type of "Consulting" also matches services tagged "Consultants". For example, frameworks ["ISO 27001", "DORA"] with region "Germany" and service_type "Consulting" returns German services covering both frameworks that consult.check_if_listed — whether a company is in the catalog. Takes a required company_name (for example "Scrut Automation") and answers with the matched record when it is listed.get_service_details — the full catalog record for one service, by its required service_name (for example "Compleye").list_categories — the distinct values in one dimension of the catalog, with counts. dimension is one of frameworks, regions, industries, service_types or problems; omit it to get every dimension at once.submit_listing — queue a free listing (the one write tool). Required: name, url (http or https), email (a contact address, not shown publicly) and brief_summary (10–300 characters). Optional: description, linkedin, service_type, region_covered and compliance_framework_expertise. Confirm the name, website, contact email and one-line summary with the user before calling — a queued listing goes into the same review queue as the free web form and is not live instantly.The read tools fetch the public snapshot from https://ismsdirectory.com/api/tools.json and run over it in memory; submit_listing posts to https://ismsdirectory.com/api/submit. Both go through one injectable fetch function, which is how the test suite exercises everything against a small hand-built snapshot with no live calls.
Two shapes are labelled reconstructions, because the published material pins the fields rather than the record layout: the per-service record fields beyond a service's name and its framework, region, industry and service-type tags, and the tools' output objects. Outputs are built around the pinned fields — the service name, its tags and the filters that matched.
Failures read plainly: a non-2xx upstream reply is complydir error: HTTP , an unreachable upstream is complydir unreachable, and a snapshot that does not parse as a list of records is complydir snapshot invalid.
Each tool is a subcommand taking one JSON argument string:
npx @reneturcios/complydir search_services '{"frameworks":["ISO 27001","DORA"],"region":"Germany","service_type":"Consulting"}'
npx @reneturcios/complydir check_if_listed '{"company_name":"Scrut Automation"}' npx @reneturcios/complydir get_service_details '{"service_name":"Compleye"}' npx @reneturcios/complydir list_categories '{"dimension":"frameworks"}' npx @reneturcios/complydir submit_listing '{"name":"Acme Compliance","url":"https://acme.example","email":"hello@acme.example","brief_summary":"ISO 27001 consulting for SaaS"}' npx @reneturcios/complydir --version
Exit codes: 0 on success, 1 on a runtime error, 2 on a usage error.
npx -y @reneturcios/complydir mcp
MCP client config:
{
"mcpServers": { "complydir": { "command": "npx", "args": ["-y", "@reneturcios/complydir", "mcp"] } } }
docker run -i ghcr.io/cloudcorprecords/complydir
docker run --rm ghcr.io/cloudcorprecords/complydir list_categories '{"dimension":"regions"}'
npm install
npm run build # tsc -> dist/ npm test # tsx --test test/*.test.ts (fake fetch only, no network) npm run dev # run the CLI from source
MIT — Copyright (c) 2026 Rene Turcios