Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Search lab-filtration products by specification, with prices and lead times.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"porefind": {
"command": "npx",
"args": [
"-y",
"@reneturcios/porefind",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add porefind -- npx -y @reneturcios/porefind mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"porefind": {
"command": "npx",
"args": [
"-y",
"@reneturcios/porefind",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"porefind": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/porefind",
"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、图片和脚本已被移除。链接会离开本站。
porefind is a thin local bridge to Filtrous' hosted catalog of laboratory filtration products: syringe filters, membranes, filter paper and the like, each with its pore size, material, SKU, price and stock position. The bridge stores nothing. It presents the upstream server's tool list locally, exactly as captured, and passes each tool call through to the remote endpoint, handing back whatever comes back untouched.
Catalog work here is read-only. You can search the catalog by free text or by specification terms, open one product for its full detail — variants, options, images and spec metafields — and ask for the current price and lead time on a single SKU. Pricing for the last of these sits behind the upstream's API key, as its own description says.
The live capture of the upstream server listed four tools. This build serves three. The fourth, request_quote, took a list of items plus a contact object and submitted them to the vendor as a quote request — personal contact details routed into a sales pipeline. That is out of scope for this program under its safety rule, so the tool is omitted entirely: it is not registered, it does not appear in tools/list, calls to it are rejected like any unknown name, and the test suite asserts its absence at both the registry and the served MCP layer.
search_products — search the catalog by free text and/or spec terms (for example 0.22 micron PES syringe filter); field filters such as product_type:... or tag:... are also honoured. Returns matching products with title, handle, SKU, product type, tags, price and availability. Required: query. Optional: limit (1-50, default 10).get_product_details — full detail for one product by its handle (the slug a search returns): variants, SKUs, options, prices, images and spec metafields. Required: handle.get_price_and_lead_time — current price, availability and, when permitted, stock for one exact SKU. Required: sku. This is the keyed tool: it needs a valid API key upstream.FILTROUS_MCP_URL (optional) — override the upstream endpoint. Defaults to https://filtrous-mcp-catalog.filtrous.workers.dev/mcp. (The override hook is this rebuild's own labelled reconstruction.)FILTROUS_API_KEY (optional) — when set, every upstream request carries an Authorization: Bearer header; when it is not set, no auth header is sent. (This forwarding is also a labelled reconstruction; the original surface was captured keyless.)The first tool call opens a streamable HTTP session with the upstream: a JSON-RPC initialize request (protocolVersion 2025-03-26, clientInfo name porefind), then a notifications/initialized notification, then the tools/call request carrying the caller's arguments unchanged. If the upstream's initialize reply carries an Mcp-Session-Id header, that value rides on every later request of the session, which is reused for the life of the process. Replies may arrive as plain JSON or as server-sent events; both are read.
Successful upstream results pass through verbatim, including any isError flag the upstream sets. Failures — a JSON-RPC error, a non-2xx status, an unreadable response, or a request that cannot be completed — come back as an isError result whose text starts with porefind error: (this rendering is this rebuild's own labelled reconstruction).
Each kept tool is also a subcommand taking one JSON argument string:
npx @reneturcios/porefind search_products '{"query":"0.22 micron PES syringe filter","limit":5}'
npx @reneturcios/porefind get_product_details '{"handle":"pes-syringe-filter-022"}' npx @reneturcios/porefind get_price_and_lead_time '{"sku":"SF-PES-022-25"}' npx @reneturcios/porefind --version
Exit codes: 0 on success, 1 on an isError result, 2 on a usage error.
npx -y @reneturcios/porefind mcp
MCP client config:
{
"mcpServers": { "porefind": { "command": "npx", "args": ["-y", "@reneturcios/porefind", "mcp"] } } }
docker run -i ghcr.io/cloudcorprecords/porefind
docker run --rm ghcr.io/cloudcorprecords/porefind --version
The container's default command is mcp, so the first form is a stdio MCP server; any other arguments reach the CLI normally.
npm install
npm run build npm test npm run dev
The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.
MIT — see LICENSE.