Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Enterprise account-research resources, product information and reproducible corporate-group samples.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://entityreach.com/api/public-mcp在终端中运行这条命令
claude mcp add --transport http public-resources https://entityreach.com/api/public-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"public-resources": {
"url": "https://entityreach.com/api/public-mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"public-resources": {
"type": "http",
"url": "https://entityreach.com/api/public-mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://entityreach.com/api/public-mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 entityreach.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于31天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有: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、图片和脚本已被移除。链接会离开本站。
EntityReach helps enterprise teams research corporate groups and review possible expansion across existing customer accounts.
This repository contains connection examples and metadata for the hosted EntityReach MCP service. It does not contain the production backend or license company data for redistribution.
Endpoint: https://entityreach.com/api/public-mcp Transport: Streamable HTTP, with stateless JSON responses. Protocol versions: 2025-06-18 and 2025-03-26.
| Tool | What it returns |
|---|---|
get_entityreach_product_information | Product capabilities, pricing, access requirements and coverage limitations. |
list_entityreach_public_resources | Public documentation, account-research guides, methodology and support links. |
get_entityreach_group_sample_analysis | Reproducible analysis of a static Alphabet corporate-group sample. |
These tools are read-only. The public endpoint does not search live company records, return private workspaces, reveal contacts or start monitoring. The sample has 483 records across 65 country codes; records include branches and locations and must not be presented as 483 legal subsidiaries or potential buyers. The sample is not a current ownership statement or a worldwide coverage benchmark.
claude mcp add --transport http entityreach-public https://entityreach.com/api/public-mcp
For another client, create a remote Streamable HTTP connection to the same endpoint. cursor-mcp.json and vscode-mcp.json provide the appropriate configuration shapes. The sample diagnostic client requires Node.js 20+ and no dependencies:
node entityreach-mcp-client.mjs --public get_entityreach_group_sample_analysis
Install the public extension from this repository:
gemini extensions install https://github.com/sens663/entityreach-mcp
The root gemini-extension.json connects directly over Streamable HTTP and includes only the three public, read-only tools. No API key is required. It passed gemini extensions validate with Gemini CLI 0.63.0. The repository is tagged for the official Gemini CLI gallery's daily crawler; gallery indexing is a separate step and is not yet confirmed.
Endpoint: https://entityreach.com/api/mcp Authentication: Authorization: Bearer YOUR_ENTITYREACH_API_KEY.
Live access requires an activated workspace, a scoped EntityReach key, the relevant permissions and agreed allowances. Store the key in your client's secret settings or secure server environment. Do not put a key in a prompt, repository, URL or directory submission.
Company tools include search_companies, get_company_profile, get_corporate_group and find_company_contacts. Search requires a legal company name or identifier and a two-letter country code. Confirm an ambiguous company before retrieving its group. Contact previews do not reveal email/mobile details or consume contact-reveal credits. Workflow tools depend on workspace plan, scope and monitoring allowances.
This Bearer-key endpoint does not supply OAuth discovery. OAuth-only clients should use the separately documented ChatGPT connector and owner-approved workspace linking. A protocol handshake does not prove live data availability: test an actual company search and inspect HTTP errors, JSON-RPC errors and isError results.
Coverage varies by company and jurisdiction. A corporate relationship does not establish buying intent, budget, procurement independence or existing agreement coverage. Preserve the evidence classifications returned by the service.
The public service is published in the official MCP Registry as com.entityreach/public-resources, version 1.0.0. It is also searchable in the mcpub archive using EntityReach; its separate live scanner may take time to index it.
plugin/ contains a portable Agent Plugins package, the existing EntityReach logo and prepared review scenarios. It is not yet a ChatGPT or Claude directory listing. Developer identity verification, platform testing, a walkthrough and directory review remain separate steps. The package contains no production backend or private credentials.